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

2016-11-22 Thread Michael Biebl
Am 23.11.2016 um 00:37 schrieb K.Ohta: > 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 > /boo

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

2016-11-22 Thread Felipe Sateler
On 22 November 2016 at 20:37, K.Ohta 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 , >

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

2016-11-22 Thread K.Ohta
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

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

2016-11-22 Thread Michael Biebl
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

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

2016-11-22 Thread 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 +LIBCR

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

2016-11-22 Thread Michael Biebl
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 wrote: >> >>> Control: tag -1 unreproducible moreinfo -wontfix >>> >>> Hello Ohta, >>> >>> K.Ohta [2016-11-22 19:56 +0900]: I was alwa

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

2016-11-22 Thread 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 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

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

2016-11-22 Thread K.Ohta
Dear Martin, On Tue, 22 Nov 2016 12:36:32 +0100 Martin Pitt 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 n

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

2016-11-22 Thread Michael Biebl
Am 22.11.2016 um 11:56 schrieb K.Ohta: > Hello Martin, > Thank you for reply. > > I was always booting with initramfs, not booting without initramfs any time. > > But, booted after upgrading systemd to 232-6 (or liblz4 to latest?) , > kernel panic happened with message, "liblz4.so not found". > S

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

2016-11-22 Thread Martin Pitt
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

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

2016-11-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 unreproducible moreinfo -wontfix Bug #845302 [systemd] systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init. Added tag(s) unreproducible and moreinfo. Bug #845302 [systemd] systemd: 232-6:Failed to boot, makes kernel panic when starting

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

2016-11-22 Thread Debian Bug Tracking System
Processing control commands: > tag -1 wontfix Bug #845302 [systemd] systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init. Added tag(s) wontfix. -- 845302: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845302 Debian Bug Tracking System Contact ow...@bugs.debian.org with

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

2016-11-22 Thread Martin Pitt
Control: tag -1 wontfix Hello Kyuma, Kyuma Ohta [2016-11-22 18:21 +0900]: > When update with systemd 232-6 and reboot , if separate partitions both / and > /usr, Having a separate /usr partition without using an initrd hasn't ever been officially supported, and it actually stopped working severa

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

2016-11-22 Thread K.Ohta
Hello Martin, Thank you for reply. I was always booting with initramfs, not booting without initramfs any time. But, booted after upgrading systemd to 232-6 (or liblz4 to latest?) , kernel panic happened with message, "liblz4.so not found". So, I made copy liblz4 to /lib/${ARCH} and made symlink