Public Update:
We found some discrepancies in the starwinds configuration file. It appeared that there were multiple image file objects for the same file on the disk, the one that was experiencing issues. After clearing all the config for the issue LUN, the following was completed:
- Removed partner target from node 2 that pointed to node 1
- Deleted header files from the CVM configuration files
- Deleted the LUN files from the disk array
Following a reboot of node 1 CVM, I used the AddPartner script I posted above to rebuild the HA LUN. This appeared to be a successful and complete resolution to my issue.
The original cause appears to be previous failures from repairing the LUN that resulted in leftover bad configuration in the StarWind.cfg configuration set.
We found some discrepancies in the starwinds configuration file. It appeared that there were multiple image file objects for the same file on the disk, the one that was experiencing issues. After clearing all the config for the issue LUN, the following was completed:
- Removed partner target from node 2 that pointed to node 1
- Deleted header files from the CVM configuration files
- Deleted the LUN files from the disk array
Following a reboot of node 1 CVM, I used the AddPartner script I posted above to rebuild the HA LUN. This appeared to be a successful and complete resolution to my issue.
The original cause appears to be previous failures from repairing the LUN that resulted in leftover bad configuration in the StarWind.cfg configuration set.
Statistics: Posted by andrew.kns — Sat Sep 14, 2024 12:23 am