kernel-packages team mailing list archive
-
kernel-packages team
-
Mailing list archive
-
Message #178717
[Bug 1581761] Re: Kernel panic - not syncing - Attempted to kill init
After multiple update-initramfs and kernel reinstalls instead of message
'fstype not found' I have 'can't open /dev/mapper/ubuntu-root no such
file'. However all the rest of the stacktrace seems to be similar as
already attached photo of the stacktrace. I check if I have installed
lvm2 and it is. Installed 3.16.x kernel (or 3.19.x) and situation didn't
changed.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1581761
Title:
Kernel panic - not syncing - Attempted to kill init
Status in linux package in Ubuntu:
Confirmed
Bug description:
Suddenly I can't boot as I receive 'kernel panic - not syncing - Attempted to kill init'. I tried to use previous kernel, then reinstall kernels but all that didn't help me. I have luks encrypted partition which contains multiple lvm with ext4 volumes. This was working since 14.04 was released so this not standard configuration should not cause this issue.
I am able to run live cd, then decrypt luks partition and mount volumes and chroot. All seems to be ok. I fsck lvm and all is ok.
I found similar issue https://bugs.launchpad.net/ubuntu/+source/cryptsetup/+bug/1273261 which suggest to try udev_settle. This didn't helped. I even entered sleep 5 (thus "sleeping for 5 secs" message on the stacktrace in the middle) but this didn't solve the issue. Maybe I enter this hack too early in the script?
No more idea... so mayday, mayday...
I attached photo of the stacktrace and report of 'apport-cli linux-generic'.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1581761/+subscriptions