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
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
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
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
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
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
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
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
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
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
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 ,
>
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
Am 23.11.2016 um 04:20 schrieb Michael Biebl:
> Fwiw, I suspect your problem might be, that / and /usr are on different
> drives. initramfs-tools is not event based, so maybe sde (your HDD) is
> not available yet when it attempts to mount /usr.
Assuming this is the case, initramfs-tools should pro
Dear Michel,
/usr entry /etc/fstab (will attach) of my box was set below, not to mount:
> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
> rw,noatime,suid,dev,exec,auto,nouser,async 0 2
But, change to below, mount /usr and boot:
> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4 defau
Am 23.11.2016 um 10:02 schrieb K.Ohta:
> Dear Michel,
>
> /usr entry /etc/fstab (will attach) of my box was set below, not to mount:
>> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
>> rw,noatime,suid,dev,exec,auto,nouser,async 0 2
>
> But, change to below, mount /usr and boot:
>> UUID=
Am 23.11.2016 um 10:25 schrieb Michael Biebl:
> Can you edit /usr/share/initramfs-tools/init, go to line 232, add a line
> "sleep 10", then run "update-initramfs -u".
Choose a longer sleep, if you have a slow system/lots of hard
disks/controllers.
--
Why is it that all of the instruments seekin
Dear Michael,
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
Am 23.11.2016 um 11:25 schrieb K.Ohta:
> Dear Michael,
>
> 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
Sorry, I booted *older* fetab entry;
Not booting with,
>> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4 defaults,noatime 0
>> 2
Booting with uncommenting below line.
>>UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
>>rw,noatime,suid,dev,exec,auto,nouser,async 0 2
I will
Am 23.11.2016 um 11:41 schrieb Michael Biebl:
> Am 23.11.2016 um 11:25 schrieb K.Ohta:
>> Dear Michael,
>>
>> 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 :
>>> [
Dear Michael,
I change line 323 of /usr/share/initramfs-tools/init,
"sleep 15" (or another wait period),and uncomment below line
of /etc/fstab (and another /usr entry is commented)
>UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
>defaults,noatime 0 2
Then, booting
Am 23.11.2016 um 12:00 schrieb K.Ohta:
> Dear Michael,
> I change line 323 of /usr/share/initramfs-tools/init,
> "sleep 15" (or another wait period),and uncomment below line
> of /etc/fstab (and another /usr entry is commented)
>> UUID=c9d2e9cb-c214-4ca0-bdc9-40d39233e700 /usr ext4
Dear Michael,
On Wed, 23 Nov 2016 12:09:22 +0100
Michael Biebl wrote:
> Am 23.11.2016 um 12:00 schrieb K.Ohta:
> > Dear Michael,
> > I change line 323 of /usr/share/initramfs-tools/init,
> > "sleep 15" (or another wait period),and uncomment below line
> > of /etc/fstab (and another /usr entry i
Can you confirm that boot is successful after you remove the "sleep 15"
again and rebuild the initramfs via update-initramfs -u.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
I already removed "sleep 15" from /usr/share/initramfs-tools/init, and
re-built initramfs, booting was completed.
Sorry for lacking write.
Cheers,
Ohta
On Wed, 23 Nov 2016 13:26:22 +0100
Michael Biebl wrote:
> Can you confirm that boot is successful after you remove the "sleep
> 15" again and r
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):
Am 23.11.2016 um 14:30 schrieb Michael Biebl:
> 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.
>
Dear Michel,
Sorry for very later.
I test your patch of initramfs-tools, but, don't mount /usr with auto at entry
of fstab.
I tested below:
1.debuild initramfs after applying that patch and install packages.
2.Boot *without* auto and nouser with /usr entry at /etc/fstab.-> Success
3.Boot *with* a
Am 25.11.2016 um 05:18 schrieb K.Ohta:
> Dear Michel,
> Sorry for very later.
> I test your patch of initramfs-tools, but, don't mount /usr with auto at
> entry of fstab.
>
> I tested below:
> 1.debuild initramfs after applying that patch and install packages.
>> W: initramfs-tools-core: script-
Dear Michael,
On Fri, 25 Nov 2016 07:49:55 +0100
Michael Biebl wrote:
> How did you apply the patch? If you do it via "patch < $patch", you'll
> need to chmod +x hooks/mounts. The lintian warning should have been a
> clue.
Thanks. I missed this, re-check now.
Then, I re-built these packages, an
Am 25.11.2016 um 08:48 schrieb K.Ohta:
> Dear Michael,
>
> On Fri, 25 Nov 2016 07:49:55 +0100
> Michael Biebl wrote:
>
>> How did you apply the patch? If you do it via "patch < $patch", you'll
>> need to chmod +x hooks/mounts. The lintian warning should have been a
>> clue.
>
> Thanks. I missed
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
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
Processing control commands:
> reassign -1 initramfs-tools 0.125
Bug #845302 [systemd] systemd: 232-6:Failed to boot, makes kernel panic when
starting /sbin/init.
Bug reassigned from package 'systemd' to 'initramfs-tools'.
No longer marked as found in versions systemd/232-6.
Ignoring request to a
34 matches
Mail list logo
