Bug#813372: systemd: does not boot

[Suchánek Michal]

> -----Original Message-----
> From: Ansgar Burchardt [mailto:ansgar at debian.org]
> Sent: Monday, February 01, 2016 2:27 PM
> To: 813372 at bugs.debian.org; Suchánek Michal
> Subject: Re: Bug#813372: systemd: does not boot
> 
> 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

Thanks for spotting this. Neither of the alternative init systems cares. Systemd even says it enabled swap although it is equally broken /o\

Michal

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4733 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20160201/b96f0516/attachment-0002.bin>