We’re running an old Proxmox server, v1.9. It’s been a workhorse for years running several VMs flawlessly. It is mostly used for internal purposes so it is not really exposed.
Suddenly one of the VMs won’t start. This VM has a large database on it that has been neglected to be backed up to an external device. Therefore, it is important for us to get it started again so we can rectify that situation.
I’m not the one who setup the proxmox configuration and the person who did has left. I’m hoping there might be expertise here that can help resolve this situation. Here are some red flags that may help narrow it down.
Suddenly one of the VMs won’t start. This VM has a large database on it that has been neglected to be backed up to an external device. Therefore, it is important for us to get it started again so we can rectify that situation.
I’m not the one who setup the proxmox configuration and the person who did has left. I’m hoping there might be expertise here that can help resolve this situation. Here are some red flags that may help narrow it down.
- When checking the logs, the only thing I get is: “VM 104 start failed - Transport endpoint is not connected”
- A failure when backing up gives: “ERROR: Backup of VM 104 failed - command 'qm set 104 --lock backup' failed with exit code 255”. This was the first backup after many successful ones.
- When using the Proxmox portal I see all VMs and their status. When doing 'qm list' it doesn't show any running VMs, only two stopped ones.
- Most of the Storage Volumes are at or close to 100% capacity, except for local which is at 50% capacity.
- The disk space for each VM, shows more free space, of course I can’t see the space for the one that failed to start.
- It does look like I have successful backups of the VM from when it was last running.