Bug#813372: systemd: does not boot

[Ansgar Burchardt]

On Mon, 2016-02-01 at 14:06 +0100, Martin Pitt wrote:
> 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.

It's not okay.  It should be

  /dev/mmcblk1p5 / ext4        defaults 0 0

that is first the device, then the mount point.  This also explains
this error:

> The unit also shows this gem:
> 
>   Failed to check directory /dev/mmcblk1p5: Not a directory
> 
> which looks weird, I don't have an explanation.

Ansgar