Hello,
Have a Debian 12 with Kernel 6.1.0.9-686-pae which suddenly stopped working (black screen, couldn't ssh) and therefore I had to re-boot it. After some tries in which GRUB was started but then nothing else happened (not even in recovery mode, black screen again with a blinking cursor) it finally happened to continue but then it stops loading all initial modules/services/whatever and stops with a message :
Google and reviewed journalctl -xb but really don't know what I'm looking for in there. This said, I found any of the messages suspicious:
Googled again and restarted journal service with "systemctl restart systemd.journald" but no result.
Rebooted several times as well in order to get drives checked, but nothing happened either.
Also found any discussion in which the problem was related to bus issues, so I halted instead of rebooted and got the following message:
But none of the solution in the discussions worked either, so not sure what to target and Google about in the end.
Can someone bring some light? Would appreciate![:-)]( "Smile")
BR,
d.
Have a Debian 12 with Kernel 6.1.0.9-686-pae which suddenly stopped working (black screen, couldn't ssh) and therefore I had to re-boot it. After some tries in which GRUB was started but then nothing else happened (not even in recovery mode, black screen again with a blinking cursor) it finally happened to continue but then it stops loading all initial modules/services/whatever and stops with a message :
Code:
You are emergency mode! After logging in,type "journalctl -xb" to viewsystem logs, "systemctl reboot" to reboot, "systemctl default" or ^Dto try again to boot into default mode.Give root password for maintainence(or type control-D to continue):Code:
File /var/log/journal/balbalbalbla/system.journal corrupted or unclearly shut down, renaming and replacing.mounting ext3 file system using the ext4 subsystemext3 filesystem being mounted at /tmp supports timestamps until 2038Rebooted several times as well in order to get drives checked, but nothing happened either.
Also found any discussion in which the problem was related to bus issues, so I halted instead of rebooted and got the following message:
Code:
Failed to connect to bus: No such file or directoryCan someone bring some light? Would appreciate
BR,
d.
Statistics: Posted by dbip — 2023-12-23 16:32 — Replies 1 — Views 48