Re: unable to boot with systemd (works with sysvinit)
On Sat, Jan 10, 2015 at 12:33:36PM +0100, Johannes Schauer wrote:
>
> I'm not subscribed, so please keep me CC-ed.
>
> I'm unable to boot my laptop with systemd which worked before. I'm unable to
> tell the changes I made since the last time it worked because according to my
> uptime, the last time I rebooted was September last year.
I see you already have a bug report, so including it for the list:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758808
(Also for reference, your older bug report, where you first saw this issue,
indicates that this might have arisen between systemd 204-14 and systemd 208-6:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=755581)
> The output of `journalctl -xb` in the systemd rescue console is here:
>
> https://mister-muffin.de/p/AabX.txt
>
> My system contains up-to-date package versions with Debian Jessie. This means
> I'm running systemd and udev version 215-8.
>
> Since the problem seems to be related to a failed fsck job, according to above
> log, here is my fstab (minus comment lines):
It looks to me like it's not fsck as much as not being able to access
/boot, /home and swap. If you want to check this, you can probably tell systemd
not to run fsck at boot. (How to do this was the topic of some recent threads
on debian-user, but I didn't follow them so I can't help with that.)
> proc /proc proc defaults 0 0
> /dev/mapper/volumegroup-root / ext4 errors=remount-ro 0 1
> UUID=ac034ff5-d28a-4ad1-8bac-97d554395e3e /boot ext2 defaults 0 2
> /dev/mapper/volumegroup-home /home ext4 defaults 0 2
> /dev/mapper/volumegroup-swap none swap sw 0 0
> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0
> cgroup /sys/fs/cgroup cgroup defaults 0 0
> tmpfs /tmp tmpfs nodev,nosuid,size=8G 0 0
> tmpfs /run tmpfs nodev,nosuid,size=8G 0 0
>
> I also booted my system into the initramfs busybox by passing "break" to the
> kernel command line and did an `fsck -f` on my root and home partitions and
> everything seems to be clean.
>
> Booting my laptop with sysvinit instead works fine, so my fstab should be
> correct.
>
> How can I further debug this problem? The journalctl output seems inconclusive.
I wonder if the problem is with decryption (under systemd), which then leads
to the timeout when accessing everything inside it? Unfortunately, I don't
know enough to suggest a good way to test this.
Reply to: