Page 1 of 1
Accessing img file after service failure
Posted: Thu Nov 13, 2025 9:49 am
by csduser01
After an unclear vm failure vSan Free does not syncronize anymore and iscsi target are not available from vmware.
There is any way to access data inside the .img disk or to restore the target even in one-node mode?
In attachment the log file of the first node.
Re: Accessing img file after service failure
Posted: Thu Nov 13, 2025 10:00 am
by yaroslav (staff)
Hi,
Welcome to StarWind Forum.
Could you please let me know what is happening to another node? Is it up?
Please install the Windows-based Management Console, connect to all replication partners, and share the screenshot of what HA devices look like.
Re: Accessing img file after service failure
Posted: Thu Nov 13, 2025 10:09 am
by csduser01
Hi, Yaroslav,
to my eyes both nodes give the same feedback. Find in attachment the console's screenshot of the first node.
Network is working fine, no firewall between the two nodes. The problem raise this morning after months running without problems.
Re: Accessing img file after service failure
Posted: Thu Nov 13, 2025 11:16 am
by yaroslav (staff)
Thanks.
Remove write-back caching
https://knowledgebase.starwindsoftware. ... -l1-cache/ and follow this guide.
Stop on one node, StarWindService and mark as synchronized on another. (it should be the only replication partner). Make sure to follow
https://knowledgebase.starwindsoftware. ... -blackout/
You can force synchronization, try using manual synchronization. Use SyncHaDevice.ps1, comment $device.Synchronize([SwHaSyncType]::SW_HA_SYNC_FULL, "") and uncomment #$device.MarkAsSynchronized()
Start the VMs and see if data inside is up-to-date.
If you are happy with what you see, resume another node. Otherwise, repeat stop the service on the only active node and mark its counterpart.
Sync starts after you resume all replication partners.