Link to home
Start Free TrialLog in
Avatar of gopher_49
gopher_49

asked on

iSCSI target unavailable when server booted and now desktop/explorer unstable

I have 3 x VMs that use iSCSI target/drives to temporary storage when doing backups...  No mission critical data is on these drives.  When they booted up the iSCSI server didn't have it's storage mounted and resulted in these drive letter not being accessible.  I since then got the iSCSI server side of it working.. But..  The VMs are still unable to see the drives and making explorer hang.  How should I force these VMs to reconnect to the iSCSI target?  One of the VMs I can't even log in for it hangs on loading profile
Avatar of Brett Danney
Brett Danney
Flag of South Africa image

In services find the Server service set this service to be dependent on the ISCSI service. This will stop the machine trying to map the drives before the iscsi drives are up.
Avatar of gopher_49
gopher_49

ASKER

I'm not worried about the servers booting in the future.. I'm trying to get the desktops to respond..   One of them is still stuck logging into the desktop.  I've seen this before when windows can't access a drive explorer gets hung.
ASKER CERTIFIED SOLUTION
Avatar of Brett Danney
Brett Danney
Flag of South Africa image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I had to force reboot he servers due to the desktop being locked up for the administrator account.  I tried remote logging the session of and force reboot via shutdown command.  It seems that I have to make sure the iSCSI server is online before logging into the server.  If I log into the server's desktop and click on one of the drive mapping or if my backup software tries to use the mapping for the temp drive (the only app that uses iSCSI drives) it makes the desktop not stable.  So I guess I just need to be careful.. Set the backup service to manual so it doesn't try to access it.. And just add to my shutdown/startup instructions to make sure the iSCSI target is up prior to servers booting.  Right?