With trial, you still can benefit from support and integration assistance in some form.
Feel free to email support if anything is needed. Just don't forget to use this thread and the reference.
Will be happy to help/bring you in contact with the team.

If your system is stable and running without the hitch, you can stay on 15260.
There has been no NVMe-oF HA for production so far introduced.

That's very strange. Even if you perform a "FULL" installation of StarWind VSAN, it has never been a problem with the latest version. Could it be that the IP address of the installation changed? Could you please see if StarWindService is running in your installation? If you have a license ...

I believe your question relates to CVM.
Could you please try refreshing the page? If that does not help
1. SSH to the VM.
2. lsblk and share the output with me.

Cheers.

I hope it sheds some light on the logging. Also, in the context of logging, I'd like to share with you this KB https://www.starwindsoftware.com/help/E ... dVSAN.html

p.s. in CVM we plan integration with Zabbix. Stay tuned.

You do not need StarWindCluster service for a Windows-based install. It is used for vVols only.
May I wonder why exactly did you give up no CVM?

There are two types of controllers: IDE and SCSI. See more at https://www.ubackup.com/enterprise-back ... -scsi.html. Try Gen 1 VM and IDE controller.

Try connecting the disk to the IDE controller and boot. Also, hook up that disk to an existing VM to see if data is doing well.

Greetings,

I guess that the wrong guide is used. Check this one out https://www.starwindsoftware.com/resour ... chine-cvm/.

My colleagues managed to p2v the disk (single partition) to a dynamic disk without any issues with partitions or data inconsistency.
Could you please let me know if there is any way to hook up that disk and try p2v over again?

Hi,

Nice to read that!

You can find the thread admins or simply reach out to support.

Thanks for your post and welcome to StarWind forum. Could you please explain what kind of issues you ran into?

Hi,

Great to read that Good luck with migration.

Thanks for your feedback. sync_from_first is to be used and it is a known problem. It should be addressed in the next build. Typically the event you shared points to the storage issues, however, here there might be difficulties with header/image creation that explains why only sync_from_first works....