My system (linux version 6.1.0-kali9-amd64 ([email protected]) (gcc-12 (Debian 12.2.0-14) 12.2.0, GNU ld (GNU Binutils for Debian) 2.40) #1 SMP PREEMPT_DYNAMIC Debian 6.1.27-1kali1 (2023-05-12))
stopped booting suddenly and I can't figure out the cause (have been using the system for quite some time just fine). Here's what it says during boot
Sometimes several of these lines appear (like 4 or 5 for docker), sometimes only postgresql@14 and not both versions (I don't remember why I installed two versions but it didn't interfere with any normal functionality).After these lines nothing happens, and I have nothing to do but to shut my ThinkpadT490 down. Now when I boot again I try to go into recovery mode in GRUB. It then asks me for my encryption password (just like during normal boot), which I successfully enter. Then some "OK" logs and then...
Then some more normal logs, then "Cannot open access to console, the root account is locked, please enter to continue" -> "reloading system manager configuration; starting default.target", some normal logs, and then it's just stuck. No access to console, no choice but to shut down again. I get that something seemingly screwed up with systemd but how and why (and why these particular services)? I was using the system normally pretty much this morning, didn't do anything potentially damaging besides some Internet browsing, and in the evening this happens. I don't think I ran any updates during last session as well. Only problematic things with my system I can think of over the last week is several days ago when I ran out of storage space during compiling (I guess swap was used and then I cleaned up a bit of unnecessary files and it seemingly didn't have any immediate effect on the system - I never ran out of space during an ongoing process that takes up gigabytes of space, though, so it was a useful experience in a sense, I guess?). Also haven't run updates in a long time and updated firefox a few days ago, but there weren't much dependencies iirc, certainly nothing related to docker, vmware, utmp and postgres. And again, it didn't affect the boot (why should it, indeed). Oh, and the last shutdown (before all these problems popped up) took longer than usual, a couple of minutes compared to the usual few seconds.
Here's a video of the failing boot process in recovery/single user mode: https://drop.infini.fr/r/MN5UYTG1gA#46cHi41euyTMGzFCdfupEdv14ke+pLYBkjy1QRkzrYE=
(the first batch of errors happens during "normal" boot, in the video you can see the UTMP one and the "root account locked" one)
Also, I can get shell access if I add rw init=/bin/bash parameter in boot options. Though if I understand correctly it boots without systemd so I can't really use any systemctl commands. And most partitions aren't mounted.
Any suggestions and help would be appreciated.
UPD: apparently the problem was that my /var was full, cleaned it up in rescue CD and the system booted.
stopped booting suddenly and I can't figure out the cause (have been using the system for quite some time just fine). Here's what it says during boot
Sometimes several of these lines appear (like 4 or 5 for docker), sometimes only postgresql@14 and not both versions (I don't remember why I installed two versions but it didn't interfere with any normal functionality).After these lines nothing happens, and I have nothing to do but to shut my ThinkpadT490 down. Now when I boot again I try to go into recovery mode in GRUB. It then asks me for my encryption password (just like during normal boot), which I successfully enter. Then some "OK" logs and then...
Then some more normal logs, then "Cannot open access to console, the root account is locked, please enter to continue" -> "reloading system manager configuration; starting default.target", some normal logs, and then it's just stuck. No access to console, no choice but to shut down again. I get that something seemingly screwed up with systemd but how and why (and why these particular services)? I was using the system normally pretty much this morning, didn't do anything potentially damaging besides some Internet browsing, and in the evening this happens. I don't think I ran any updates during last session as well. Only problematic things with my system I can think of over the last week is several days ago when I ran out of storage space during compiling (I guess swap was used and then I cleaned up a bit of unnecessary files and it seemingly didn't have any immediate effect on the system - I never ran out of space during an ongoing process that takes up gigabytes of space, though, so it was a useful experience in a sense, I guess?). Also haven't run updates in a long time and updated firefox a few days ago, but there weren't much dependencies iirc, certainly nothing related to docker, vmware, utmp and postgres. And again, it didn't affect the boot (why should it, indeed). Oh, and the last shutdown (before all these problems popped up) took longer than usual, a couple of minutes compared to the usual few seconds.
Here's a video of the failing boot process in recovery/single user mode: https://drop.infini.fr/r/MN5UYTG1gA#46cHi41euyTMGzFCdfupEdv14ke+pLYBkjy1QRkzrYE=
(the first batch of errors happens during "normal" boot, in the video you can see the UTMP one and the "root account locked" one)
Also, I can get shell access if I add rw init=/bin/bash parameter in boot options. Though if I understand correctly it boots without systemd so I can't really use any systemctl commands. And most partitions aren't mounted.
Any suggestions and help would be appreciated.
UPD: apparently the problem was that my /var was full, cleaned it up in rescue CD and the system booted.
Last edited:
