the server complains that there was a disconnet on the 20th 3:36am. It automatically logs out the iscsi user after some time and the re-login from the Globalsan app sometimes takes too long, so that OSX detects a hard disconnect. But I do still get disconnecting errors on my server, because of some weird behavior of the Qnap. I did not get a GLO warning from the Globalsan software yet, which is a good sign. And I did re-enable the HD sleep function in the Qnap box. I did reinstall the iscsi luns using instant alloction (witch is block access I think).
If so, is there a way to prevent the Qnap from automatically logging out after some idle time? Thanks for your support, Tim Maybe the OS detects the login before the GlobalSAN app, so that I sometimes get the disconnection error message. Sometimes the time gap is short (see yourself in the log), sometimes it takes longer. If the Qnap logs out after a while for some reason, probably the GlobalSAN logs back in after a short time. Are these logouts/logins initiated by the Qnap? Why is that? The GlobalSAN support says that they never logout the device from their software. Strangely the targets logout and back in a few times every day. Is anybody else using GlobalSAN with a Qnap box? If so are there any problems? I started the iSCSI logging on the Qnap box and I get inormation only (no errors).
They asked for the full price for an update so I went with GlobalSAN which is way cheaper. I never had any issues with that combination. Before I updated my Mac Mini it ran under 10.9 with the Xtend SAN software. They say it's not related to GlobalSAN but to the QNAP box. So I created a ticket with SNS support and they tried to find the error. Sometimes I get an error window telling me that either files or backup was not disconnected properly. I created 2 targets (backup and files), no ACLs.
The target is a QNAP TS-659 with FW 4.2.6. Latest GlobalSAN iSCSI initiator is installed (5.3.1.555). Hi there, I have a Mac Mini server running under Sierra.