You are not logged in.
Tried hibernating without a swap (by mistake, I forgot that I don't use a swap nowadays!), now systemd can't complete booting.
But, if I remove the init=whatever/systemd line from the bootloader, the old init system does its work nicely.. (though that's a poor permanent solution. )
I have saved the 1000+ line journalctl log, but have no idea where to start looking for the problem.
https://www.pastee.org/j3htz
It seems to be something to do with filesystem errors, as the following line is the last shown by systemd before stopping.
Nov 11 20:19:45 manasijd systemd-fsck[413]: Home: clean, 85694/1221600 files, 4430911/4883456 blocksBut running fsck(after unmounting the partitions) from the 'emergency mode' systemd drops me into, the results come up clean.
Any idea what can be wrong, or what exactly to look for in the log ?
Last edited by manasij7479 (2012-11-12 11:54:55)
Offline
Seems like I was correct about the filesystem problem @ /home .
Backed up the home folder and nuked the ext4 partition and created a new btrfs in its place.
Everything seems to be fine now, after copying back the folder (few issues with kde not cooperating, but nothing major) .
Btw, can anyone try to replicate this on a 'torture' rig or a virtual machine, seems to be a pretty important bug ?
Offline