You are not logged in.

#1 2018-03-23 21:03:29

csingley
Member
Registered: 2011-05-19
Posts: 8

LVM on LUKS: "Failed to execute /init"

So I updated an existing (working) installation in LVM on LUKS, pretty much identical to this setup:

https://wiki.archlinux.org/index.php/Dm … VM_on_LUKS

Now it's fried; when the boot process gets to loading the initramfs I get a kernel panic: "No working init found".

The installation is still intact; from the installation medium I can `cryptsetup open` and everything's there.

I've got this in my /etc/mkinitcpio.conf:

HOOKS=(base udev autodetect modconf keyboard keymap block encrypt lvm2 filesystems fsck)

Using that, I just went ahead and reinstalled linux through pacman; the post-installation hooks generate the initramfs.

I've got this in my /etc/default/grub:

GRUB_ENABLE_CRYPTODISK=y
GRUB_CMDLINE_LINUX="cryptdevice=UUID=<uuid>:lvm root=/dev/mapper/MyVol-root"

The device UUID is correct per /dev/disk/by-uuid/ .

Then I run grub-mkconfig, which doesn't complain.  Upon booting, the /boot/grub/grub.cfg seems to load fine, picking up those configs from /etc/default/grub.  Continuing with the boot, it finds linux, finds the initrams, loads it... and wipes out, complaining about no init.

What am I doing wrong?

Offline

#2 2018-03-23 21:16:48

jasonwryan
Anarchist
From: .nz
Registered: 2009-05-09
Posts: 30,426
Website

Re: LVM on LUKS: "Failed to execute /init"

Not an Installation issue, moving to NC...


Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

Offline

#3 2018-03-26 16:00:10

csingley
Member
Registered: 2011-05-19
Posts: 8

Re: LVM on LUKS: "Failed to execute /init"

Browsing the forum shows that many users have recently been experiencing problems with LUKS.  It's difficult to troubleshoot the precise cause in my case, because cryptsetup failing means the system won't boot.

If anyone else experiences a similar problem and is searching for an answer, the only way I've been able to restore to a working state is to roll back the entire system to a date prior to the update that b0rked it.  This fixed it without any configuration changes.

https://wiki.archlinux.org/index.php/Ar … cific_date

I hope to get some time to zero in the exact package(s) introducing the bug.

Offline

Board footer

Powered by FluxBB