Package Update caused all VM's to fail to start

[FourPaws]

Hello All...

Please forgive me if I have posted in the wrong area.

As someone not very familiar to ProxMox, I am unable to work out what has happened. I did a package update to my nodes ( apt update apt upgrade). I rebooted only one of the nodes, and none of the VM's would start. I migrated one of the VM's to another node (also updated) and it also failed to start.

Considering it could be just the one VM being a problem, I shutdown a VM on an updated, but not rebooted node, and that also failed to start.

Restoring a backup did not work.

I cloned a template and that is fine.

I have managed to solve most issues I faced in the past, but this one is currently beyond me. I would very mush appreciate your help and guidance solving this issue.

Please find attached two failure logs.

I thank you for your time.

 

[JeanL]

Hi,

( apt update apt upgrade)

wrong

For the update itself use either the Web UI Node → Updates panel or through the CLI with:

apt update
apt full-upgrade

Note : Always ensure you correctly setup the package repositories and only continue with the actual upgrade if apt update did not hit any error.

see : https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_frequently_asked_questions_2

Make sure that all updates are done properly.

And please post your VM configuration:

qm config <VMID>

Best regards,

 

[FourPaws]

Hi,


wrong

see : https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_frequently_asked_questions_2

Make sure that all updates are done properly.

And please post your VM configuration:

qm config <VMID>

Best regards,

Hello There...

Thanks for the info. I will in future upgrade the way you posted.

Turned out that one node, that had recently been giving me issues was the culprit. All VM's on that node failed to reboot, shutdown or start without errors. Even migrating those VM's to another node caused the same failures.

I ended up removing the node from the cluster. reloading it and adding it back. The VM's were then loaded back from nightly backups.

All ok now..!!

Thanks..!!