After updating to the latest kernel I have found that during the service booting it keeps hanging on the network service throwing 'waiting for process: systemd-udevd' and 'waiting for process: udev-worker'. I can run my last kernel, 6.14.11-9-pve but I would like a permanent solution.
proxmox-kernel-7.0.2-6-pve failing network service
- Thread starter ArcWeaver
- Start date
I can easily obtain the working journal but how would I obtain the broken journal? It breaks the network so I can't ssh to copy it. I'm also away from the physical machine so I can't risk getting locked out again. Any suggestions?
You can cycle back by appending -1, -2, -3, etc.
For example,
For example,
journalctl -b -1 is the bootlog before the current boot.
Hi,
I might have missed something, but I don't see a smoking gun in the logs unfortunately. Could you also try kernel 6.17? That would already help determine when the regression was introduced.
Even better if you could test mainline kernel builds from Ubuntu between versions 6.14 and 7.0 (or after testing 6.17 about half that range): https://kernel.ubuntu.com/mainline/ You'll need the linux-image-unsigned and linux-modules packages for amd64.
Note that these do not include ZFS, so you can't test if you need that (as the root filesystem).
I might have missed something, but I don't see a smoking gun in the logs unfortunately. Could you also try kernel 6.17? That would already help determine when the regression was introduced.
Even better if you could test mainline kernel builds from Ubuntu between versions 6.14 and 7.0 (or after testing 6.17 about half that range): https://kernel.ubuntu.com/mainline/ You'll need the linux-image-unsigned and linux-modules packages for amd64.
Note that these do not include ZFS, so you can't test if you need that (as the root filesystem).
Seems like it is incomplete - but maybe that's because the system is still waiting on udev.
@ArcWeaver Are you using any Fusion-io SSDs?
Similar behavior indeed, but no reference to that in the 6.x bootlog.
Hopefully @ArcWeaver is able to collect some more/complete logs of problematic boots.
I suspect the udev is stalling. This log might be from one of my attempts and early shutdowns, my bad.
I can definitely try this but I need to be at my machine and I dont know when the next time that will be
Never heard of Fusion-io SSDs and I doubt my ssd is connected to one, though it is on a extend pcb. Again when I'm back at the machine I can take a look
I will do some more digging into other logs, so long as they save that far, and make a new upload when I get a chance