UEFI: encrypt hook device not found. Works In Legacy mode w/ interupt

pathann · 2018-07-22 07:42:34

Hello,

Ill try to explain as clearly as I can. There have been similar issues posted, but none quite like this one, as far as I could find. Also not sure if it is strictly an installation problem, but seems to be around the same type of topics of boot and config problems.

All of this is on a Dell XPS 15 9560.

My system has been running for over a year problem free, and then one day a few weeks ago it just stopped booting.

The problem in short is that I can't boot in UEFI mode. The encrypt hook doesn't recognize the device (device not found) and drops to an emergency shell.

If I set the bios to boot in legacy mode, and interrupt the boot process with F12, and choose UEFI mode(Linux boot manager) in the boot options menu, encrypt hook finds device, I enter password and all works perfectly.

In straight legacy mode, it also doesn't work, but that is expected.

I am thinking it has something to do with my bios config, as if for some reason in straight UEFI mode the encrypted block is not visible. But what I can't figure out is how can it work in one way, but not the other. Since I am interrupting the boot, and choosing UEFI in the boot options menu.

I have tried re-ordering some of the HOOKS, same result.

I have tried the boot options cryptdevice=UUID and PARTUUID. Same. I read somewhere that adding rootdelay might help, but I'm not sure it's what I need since without cryptdevice passing, there is no rootdevice. Also not sure that using luks.uuid rather than cryptdevice would be any different. But I may be wrong.

Any ideas? Or even where to start poking? I think its somewhere in the bios config somewhere, and will do while waiting for input.

Here is the config.

First few lines of lshw (while booted with via f12->UEFI)

description: Notebook
product: XPS 15 9560 (07BE)
vendor: Dell Inc.
serial: <>
width: 4294967295 bits
capabilities: smbios-3.0 dmi-3.0 smp vsyscall32
configuration: boot=normal chassis=notebook family=Latitude sku=07BE uuid=44454C4C-4B00-104E-8048-CAC04F594632

/boot/loader/entries/arch.conf

title Arch Linux Encrypted LVM
linux /vmlinuz-linux
initrd /intel-ucode.img
initrd /initramfs-linux.img
options cryptdevice=PARTUUID=3fd51ec7-c50c-49b9-b71d-641f6397e437:hoxton root=/dev/mapper/hoxton-root rw

/etc/mkinitcpio.conf (hooks only)

HOOKS="base udev block autodetect modconf keyboard encrypt lvm2 filesystems fsck"

/etc/fstab

# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/mapper/hoxton-root
UUID=b185cc94-745f-4de9-8ba6-184f891a21a6	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/mapper/hoxton-home
UUID=807c2f8b-307c-4151-b92d-aa9712e9c1cc	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/nvme0n1p1 LABEL=ESP
UUID=C4EE-9178      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro	0 2

# /dev/mapper/hoxton-swap
UUID=c2436475-305a-4958-938b-02cd09f3fc36	none      	swap      	defaults  	0 0

blkid

/dev/nvme0n1p1: LABEL="ESP" UUID="C4EE-9178" TYPE="vfat" PARTUUID="8db98789-0af3-413e-8806-f08701bfed05"
/dev/nvme0n1p2: UUID="9f4db370-ec20-4e5f-951c-aa1cc31da236" TYPE="crypto_LUKS" PARTUUID="3fd51ec7-c50c-49b9-b71d-641f6397e437"
/dev/nvme0n1: PTUUID="057228bf-6689-4d76-9b4c-7eae2bf83a5e" PTTYPE="gpt"
/dev/mapper/hoxton: UUID="5fy5ur-qtwm-K1am-ag3B-NzGF-tfdd-PAwujz" TYPE="LVM2_member"
/dev/mapper/hoxton-swap: UUID="c2436475-305a-4958-938b-02cd09f3fc36" TYPE="swap"
/dev/mapper/hoxton-root: UUID="b185cc94-745f-4de9-8ba6-184f891a21a6" TYPE="ext4"
/dev/mapper/hoxton-home: UUID="807c2f8b-307c-4151-b92d-aa9712e9c1cc" TYPE="ext4"

Thanks in advance for any ideas.

jasonwryan · 2018-07-22 08:08:21

Not an Installation issue, moving to Kernel and Hardware.

Arch Linux

#1 2018-07-22 07:42:34

UEFI: encrypt hook device not found. Works In Legacy mode w/ interupt

#2 2018-07-22 08:08:21

Re: UEFI: encrypt hook device not found. Works In Legacy mode w/ interupt

Board footer