You are not logged in.
Hi everyone, when I upgrade to any kernel above the 4.9.78-1 lts (which is pretty old at this point)
The systemd just hangs at "starting version 237" during boot.
I have read a few threads on this that have something to do with the elevator type being used
https://bbs.archlinux.org/viewtopic.php?id=228693
... and that didn't seem to apply to me, as I am using noop with cfq on an SSD as my boot device.
IE, I am not using bfq or kyber
~ $ cat /sys/block/sdb/queue/scheduler
noop [deadline] cfqSo far, I am not sure what to do to diagnose the problem.
I followed what was mentioned in that thread above, using journalctl to see if I could find anything... but it doesn't even seem to record the failed boots
~ $ journalctl --list-boots -q | grep "Mon 2018-03-05"
-1 6a8293c998f3440cbc13d644d6fb80f3 Mon 2018-03-05 21:37:03 PST—Mon 2018-03-05 21:50:02 PST
0 cd69a646a0f34dcf950152fda1dc39d9 Mon 2018-03-05 21:51:34 PST—Mon 2018-03-05 21:56:35 PSTbut... the boot which I tried and failed to perform was at ~21:50:30
-1 in that list was a successful boot with the old kernel I am using, and 0 is the current boot I am in as I write this... on the old kernel.
I also can't seem to get a shell, regardless of what I pass as a kernel param.
I haven't tried the solution (to get a shell) mentioned in that linked thread, because I don't understand what it is doing, and didn't want to make any change I didn't understand
Where should I begin here? I am pretty much at a total loss, as I haven't ever had to diagnose a problem like this one before.
Any help is greatly appreciated :-)
Last edited by liefswanson (2018-03-06 06:13:34)
Offline
Try to generate more output: https://wiki.archlinux.org/index.php/Ge … t_problems (in addition to removing boot parameters like quiet or splash, of course)
Offline
okay thanks seth! I will report back as soon as I get a chance to try and force some more output. Really busy, hopefully you will be available for more help once I manage to get around to this in a day or two.
Offline