Not booting after Update

[Miree]

Hey there,

we are using a PBS and the update process in the GUI worked like a charm.

Today we have done it the same way we did before: first "refreshed", then "update". After that we have rebootet the system via the GUI. Now the system is not starting.

We do not have access directly to the system, we use a managed server in the cloud. We have bootet into a rescue system and we have access to the rescue system via SSH, but now we don't know what to do.

Is there a way to revert the last updates? Is there anything else we should check?

Thanks to all of you who can help us.

Here is the output of the /var/log/apt/history.log:

Start-Date: 2025-04-11  08:30:53
Commandline: apt full-upgrade
Upgrade: proxmox-widget-toolkit:amd64 (4.3.7, 4.3.10), pve-firmware:amd64 (3.14-3, 3.15-3), tzdata:amd64 (2025a-0+deb12u1, 2025b-0+deb12u1), liblzma5:amd64 (5.4.1-0.2, 5.4.1-1), pbs-i18n:amd64 (3.4.1, 3.4.2), xz-utils:amd64 (5.4.1-0.2, 5.4.1-1), proxmox-backup:amd64 (3.3.0, 3.4.0), pve-xtermjs:amd64 (5.3.0-3, 5.5.0>
End-Date: 2025-04-11  08:31:00

 

[fv3rdugo]

I had a similar problem. In my case it was a permissions issue in /etc/proxmox-backup
Check running proxmox-backup-api and you might see some issues.

Good luck
/usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api
Error: configuration directory '/etc/proxmox-backup' permission problem - wrong permission (701 != 700)

 

[Chris]

Hi,

Today we have done it the same way we did before: first "refreshed", then "update". After that we have rebootet the system via the GUI. Now the system is not starting.

can you describe what exactly is not working? Are you unable to boot the system or is just the Web UI not accessible? Can you ping the host? If it does not boot, do you have insight at which step of the boot it fails?

We do not have access directly to the system, we use a managed server in the cloud.

Does you provider maybe give you a management interface such as IPMI?

 

[Miree]

Thanks for your answers guys.

I think it's not a PBS problem, because after the reboot we are unable to ping the host. I think the system is not booting properly. I'll try to contact the provider to give us access to the console to see where the system is hanging on.

 

[LukasInCloud]

Thanks for your answers guys.

I think it's not a PBS problem, because after the reboot we are unable to ping the host. I think the system is not booting properly. I'll try to contact the provider to give us access to the console to see where the system is hanging on.

Hi from Munich, colleague! Since the host isn’t even responding to ping after the reboot, it’s likely a low-level boot or kernel issue. The best move now is to contact your provider and request direct console or KVM/IPMI access. This way you can see at which point the system hangs. If that’s not possible, try booting into the rescue system again, check /var/log/syslog and /var/log/kern.log for the last boot entries. Also verify /etc/fstab for any mount issues that might block the boot.