Arch Linux

ouafnico

Member

Registered: 2014-10-30

Posts: 14

[SOLVED] Encrypted disk boot: Different behavior

Hi all,

I've installed an Archlinux on an USB drive.
This installation is encrypted with cryptsetup.

When I boot a virtual machine (qemu), on the USB key, on boot, I correctly see the password prompt for unlock cryptroot, then the system boots (with UEFI).
When I boot the USB key on a physical computer, with UEFI, the boot start, then the system says "waiting 10 seconds for device ..." and never ask for the password, the system goes to a prompt and don't boot.

I dont understand why the boot is different.

I'm using UUID for the partitions, on the bootloader (systemd-boot), and cryptroot volumes, and fstab.

Any idea what"s wrong ?

Last edited by ouafnico (2017-05-16 17:57:10)

tom.ty89

Member

Registered: 2012-11-15

Posts: 897

Re: [SOLVED] Encrypted disk boot: Different behavior

The init wasn't able to find your cryptdevice. Could be of a few reasons, wrong UUID, necessary driver was not included in the initramfs.

Check your boot entry conf against lsblk -f outputs in Arch ISO environment. Also try boot with the fallback initramfs image. And make sure you included the encrypt hook.

ouafnico

Member

Registered: 2014-10-30

Posts: 14

Re: [SOLVED] Encrypted disk boot: Different behavior

Hi
The uuid is good, i've checked a lot of times, and encypted is on the initramfs image.
I don't think it's a configuration issue like this, becsuse it works on a VM, but not on the physical pc.
I will try the fallback image.

Any way to start with kind of debug or verbose mode ?

tom.ty89

Member

Registered: 2012-11-15

Posts: 897

Re: [SOLVED] Encrypted disk boot: Different behavior

Try to ls -l /dev/sd* or /dev/disk/by-uuid/* in the initramfs shell (the prompt in "the system goes to a prompt" ), or blkid.

R00KIE

Forum Fellow

From: Between a computer and a chair

Registered: 2008-09-14

Posts: 4,734

Re: [SOLVED] Encrypted disk boot: Different behavior

Have you tried booting with the fallback initramfs?

---

R00KIE
Tm90aGluZyB0byBzZWUgaGVyZSwgbW92ZSBhbG9uZy4K

ouafnico

Member

Registered: 2014-10-30

Posts: 14

Re: [SOLVED] Encrypted disk boot: Different behavior

I tried but I don"t have keyboard when I'm on the initramfs.

On mkinitcpio.conf I got as hooks : base udev autodetect keyboard keymap consolefont modconf block encrypt filesystems fsck".

ouafnico

Member

Registered: 2014-10-30

Posts: 14

Re: [SOLVED] Encrypted disk boot: Different behavior

When it fail, on initramfs, it seems there are no /dev/disk/by-uuid folder.
It's like the key is not detected, but it's correctly here because the bootloader starts...

blkid says nothing like empty.

Maybe something is missing for usb to work?

Ropid

Member

Registered: 2015-03-09

Posts: 1,069

Re: [SOLVED] Encrypted disk boot: Different behavior

Do you use a keyboard that can do "n-key rollover" through USB?

Last edited by Ropid (2017-05-16 12:54:15)

tom.ty89

Member

Registered: 2012-11-15

Posts: 897

Re: [SOLVED] Encrypted disk boot: Different behavior

Also try boot with the fallback initramfs image.

Have you tried booting with the fallback initramfs?

ouafnico

Member

Registered: 2014-10-30

Posts: 14

Re: [SOLVED] Encrypted disk boot: Different behavior

The problem is solved.
It's a problem with USB3.0.
I need to add xhci-pci and xhci-hcd" on modules on mkinitcpio.conf.

tom.ty89

Member

Registered: 2012-11-15

Posts: 897

Re: [SOLVED] Encrypted disk boot: Different behavior

Which should be included in the fallback initramfs image anyway.

Also you don't really need to list xhci-hcd there; when you have xhci-pci listed, xhci-hcd will also be pulled.

In my current mkinitcpio.conf:

...
MODULES="xhci-pci ehci-pci usb-storage sd_mod f2fs"
...
HOOKS="base udev encrypt fsck"
...

And I do not even have the fallback image generated

Last edited by tom.ty89 (2017-05-16 18:06:48)