by kevin@nextvault.com » Tue Aug 23, 2011 4:47 pm
Here is our environment:
Windows 2008 server running latest version of Starwind.
Has multiple targets both disk and image and several servers connecting to it via separate storage-only LAN.
WE created a new ESX Server and loaded a WIndows 2008 guest OS. Using MS Iscsi initiator connected to a disk target on the above Starwind server no problem. We can access the drive, format it, etc with acceptable performance.
But....
When we reboot the Guest OS server the iscsi intiator sees and connects to the drive very quickly, but when we pull up Windows Disk administrator it takes hours (literally as much as 8 hours) for it to see the new drive, then takes 8+hours to quick format.
We experience the same problem of the Windows Guest OS seeing the drive and using it after reboot (after all formatting is complete) for about 8 hours, then it seems to function and drive performance is acceptable.
We can reproduce this problem on 2 different host systems, one running ESX, one running VMWare server.
The length of delay seems to relate to size of the disk image (5GB image takes less delay than a 500GB image)
We can connect to the same targets without performance problems from any physical machine with the same configuration (separate lan and storage networks)
We don't see any error messages anywhere.
We've checked cabling, switch settings (even change switches), used different NIC interfaces...nothing seems to help this.
Hoping someone can share if they have had similar experiences or other things to check...or a solution!
Thank you