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

[K.Ohta]

Dear Michel and Martin,

Now, I checked older daemon.log (maybe booting with older than 232-4),
systemd prints below massage to log at starting.

--- quote ---
Nov  8 23:29:39 melchior systemd[1]: systemd 232 running in system
mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS
+KMOD +IDN)
--- end quote ---

Then, I checked recent daemon.log again, systemd (232-6) prints below
message to log.
--- quote ---
Nov 21 19:31:14 melchior systemd[1]: systemd 232 running in system
mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP
+LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS
+KMOD +IDN)
--- end quote ---

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}).

Basically, box with systemd should be same pertition both / and /usr
(I did not know this until today [1]), but some boxes already have 
different partitions both / and /usr ... these owner (include me) 
don't do easy to merge partions both / and /usr :-(

I think needs some preventives for this (or similar) issue, because some
older users/admins often miss to configure that their box to separate
both / and /usr ,they hope to be more robust box against physical hazard :-(

[1] http://freedesktop.org/wiki/Software/systemd/separate-usr-is-broken

Sorry for longer reply.
Ohta.

On Tue, 22 Nov 2016 14:41:00 +0100
Michael Biebl <biebl at debian.org> wrote:

> Am 22.11.2016 um 14:12 schrieb Michael Biebl:
> > Am 22.11.2016 um 13:12 schrieb K.Ohta:  
> >> Dear Martin,
> >>
> >> On Tue, 22 Nov 2016 12:36:32 +0100
> >> Martin Pitt <mpitt at debian.org> wrote:
> >>  
> >>> Control: tag -1 unreproducible moreinfo -wontfix
> >>>
> >>> Hello Ohta,
> >>>
> >>> K.Ohta [2016-11-22 19:56 +0900]:  
> >>>> I was always booting with initramfs, not booting without
> >>>> initramfs any time.    
> >>>
> >>> So it seems the initramfs did not actually mount /usr as it's
> >>> supposed to. Can you please boot with "init=/bin/bash" on the
> >>> kernel command line, and check if /usr is mounted in the shell
> >>> that you get?  
> >>
> >> My box not mount /usr (to /root/usr) before running /sbin/init.you
> >> are right.  
> > 
> > Can you share more details about your partition scheme.
> > Do you use LVM, LUKS/cryptsetup, btrfs etc?  
> 
> 
> Fwiw, I have a test-vm, which uses a split /usr partition, which boots
> fine. It's a simple ext4 partition, no lvm or anything.
> 
> 
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 228 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20161123/e92769b4/attachment-0002.sig>