Proxmox 9 boot issues

[sagiziv3]

I have an HPE microserver gen 8 that I just upgrade to version 9 and I get those terrible failures on boot.
I initially tried to do a clean install but it showed an error related to GRUB files, so I installed version 8 and then upgraded to 9 (`pve8to9 --full` showed no errors).
I followed the official guide and everything seemed to go well, but when I rebooted the machine I got those errors.

I can boot to the previous version of the kernel and to the recovery mode of the new kernel, but I am not sure what I need to do from here to fix this.
I can continue with the old kernel, but I still prefer to be on the latest version if possible.

 

[kawano-y]

Could you please share the output using the forum’s code formatting?

This may be related to filesystem errors, an underlying disk or I/O issue, or a storage-driver regression in the newer kernel.

 

[sagiziv3]

@kawano-y I got it from the ILO interface so I don't really have it as text, but I'll convert it

 

[sagiziv3]

@kawano-y I got it from the ILO interface so I don't really have it as text, but I'll convert it

[   16.434665] EXT4-fs (dm-1): Remounting filesystem read-only
[FAILED] Failed to start tailscaled.service - Tailscale node agent.
[FAILED] Failed to start tailscaled.service - Tailscale node agent.
[FAILED] Failed to start lxc-net.service - LXC network bridge setup.
[FAILED] Failed to start open-iscsi.service - Login to default iSCSI targets.
[FAILED] Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
[FAILED] Failed to start rbdmap.service - Map RBD devices.
[FAILED] Failed to start ssh.service - OpenBSD Secure Shell server.
[FAILED] Failed to start tailscaled.service - Tailscale node agent.
[FAILED] Failed to start blk-availability.service - Availability of block devices.
[FAILED] Failed to start lxc.service - LXC Container Initialization and Autoboot Code.
[FAILED] Failed to start pve-firewall-commit.service - Commit Proxmox VE Firewall changes.
[FAILED] Failed to start pve-sdn-commit.service - Commit Proxmox VE SDN changes.
[FAILED] Failed to start pvedaemon.service - PVE API Daemon.
[FAILED] Failed to start pvestatd.service - PVE Status Daemon.
[FAILED] Failed to start systemd-user-sessions.service - Permit User Sessions.
[FAILED] Failed to start pveproxy.service - PVE API Proxy Server.
[FAILED] Failed to start pve-firewall.service - Proxmox VE firewall.
[FAILED] Failed to start spiceproxy.service - PVE SPICE Proxy Server.
[FAILED] Failed to start pve-guests.service - PVE guests.
[FAILED] Failed to start pvescheduler.service - Proxmox VE scheduler.
[FAILED] Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
[FAILED] Failed to start ssh.service - OpenBSD Secure Shell server.
[FAILED] Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
[FAILED] Failed to start ssh.service - OpenBSD Secure Shell server.
[FAILED] Failed to start pvedaemon.service - PVE API Daemon.
[FAILED] Failed to start tailscaled.service - Tailscale node agent.
[FAILED] Failed to start pveproxy.service - PVE API Proxy Server.
[FAILED] Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
[FAILED] Failed to start ssh.service - OpenBSD Secure Shell server.
[FAILED] Failed to start pvedaemon.service - PVE API Daemon.
[FAILED] Failed to start tailscaled.service - Tailscale node agent.
[FAILED] Failed to start pveproxy.service - PVE API Proxy Server.
[FAILED] Failed to start tailscaled.service - Tailscale node agent.
[FAILED] Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
[FAILED] Failed to start ssh.service - OpenBSD Secure Shell server.
[FAILED] Failed to start pvedaemon.service - PVE API Daemon.
[FAILED] Failed to start pveproxy.service - PVE API Proxy Server.
[FAILED] Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
[FAILED] Failed to start ssh.service - OpenBSD Secure Shell server.
[FAILED] Failed to start pvedaemon.service - PVE API Daemon.
[FAILED] Failed to start pveproxy.service - PVE API Proxy Server.
[FAILED] Failed to start pve-cluster.service - The Proxmox VE cluster filesystem.
[FAILED] Failed to start cron.service - Regular background program processing daemon.
[FAILED] Failed to start pvedaemon.service - PVE API Daemon.
[FAILED] Failed to start ssh.service - OpenBSD Secure Shell server.
[FAILED] Failed to start pveproxy.service - PVE API Proxy Server.

 

[UdoB]

[ 16.434665] EXT4-fs (dm-1): Remounting filesystem read-only

Well..., now the seconds before this one would be interesting. Everything here is too late.

Is it possible to catch them the same way? There must be a reason for "remount read-only" - possibly/hopefully logged in the seconds before.

ILO has a local device management and an error log, right? Did you check that?

What is the state (on the console) at the end? Do you get a login prompt? (Just press "Enter" to (possibly) trigger it to get redrawn).