eudev startup issue after upgrade

[Member wildstar84]

I rebooted my system today for the first time in a couple of weeks and couldn’t type a login into Slim/X (system completely frozen: no typee, no Ctl-Alt-Fn => console, no nothin’ except hard power-cycle! Traced pbm. down to eudev NOT starting from /etc/rcS.d. I tried renaming S02udev to S99udev there to make it start as late as possible and rebooted into single-user mode. This did NOT start it either, even though I could immediately start it up manually (from the console) and then telinit 5 and login to Slim/X normally, but trying to BOOT into normal runlevel 5 – no udev, no dice! I recall running into this a year or so on an old box at someone elses house and, assuming disk corruption/old STRETCH install and not having time to look further into it, ended up hacking up /etc/init.d/slim and adding the following code at the top to test for the existance of a device that udev creates on startup (/dev/userio), and failing that test, starting eudev manually in slim itself to ensure that it is running. This “hack” seems to get everything working again!:

#JWT:ADDED 20211129 B/C /dev/rcS.d/S02udev SEEMS TO NOW *NOT* START THE UDEV
#DAEMON RUNNING ANYMORE AND UDEV *MUST* BE RUNNING OR
#SLIM/X COME UP TOTALLY LOCKED UP?!!!!!!!
#(THE DEVICE "userio" SEEMS TO BE CREATED WHEN UDEV RUNS, SO WE CHECK FOR THAT!):
test -c "/dev/userio" || /etc/init.d/udev start

The only seemingly-related update between last good boot and currently was:

elogind (246.10-2.0antix4) to 246.10-3.0antix1

I’ve forced fsck, and don’t see any corruption.
I’m currently running bookworm/testing

Any ideas?

[Forum Admin anticapitalista]

Helpful

Up

0

::

Check your repos are up to date
Check /etc/init.d/udev exists and is executable
If it exists, remove any /etc/init.d/udev.old (or whatever) files

Boot with your hack and try reinstalling eudev

sudo apt install --reinstall eudev

Philosophers have interpreted the world in many ways; the point is to change it.

antiX with runit - leaner and meaner.

[Member wildstar84]

Helpful

Up

0

::

SOLVED! That was close – I had already tried that. What actually fixed it was apt-get reinstall elogind.

Thanks,

Jim

[Author]

Posts