Upgrading to Proxmox 9 Issues

eakteam

New Member
Jan 30, 2024
7
1
3
Albania
eakteam.com
I just upgraded to Proxmox 9 but it doesn't work with the new kernel 6.14.8-2-pve and stuck on boot going in emergency mode. If i manually choose old kernel 6.8.12-13-pve everything works OK. Also I have some problems with IPv6 networks, but anyway the most important thing is booting problem. Anyone can help please?

Boot Logs ar attached.
 

Attachments

Hi!

There is a failing service logged in the bootlog:

Code:
Aug 08 14:37:03 server (plymouth)[514]: emergency.service: Unable to locate executable 'plymouth': No such file or directory

With the fact that the boot works with another kernel it's likely that there's something wrong with the boot entry / image for the newer kernel. In that case, could you try re-generate the grub config with update-grub?
 
Also I have some problems with IPv6 networks,
There's also another warning in your bootlog that might point in a direction:
Code:
Aug 08 14:37:01 server networking[694]: warning: vmbr0: up cmd 'ip -6 route add 2a01:4f8:10b:2119::/64 dev vmbr1' failed: returned 1 (Cannot find device "vmb>
Aug 08 14:37:01 server networking[694]: )
Aug 08 14:37:01 server /usr/sbin/ifup[694]: warning: vmbr0: up cmd 'ip -6 route add 2a01:4f8:10b:2119::/64 dev vmbr1' failed: returned 1 (Cannot find device >
                                            )

The whole message is cut of, but I guess that it complains about a missing vmbr1 device here, which might not be created yet at the time where the up-cmd is executed. Please correct me if I don't understand the requirements here yet, but if that's the case it would be better to move that up-cmd to the vmbr1 entry.
 
Hi!

There is a failing service logged in the bootlog:

Code:
Aug 08 14:37:03 server (plymouth)[514]: emergency.service: Unable to locate executable 'plymouth': No such file or directory

With the fact that the boot works with another kernel it's likely that there's something wrong with the boot entry / image for the newer kernel. In that case, could you try re-generate the grub config with update-grub?
The issue not comming from plymouth since i tried t install it and try again.

Anyway here is the generated grub file:

Grub Config
 
There's also another warning in your bootlog that might point in a direction:
Code:
Aug 08 14:37:01 server networking[694]: warning: vmbr0: up cmd 'ip -6 route add 2a01:4f8:10b:2119::/64 dev vmbr1' failed: returned 1 (Cannot find device "vmb>
Aug 08 14:37:01 server networking[694]: )
Aug 08 14:37:01 server /usr/sbin/ifup[694]: warning: vmbr0: up cmd 'ip -6 route add 2a01:4f8:10b:2119::/64 dev vmbr1' failed: returned 1 (Cannot find device >
                                            )

The whole message is cut of, but I guess that it complains about a missing vmbr1 device here, which might not be created yet at the time where the up-cmd is executed. Please correct me if I don't understand the requirements here yet, but if that's the case it would be better to move that up-cmd to the vmbr1 entry.
But what can I do to fix it?
 
There's also another warning in your bootlog that might point in a direction:
Code:
Aug 08 14:37:01 server networking[694]: warning: vmbr0: up cmd 'ip -6 route add 2a01:4f8:10b:2119::/64 dev vmbr1' failed: returned 1 (Cannot find device "vmb>
Aug 08 14:37:01 server networking[694]: )
Aug 08 14:37:01 server /usr/sbin/ifup[694]: warning: vmbr0: up cmd 'ip -6 route add 2a01:4f8:10b:2119::/64 dev vmbr1' failed: returned 1 (Cannot find device >
                                            )

The whole message is cut of, but I guess that it complains about a missing vmbr1 device here, which might not be created yet at the time where the up-cmd is executed. Please correct me if I don't understand the requirements here yet, but if that's the case it would be better to move that up-cmd to the vmbr1 entry.
This is my network config: Network Config
 
The issue not comming from plymouth since i tried t install it and try again.
Yes, plymouth is not the issue but there might be an issue while generating the initramfs, installing the kernel image, etc. So you can try to regenerate the GRUB config and check if the installation of the new kernel was successful (or try reinstalling the package) and check whether the host can boot with that kernel again.
 
But what can I do to fix it?
I'm not sure about what you're trying to do here:

Code:
iface vmbr0 inet6 static
    address 2a01:4f8:10b:2119::***/127
    up ip -6 route add 2a01:4f8:10b:***::/64 dev vmbr1

But you shouldn't reference other interfaces in the command then the currently referenced one. Or did you meant vmbr0 here?