/dev/gpt-auto-root timed out

Hi all,

my system is not booting, because the auto root mount timed out and idk why. here’s some output.


BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0006,0004,0000,0005
Boot0000* Windows Boot Manager HD(4,GPT,89ef30f9-575f-49ab-843e-853576a6c044,0xbe270800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000061000100000010000000040000007fff0400
Boot0004* Linux Boot Manager HD(3,GPT,47a87148-4f53-46ec-9c79-d049fea1c9d8,0x2001800,0x200000)/File(\EFI\SYSTEMD\SYSTEMD-BOOTX64.EFI)
Boot0005* Windows Boot Manager HD(3,GPT,47a87148-4f53-46ec-9c79-d049fea1c9d8,0x2001800,0x200000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)0000424f
Boot0006* UEFI: Intenso Alu Line 8.07, Partition 1 PciRoot(0x0)/Pci(0x1,0x2)/Pci(0x0,0x0)/Pci(0x8,0x0)/Pci(0x0,0x3)/USB(3,0)/HD(1,GPT,bf3a7754-88ec-4539-bf9b-3ab1f66bcd3e,0x800,0x39cf7df)0000424f


UUID=29C7-DBD8 /efi vfat umask=0077 0 2
UUID=ba1c73ab-bea3-4459-a470-b85a64eef18a / ext4 defaults,noatime 0 1

lsblk -f

├─nvme0n1p1 swap 1 03f4d3ac-876b-4e6a-b7cb-e23d2f71c6fa
├─nvme0n1p2 ext4 1.0 72de97b2-c4b4-46d6-9533-1ce2e6284839
├─nvme0n1p3 vfat FAT32 29C7-DBD8

ls /efi/device-id/

6.6.10-arch1-1 6.6.11-1-lts

bootctl status

Firmware: UEFI 2.70 (American Megatrends 5.17)
Firmware Arch: x64
Secure Boot: disabled
TPM2 Support: yes
Measured UKI: no
Boot into FW: supported

Current Boot Loader:
Product: systemd-boot 254.6-2-arch
Features: ✓ Boot counting
✓ Menu timeout control
✓ One-shot menu timeout control
✓ Default entry control
✓ One-shot entry control
✓ Support for XBOOTLDR partition
✓ Support for passing random seed to OS
✓ Load drop-in drivers
✓ Support Type #1 sort-key field
✓ Support @saved pseudo-entry
✓ Support Type #1 devicetree field
✓ Enroll SecureBoot keys
✓ Retain SHIM protocols
✗ Menu can be disabled
✓ Boot loader sets ESP information
WARNING: The boot loader reports a different ESP UUID than detected (bf3a7754-88ec-4539-bf9b-3ab1f66bcd3e vs. 47a87148-4f53-46ec-9c79-d049fea1c9d8)!
ESP: /dev/disk/by-partuuid/bf3a7754-88ec-4539-bf9b-3ab1f66bcd3e

Random Seed:
System Token: set
Exists: yes

Available Boot Loaders on ESP:
ESP: /efi (/dev/disk/by-partuuid/47a87148-4f53-46ec-9c79-d049fea1c9d8)
File: ├─/EFI/systemd/systemd-bootx64.efi (systemd-boot 255.2-2-arch)
└─/EFI/BOOT/BOOTX64.EFI (systemd-boot 255.2-2-arch)

Boot Loaders Listed in EFI Variables:
Title: Linux Boot Manager
ID: 0x0004
Status: active, boot-order
Partition: /dev/disk/by-partuuid/47a87148-4f53-46ec-9c79-d049fea1c9d8

    Title: Windows Boot Manager
       ID: 0x0000
   Status: active, boot-order
Partition: /dev/disk/by-partuuid/89ef30f9-575f-49ab-843e-853576a6c044

    Title: Windows Boot Manager
       ID: 0x0005
   Status: active, boot-order
Partition: /dev/disk/by-partuuid/47a87148-4f53-46ec-9c79-d049fea1c9d8

Boot Loader Entries:
$BOOT: /efi (/dev/disk/by-partuuid/47a87148-4f53-46ec-9c79-d049fea1c9d8)
token: endeavouros

Default Boot Loader Entry:
type: Boot Loader Specification Type #1 (.conf)
title: EndeavourOS (6.6.10-arch1-1)
id: 261********-6.6.10-arch1-1.conf
source: /efi//loader/entries/261********-6.6.10-arch1-1.conf
sort-key: endeavouros-6.6.10-arch1-1
version: 6.6.10-arch1-1
machine-id: 261892fefa2e4c66aa35065bcd8a5532
linux: /efi/261********/id/6.6.10-arch1-1/linux
initrd: /efi//261********/6.6.10-arch1-1/initrd
options: archisobasedir=arch archisolabel=EOS_202311 cow_spacesize=10G copytoram=n nvidia nvidia-drm.modeset=1 nouveau.modeset=0 i915.modeset=1 radeon.mode>

I’d be greatful for some help. If you need further information please let me know.

Your UUID doesn’t match. Did you change your partition layout by adding a swap? (Missing from the fstab, but in the lsblk)?

UUID=03f4d3ac-876b-4e6a-b7cb-e23d2f71c6fa swap            swap    defaults   0 0
1 Like

yea I noticed the diverging UUID after the post too :man_facepalming:
I added the swap to the fstab aswell now it looks like this

# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=29C7-DBD8                            /efi      vfat    umask=0077 0 2
UUID=03f4d3ac-876b-4e6a-b7cb-e23d2f71c6fa none      swap    defaults 0 0 
UUID=72de97b2-c4b4-46d6-9533-1ce2e6284839 /         ext4    defaults,noatime 0 1 

Did a sudo reinstall-kernels but the issue persists.
To answer your question. I’ve got a new drive and installed the endeavourOS. Based on that I restored a backup which is working fine I just have to change the UUID of the esp, once I update to a new kernel it all goes down the river.

So something in the backup is overwriting something important in the current install, does that about sum it up?

If that is correct, it will be a really long job trying to find out what. How do you hold your backups? Can you restore selectively?

basically yes

I ended up just restoring my /home folder and kept on working from there. In the end it serves me as a great reminder on why to keep backups.

I don’t back up stuff that can easily be reinstalled, I do back up the configuration files though. Glad it is working.