Bug#813372: systemd: does not boot

[Martin Pitt]

Control: tag -1 moreinfo
Control: retitle -1 fails to mount rootfs on mmcblk1p5 during boot

Hello Michal,

Michal Suchanek [2016-02-01 13:36 +0100]:
> Attaching the output of journalctl -xb from the recovery shell on failed boot.

This is the culprit:

Feb 01 13:18:41 chromebook systemd[1]: dev-mmcblk1p5.mount: Mount process exited, code=exited status=32
Feb 01 13:18:41 chromebook systemd[1]: Failed to mount /dev/mmcblk1p5.

Your fstab has

  / /dev/mmcblk1p5 ext4        defaults 0 0

which looks ok at first, the kernel does detect /dev/mmcblk1p5. "man
mount" says that exit code 32 is "mount failure", so that doesn't help
much. Also, the root file system is quite obviously already mounted.

The unit also shows this gem:

  Failed to check directory /dev/mmcblk1p5: Not a directory

which looks weird, I don't have an explanation.

In the rescue shell, can you get the output of

  systemctl status dev-mmcblk1p5.mount

?

Thanks,

Martin

-- 
Martin Pitt                        | http://www.piware.de
Ubuntu Developer (www.ubuntu.com)  | Debian Developer  (www.debian.org)