I have upgraded our first node of a 3-node cluster from 8.4.19 to 9.x.
I have all done I needed to do: tested on a test-cluster, took my time, checked everything multiple times before moving to the next step and yet, the thing I always fear when I perform a upgrade happend: a non responsive PVE. It hangs on on /dev/mapper/pve-root
I can ping the GUI IP but it is not loading
I can't start a SSH session on that IP
specifications:
PVE-enterprise
FRR
CEPH
NIC pinning
PBS (upgraded to 4.x)
Can you access the local console or does the boot stall before that?
If you can, what does journalctl tell you?
If not and assuming you use systemd-boot, you should try booting into rescue mode by manually adding systemd.unit=rescue.target to the end of the linux line in your bootloader. From there, check any previous problematic boots with journalctl -b -1 (or -2, -3, etc. to show to a problematic boot).
Can you access the local console or does the boot stall before that?
If you can, what does journalctl tell you?
If not and assuming you use systemd-boot, you should try booting into rescue mode by manually adding systemd.unit=rescue.target to the end of the linux line in your bootloader. From there, check any previous problematic boots with journalctl -b -1 (or -2, -3, etc. to show to a problematic boot).
Thank you for your reaction.
It stops at the screen attached in the previous post and doesn't go further
Currently, I have access via ilo and can see this screen before it stops:
after e:
update: I deleted quiet at the end of the "linux" line and after boot it hangs here:
