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

[Felipe Sateler]

On 22 November 2016 at 20:37, K.Ohta <whatisthis.sowhat at gmail.com> wrote:
> Good morning, Michel,
>
>> What we don't know is, why /usr was not mounted for you by the
>> initramfs. It should do that automatically.
>
> This is caused by design-specification of systemd.
> Summing up of below quote written by author of systemd ,
> 1.This issue is caused by design of systemd, Mainly to reduce security risk.
> 2. *THIS ISSUE WILL NOT FIX, SHOULD CHANGE PARTITION*.

You misunderstand. The solution is not to change partition, but to
have /usr be mounted by the initramfs. You should not need to
repartition.

>
> I wonder I failed to boot without liblz4 in /lib/${ARCH} , but in your simulation VM,
> booting without liblz4 in /lib/${ARCH}.

Exactly, that is what we are trying to discover.

> My idea is, adding new kernel command line parameters; this is bypass to systemd: systemd.{foo}
> i.e: {foo} is usr_mount_dev and usr_mount_uuid , arg = device name ore UUID.
> If this parameter entry will be set, mount ${ARG} block-device to /usr directory.

Unfortunately passing parameters to systemd is already too late: by
the time the kernel tries to execute systemd /usr should already be
mounted. If it isn't, the problems you describe occur.

To repeat: this is not a problem that can be solved by systemd the
program, as the problem occurs *prior* to it being executed.

>
> On Tue, 22 Nov 2016 18:15:49 +0100
> Michael Biebl <biebl at debian.org> wrote:
>
>> Am 22.11.2016 um 18:01 schrieb K.Ohta:
>> > Older systemd was built without liblz4, and liblz4 places
>> > at /usr/lib/${ARCH} , problems of this my report had not happened.
>> > But, now, systemd (maybe later than 232-5) is built with liblz4,
>> > problem has happened (due to not placing liblz4 at /lib/${ARCH}).
>>
>> We are very well aware that liblz4 is in /usr and that this is a new
>> dependency.
>>
>> What we don't know is, why /usr was not mounted for you by the
>> initramfs. It should do that automatically.
>
> I'm using initramfs-tools 0.125 to assemble initramfs.
>
>>
>> Can you provide the requested information, about your partitioning
>> scheme: LVM, cryptsetup/LUKS, btrfs etc.
>
> Pertitioning of core filesystems are a SSD and HDD.(Will replace HDD to another SSD)
> SSD: ADATA 240GiB (/dev/sde)
> HDD: Toshiba 3TiB (/dev/sdd)
> Partition type of both disks are GPT.
>
> Partition structure:
> /      : sdd3, #8300, EXT4, 30GiB
> /boot  : sde2, #8300, EXT4, 7.9Gib
> /usr   : sde3, #8300, EXT4, 79.2GiB
> /home  : sde4, #8300, EXT4, 134.0GiB
> /var   : sdd5, #8300, XFS, 76.8GiB

This is not the contents of /etc/fstab. Could you please attach that file?

-- 

Saludos,
Felipe Sateler