[SOLVED] Can't upgrade PVE 7.0 with udev error

[wy3QkoM7Kk3666ou2vd]

Hello!

I have been scratching my head with why I can not do a normal upgrade of my system. It started a couple of days ago until the point where I decided to begin with a clean install of PVE 7.0. But after having everything setup, the same problem comes up even before I do any changes on the server. Hence I can't update "right out of the box". I copied the "apt dist-upgrade" output and the recommended logs in the error description as well which can be found as attached files.

Some apt output:

Setting up udev (247.3-6) ...
Job for systemd-udevd.service failed because the control process exited with error code.
See "systemctl status systemd-udevd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - Rule-based Manager for Device Events and Files
Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
Active: failed (Result: exit-code) since Thu 2021-08-05 16:00:50 CEST; 18ms ago
TriggeredBy: ● systemd-udevd-kernel.socket
● systemd-udevd-control.socket
Docs: man:systemd-udevd.service(8)
man:udev(7)
Process: 39547 ExecStart=/lib/systemd/systemd-udevd (code=exited, status=226/NAMESPACE)
Main PID: 39547 (code=exited, status=226/NAMESPACE)
CPU: 589us

Aug 05 16:00:50 proxmox systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 5.
Aug 05 16:00:50 proxmox systemd[1]: Stopped Rule-based Manager for Device Events and Files.
Aug 05 16:00:50 proxmox systemd[1]: systemd-udevd.service: Start request repeated too quickly.
Aug 05 16:00:50 proxmox systemd[1]: systemd-udevd.service: Failed with result 'exit-code'.
Aug 05 16:00:50 proxmox systemd[1]: Failed to start Rule-based Manager for Device Events and Files.

This is a part of the journal output (don't know how relevant this is):

Aug 05 15:38:14 proxmox systemd[14624]: systemd-udevd.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc/sys/kernel/domainname: No such file or directory
Aug 05 15:38:14 proxmox systemd[14624]: systemd-udevd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-udevd: No such file or directory

Any ideas?

 

[fabian]

is this PVE system installed on baremetal?

 

[wy3QkoM7Kk3666ou2vd]

is this PVE system installed on baremetal?

Yes it is.

 

[fabian]

could you post the full journal since boot (journalctl -b)?

 

[wy3QkoM7Kk3666ou2vd]

could you post the full journal since boot (journalctl -b)?

I have edited the post. The requested log is named 'journalctl_log.txt'.

 

[fabian]

okay, so lxcfs crashes with a fuse error in addition to udev crashing because of lack of namespace support.. could you provide the output of mount? thanks!

something rather strange is going on - this is a clean PVE 7 install? did you enable access to a proxmox repository yet? if not, please do so and try to update to the newest PVE packages as well.

 

[wy3QkoM7Kk3666ou2vd]

okay, so lxcfs crashes with a fuse error in addition to udev crashing because of lack of namespace support.. could you provide the output of mount? thanks!

something rather strange is going on - this is a clean PVE 7 install? did you enable access to a proxmox repository yet? if not, please do so and try to update to the newest PVE packages as well.

Sure thing, the output is attached to the original post.

Yes, I even downloaded the ISO again and used a different USB-stick for the installation and the only thing I do is commenting out the PVE Enterprise Repository. After that I proceed with 'apt update' followed by 'apt dist-upgrade' which results in the output attached above.

EDIT:

/dev/fuse on /etc/pve type fuse (rw,nosuid,nodev,relatime,user_id=0,group_id=0,default_permissions,allow_other)

Has been appended to the mount command after having done the 'apt update' and 'apt dist-upgrade'.

 

[fabian]

you have two pools mounted over eachother (or more specifically, you have two pools with a dataset for / and BOTH are mounted). rectify that situation (e.g., by booting a live disk / using the installer iso shell, importing the second pool and setting canmount=off or a different mountpoint for that problematic dataset)

 

[wy3QkoM7Kk3666ou2vd]

you have two pools mounted over eachother (or more specifically, you have two pools with a dataset for / and BOTH are mounted). rectify that situation (e.g., by booting a live disk / using the installer iso shell, importing the second pool and setting canmount=off or a different mountpoint for that problematic dataset)

Thank you for your help!