Hello,
I have proceed crash-tests for StarWind and I have faced a problem. I need solution for future similar situation.
How I have got the problem.
1. I moved vCenter to StarWind storage to extend SW volume capacity. Done. works fine.
2. I shut a CVM down to extend HDD of CVM. vCenter frizzed after that and one of ESXi is getting glitching.
3. I rebooted ESXi . all VMs works on second ESXi node. Web GUI on the first ESXi was not available. The reason of problem with img file.
It was a long way to resolve the gui problem. finally I disabled Sync and Replication links and then I got a chance to reach the img file.
previously if you try to ls /vmfs/volume ESXi console is suspended immediately.
Current condition
1. Physical disks - looks the same for both nodes in SW Web GUI
2. Storage pools - the same
3. Volumes - the same
4. LUN presents but "Limited availability"
5. Network All Links have status is "Up". Even though I got down NICs Sync and Replication on second Node.
6. All servers including vCenter are running on the second node. SW LUN is available for second node. on first node only CVM is running.
7. on ESXi Devices tab for the first node system doesn`t have StarWind disk for now. I think because of broken img is located on the CVM.
Is this a good way to remove manually unecessary or broken img files from /mnt/volume0 and from /opt/starwind/../../headres/LUN_Name ? f PowerShell script doesn`t remove this files .
What is the strategy in this case to restore SW Cluster ?
Support bundle for both nodes https://dropmefiles.com/AKwNv
The Latest Gartner® Magic Quadrant™Hyperconverged Infrastructure Software