Proxmox 6.x fails to start after upgrading packages through GUI and land on emergency mode

[hisaltesse]

I just updated the packages through the proxmox 6.x (I think 6.4 or 6.5) web interface and it caused the lxc containers to stop working properly... so I rebooted the proxmox node and now it won't come back up. Here is the screenshot of where the boot up process stops in emergency mode. I am not sure what to do here....
Note that I tried to put the root password and tried the journalctl command... couldn't make sense of anything.... then I exited and when it rebooted I got a kernel panic...

Any insight would be greatly appreciated. Thank you.

 

[fabian]

well.. without any log or error output it will be kind of hard to help you..

 

[hisaltesse]

well.. without any log or error output it will be kind of hard to help you..

This is what I have access to.. any commands that I can run in emergency mode that I can provide the output of to make sense of this?
Would the output of journalctl -xb help, or any particular parameters to pass to filter out what you want to see?

 

[fabian]

the full output of journalctl -b and systemctl status might provide some hints.

 

[hisaltesse]

well.. without any log or error output it will be kind of hard to help you..

Here is the output of all the errors in the current boot session with the command:
journalctl -p 3 -xb

 

[hisaltesse]

the full output of journalctl -b and systemctl status might provide some hints.

The output of journalctl -b is way too long and I don't have a way to copy it easily.. I am accessing the server via an old KVM as it is at a datacenter.. I can only take screenshots... if there is a way to filter even more let me know.

Here is the output of systemctl status



How do I run a fsck on the proxmox volume in this (emergency) mode? And would it help? When I do fsck I get "/dev/mapperpve-root is mounted"

 

[fabian]

it timed out waiting for /dev/sdb1 (which is probably referenced in /etc/fstab) - I'd check next what that is supposed to be and why it's not there/coming up.

 

[hisaltesse]

it timed out waiting for /dev/sdb1 (which is probably referenced in /etc/fstab) - I'd check next what that is supposed to be and why it's not there/coming up.

sdb1 is a usb drive attached for container backups.

 

[hisaltesse]

I commented the line that mount sdb1 in /etc/fstab and it allowed the server to complete the boot process.
Thank you for the hint.
Just not sure why it suddenly could not see the usb backup drive that was attached....