Update:

Was able to resolve the issue. I updated my CVM and my Starwind X library, and the problem resolved itself. If anyone stumbles across this in the future with the same problem, that my advice.

yaroslav (staff) wrote: ↑

Tue Feb 03, 2026 7:44 pm

Yes, I also noticed that bit. Can you try using a different slash?

It appears the StarwindX library is adding the backslash. Even if I add a forward slash to the beginning of the image name, or a forward slash to the end of my image path, starwind seems to insert the backslash.

Try using root/starwind. Also, try moving the IP addresses around so that p1 refers to the 2nd node while p2 refers to the first. Thanks for the response, On your first point, I am authenticating to the Starwind appliances correctly, just removed the username and password from my post for security ...

PMing support requests also kinda defauts the purpose of a support form. Having it as a post means the poor shmuck who runs into the same problem as you 4 years down the line can find an answer when googling

Due to some issues, I had to recreate one of my two Starwind nodes, running on the starwind CVM, with a free license. All data is still intact on the functioning node. I have successfully used the "removeHAPartner" Powershell script, and removed any remininats of swdisks, headers, or refer...