Hello,
We have an issue with one of our Proxmox servers.
In our country, we often have power outages for longer time that the UPS can hold, so the server stops and sometimes stops before VMs can poweroff first.
At the next boot, the server try to start the 3 VMs, however the 2 firsts have an error, then the 3rd can boot normally (it is always the same VMs that have the issue)
The 1st VM boot at 0s
The 2nd VM boot at 10s
The 3rd VM boot at 20s
The error:
The server is actually running the last version of PVE 5.4
pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-20-pve)
with all updates applied
We looked at the logs and found the error, but didn't find relevant information about the reason of it.
We checked the /dev/zvol/rpool/data and could see the link to the disks, so it exists (at least afterward)
What we don't understand is why the directory is not found when the first 2 VMs start?
We intended to extend the boot time at 30 / 40 / 50 seconds meanwhile to see if the issue continues (to let more time to the services to start, just in case...)
Does anyone had this issue before?
Haw can it be fixed?
Thanks for your answers!
We have an issue with one of our Proxmox servers.
In our country, we often have power outages for longer time that the UPS can hold, so the server stops and sometimes stops before VMs can poweroff first.
At the next boot, the server try to start the 3 VMs, however the 2 firsts have an error, then the 3rd can boot normally (it is always the same VMs that have the issue)
The 1st VM boot at 0s
The 2nd VM boot at 10s
The 3rd VM boot at 20s
The error:
Code:
kvm: -drive file=/dev/zvol/rpool/data/vm-[VMID]-disk-0,if=none,id=drive-scsi0,format=raw,cache=none,aio=native,detect-zeroes=on: Could not open '/dev/zvol/rpool/data/vm-[VMID]-disk-0': No such file or directory
TASK ERROR: start failed: command '/usr/bin/kvm [VM DETAILS] failed: exit code 1The server is actually running the last version of PVE 5.4
pve-manager/5.4-13/aee6f0ec (running kernel: 4.15.18-20-pve)
with all updates applied
We looked at the logs and found the error, but didn't find relevant information about the reason of it.
We checked the /dev/zvol/rpool/data and could see the link to the disks, so it exists (at least afterward)
What we don't understand is why the directory is not found when the first 2 VMs start?
We intended to extend the boot time at 30 / 40 / 50 seconds meanwhile to see if the issue continues (to let more time to the services to start, just in case...)
Does anyone had this issue before?
Haw can it be fixed?
Thanks for your answers!
