Hello my friends...
I don't know if this behavior has to do with Debian Linux, PVE Kernel or part of the system.
I have a Server with Supermicro mainboard. Everything works fine but, suddenly, the disk changed it identification.
I have an External USB hard driver and another SATA driver connected to this system.
So, this morning, the VM froze, because a malfunction and we need to shutdown the VM.
But, when try to start it again, the Proxmox not found the VM image, because the ID of the disk where VM image file reside, changed from /dev/sdc1 to /dev/sdd1.
Is there someway to prevent this kind of trouble??
I will appreciate any help or advice!
Thank you
I don't know if this behavior has to do with Debian Linux, PVE Kernel or part of the system.
I have a Server with Supermicro mainboard. Everything works fine but, suddenly, the disk changed it identification.
I have an External USB hard driver and another SATA driver connected to this system.
So, this morning, the VM froze, because a malfunction and we need to shutdown the VM.
But, when try to start it again, the Proxmox not found the VM image, because the ID of the disk where VM image file reside, changed from /dev/sdc1 to /dev/sdd1.
Is there someway to prevent this kind of trouble??
I will appreciate any help or advice!
Thank you