You are not logged in.

#1 2022-12-31 03:22:28

eom.dev
Member
Registered: 2022-02-11
Posts: 57

Timed out waiting for device

I have LVM on LUKS for my root partition:

/dev/sda
    /dev/sda1 (BIOS boot)
    /dev/sda2 (EFI)
    /dev/sda3
        luks-container-0eecb6fed94e
            volume-group-d04748d457a
                logical-volume-19430dBe2129 (root partition)

This drive boots on my PC and as a virtual machine, but when I try to boot it on a Mac, I get the following error:

[ TIME ] Timed out waiting for device xxx.
[DEPEND] Dependency failed for Cryptography Setup for luks-container-0eecb6fed94e.
[DEPEND] Dependency failed for Local Encrypted Volumes.
[ TIME ] Timed out waiting for device /dev/mapper /volume--group--d0474Bd4e57a-logical--volume--19430dBe2129.
[DEPEND] Dependency failed for File System Check on /dev/mapper/volume--group--d04748d457a-logical--volume--19430dBe2129,
[DEPEND] Dependency failed for /sysroot.
[DEPEND] Dependency failed for Initrd Root File System.
[DEPEND] Dependency failed for Mountpoints Configured in the Real Root.
[DEPEND] Dependency failed for Initrd Root Device.
You are in emergency mode.  After logging in type " journalctl -xb" to view
system logs, "systemctl reboot", "systemctl default" or "exit"
to boot into default mode.

Cannot open access to console, the root account is locked
See sulogin(8) man page for more details.
Press Enter to continue

Pressing Enter does nothing.  I boot the device as a virtual machine or as the host os on my desktop and check the journal command, but there are no logs of the event (why would there be?  the device is still encrypted...).  My fstab uses UUIDs to name devices, and I triple checked that fstab matches the actual device id (same with crypttab).  I've also confirmed that /etc/default/grub contains the correct rd.luks. id's, and that mkinitcpio.conf is configured correctly (though I did find this post mentioning an sd-lvm2 hook, whereas I have just lvm2, thought this was previously working).  Again, this is specific to booting on a MacBook Pro, as the drive boots under other conditions and I can also confirm that this device was able to boot on the Mac at a previous date.  The drive is labeled "EFI" when I select it for booting, but I have no further evidence that it is booting EFI (the drive supports both).

Offline

#2 2022-12-31 03:57:07

Slithery
Administrator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 5,776

Re: Timed out waiting for device

Why do you have both a BIOS boot partition and an EFI partition?

The former is only required for GPT drives booting in BIOS mode and the latter is only required for GPT drives booting in UEFI mode.
Your bootloader will only be configured to use one of these setups, not both of them.


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2022-12-31 20:16:06

eom.dev
Member
Registered: 2022-02-11
Posts: 57

Re: Timed out waiting for device

Slithery wrote:

Why do you have both a BIOS boot partition and an EFI partition?

The former is only required for GPT drives booting in BIOS mode and the latter is only required for GPT drives booting in UEFI mode.
Your bootloader will only be configured to use one of these setups, not both of them.

It is based on this wiki page as well as this one, which indicate a need for the BIOS partition.

Offline

#4 2023-01-19 12:48:23

eom.dev
Member
Registered: 2022-02-11
Posts: 57

Re: Timed out waiting for device

Still experiencing this issue on a mac - maybe I wasn't clear about having both BIOS and EFI partitions.  The external ssd is following 1.2.2 Hybrid UEFI GPT + BIOS GPT/MBR boot.  During the installation process, I actually run two grub install commands, as shown in the wiki:

grub-install --target=x86_64-efi --recheck --removable --efi-directory=/EFI_MOUNTPOINT --boot-directory=/DATA_MOUNTPOINT/boot

And for BIOS with:

# grub-install --target=i386-pc --recheck --boot-directory=/DATA_MOUNTPOINT/boot /dev/sdX

The end result should be able to boot UEFI (which it does successfully as the host on my dell desktop) and BIOS (which it also does successfully as a qemu virtual machine).  The issue only exists when I try to boot UEFI on a macbook.

Offline

Board footer

Powered by FluxBB