Bug#808151: systemd: failed to start remount root and kernel file system

Michael Biebl biebl at debian.org
Fri Dec 18 02:15:15 GMT 2015

Am 17.12.2015 um 22:38 schrieb Michael Biebl:
> Am 17.12.2015 um 16:24 schrieb Frank B. Brokken:
>> This time the debug shell prompt was available at tty9, although booting
>> failed. And in line with my previous findings, systemd-analyze and journalctl
>> weren't available, as they live in /usr/bin, and /usr hadn't been mounted. But
> Well, /usr is mounted by the initramfs these days. So it should already
> be available when systemd is started. If that fails, this is a bug which
> needs to be addressed by initramfs-tools (or one of the hook scripts).
> It wasn't clear so far that /usr hasn't been mounted at all.
> Is /usr on LVM, RAID, etc?

I'm a bit confused by those logs. They show that sda5 have been mounted.

Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounting
ext3 file system using the ext4 subsystem
Dec 17 15:44:29 localhost.localdomain kernel: EXT4-fs (sda5): mounted
filesystem with ordered data mode. Opts: (null)

I figure /dev/sda5 is your /usr partition? Just to be sure, please
attach ls -la /dev/disk/by-uuid/

If so, I'm honestly puzzled why later on the binaries from /usr/bin are
not found.

Could you do another try and add "debug" to the kernel command line.
Then attach /run/initramfs/initramfs.debug and journalctl -alb (and
avoid mounting /usr manually on tty9)

Do you have any custom udev rules in /etc/udev/rules.d?


Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

More information about the Pkg-systemd-maintainers mailing list