I just recently had to reboot my Starwind target due to Windows patching. I shutdown all VMs connected to the datastores that were going offline and patched my server (and upgraded to Starwind 6.0.5189 after patching). Once the Starwind server came back online, two of my datastores would not mount on my ESXi cluster. I rebooted both of my hosts and still the datastore wouldn't mount (even after multiple refreshes and rescans of my hba). The devices are visible on both hosts, just not the datastores themselves.
I was able to add storage manually to the first host in the cluster and said "keep existing vmfs signature". However, I'm unable to mount the luns on the second host. When I go to the "Add Storage" link and select one of the luns, the "Keep Existing Signature" box is disabled and my only option is to "Format".
My other two datastores came back fine. The only thing different about the ones that didn't come back up is that there's a gap in names between the two that came up and the two that came down. The ones that came back online are "ImageFile1" and "ImageFile2". The ones that wouldn't come back online are "ImageFile5" and "ImageFile6" (I originally had additional luns that I removed because I no longer needed them).
I'm at a loss for troubleshooting further. I've attached my Starwind log. The target is set for "Clustering = True". The two luns that won't mount are both set to Asynchronous Mode = Yes.
Thanks
Dark Diamond
