Deduplication datastore inactive after san reboot
Posted: Mon Apr 23, 2012 12:55 pm
Hello,
I just upgraded one of my SANs to the 5.9 beta (free edition). I originally had a deduplication lun and a standard lun attached to my home ESXi cluster using the most recent version of 5.8. After I upgraded the SAN (which of course involved a restart of Starwind), the standard lun became available after a short period of time in vCenter. However, the dedupe lun didn't come back online, and the VMs I had within it were not available to start. I tried rebooting vCenter to see if something was "stuck" - but that didn't help either. I'm able to see the device on each individual host, but not the datastore. If I select a host individually, I'm able to add the datastore back, either by "Keeping the existing signature" (which is basically a force mount), or by "Assigning a new Signature".
Should this have happened? I've had to reboot Starwind in the past and don't remember any issues like this? It also seems peculiar that it only affected the dedupe lun.
Thanks!
Chris
I just upgraded one of my SANs to the 5.9 beta (free edition). I originally had a deduplication lun and a standard lun attached to my home ESXi cluster using the most recent version of 5.8. After I upgraded the SAN (which of course involved a restart of Starwind), the standard lun became available after a short period of time in vCenter. However, the dedupe lun didn't come back online, and the VMs I had within it were not available to start. I tried rebooting vCenter to see if something was "stuck" - but that didn't help either. I'm able to see the device on each individual host, but not the datastore. If I select a host individually, I'm able to add the datastore back, either by "Keeping the existing signature" (which is basically a force mount), or by "Assigning a new Signature".
Should this have happened? I've had to reboot Starwind in the past and don't remember any issues like this? It also seems peculiar that it only affected the dedupe lun.
Thanks!
Chris