[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.



On Wed, 23 Nov 2016 14:30:36 +0100 Michael Biebl <biebl@debian.org> wrote:
> Control: reassign -1 initramfs-tools 0.125
> 
> 
> Am 23.11.2016 um 11:25 schrieb K.Ohta:
> > Not mounted /usr and made kernel panic still longer sleep.
> > 
> > Then booting with "init=/bin/bash" , check dmesg (attached).
> > Below message was wrote when trying to mount /usr :
> >> [   15.958645] EXT4-fs (sde3): Unrecognized mount option "auto" or missing value
> > 
> > If this message is correct, mount program included by initramfs
> > has not recognized "auto" (or some another) option(s), regardless
> > /bin/mount (or /sbin/mount/ext4) recognize this option(s) :-(
> 
> 
> I'm going to reassign this to initramfs-tools as it uses mount
> implementations from either klibc-utils or busybox which are both
> incomplete and as a result, fail to mount /usr.
> 
> I decided against reassigning this to busybox and klibc-utils.
> I think it's preferable, if initramfs-tools simply uses the mount
> implementation from the real systemd, i.e. util-linux. This guarantees
> that we won't run into such problems again in the future.
> 
> The mount utility is tiny, all its library dependencies are already in
> the initramfs. Rebuilding the initramfs with mount from u-l increases
> the size by 17K.

I see.  fsck already pulls in libmount, so indeed there is little extra
cost to including mount.

> We would also have to make sure to use mount --move in
> /usr/share/initramfs-tools/init for /run, /sys and /proc
> 
> Ben, what's your take on this?

I'd like to sort out the busybox and klibc-utils implementations of
mount, but I must admit there isn't much point in using them any more.

Ben.
 
-- 
Ben Hutchings
When in doubt, use brute force. - Ken Thompson

Attachment: signature.asc
Description: This is a digitally signed message part


Reply to: