Hello, I just notice that if I don’t have my usb stick plugged in, my pc will just get stuck during boot.
I’m not so sure but I think it started with the broken grub update in august, which required manual intervention.
System info
Can we see the output of sudo efibootmgr
Here you go.
BootCurrent: 0001
Timeout: 1 seconds
BootOrder: 0001,000B,000D,0000,000C
Boot0000 Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fc3000000080000008b0053005400310030003000300044004d003000300033002d003100450052003100360032000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600030101010600010003120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce620002000200020002000200020002000200020002000200034005300310059003200510030004c0000007fff04000000424f00004e4fb30000000800000083004e0056004d00450020005300530044002000320035003600470042000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a00000000010106000101010106000000031710000100000000000100000000007fff040001043000ef47642dc93ba041ac194d51d01b4ce6320030003200300031003100300034003000300036003500330000007fff04000000424f
Boot0001* endeavouros HD(1,GPT,8315c795-8cf9-964f-84db-2f0008808fdc,0x1000,0x100000)/File(\EFI\ENDEAVOUROS\GRUBX64.EFI)
Boot000B* UEFI OS HD(1,GPT,8315c795-8cf9-964f-84db-2f0008808fdc,0x1000,0x100000)/File(\EFI\BOOT\BOOTX64.EFI)0000424f
Boot000C USB KEY BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0b00)0000474f00004e4fc9000000080000008500560065006e0064006f00720043006f00500072006f00640075006300740043006f0064006500200032002e00300030000000050109000200000000010416008b12e85cec2cf040837280640e3dc8580b007fff040002010c00d041030a000000000101060003010101060000000305060007007fff040001043c00ef47642dc93ba041ac194d51d01b4ce6360036003400390034003100310033003000350036003800300030003300370038003400340000007fff04000000424f
Boot000D* UEFI: VendorCoProductCode 2.00, Partition 2 PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(7,0)/HD(2,GPT,31323032-3830-4632-b232-303331313431,0x3a80bc,0x31000)0000424f
It looks like you need to switch “endeavouros” to the highest priority. You can do this with efibootmgr or just go into your BIOS and change it there.
Oh, I’ll try this. Thanks!
Isn’t endeavouros already first in my boot order?
Ugh. Yes, you are right.
Can we see the output of these commands
lsblk -o name,type,fstype,size,mountpoint,uuid
cat /etc/fstab
NAME TYPE FSTYPE SIZE MOUNTPOINT UUID
sda disk 931,5G
└─sda1 part ext4 931,5G /run/media/a 5fd00c25-0bc8-4baa-8175-53f203f6281c
nvme0n1 disk 238,5G
├─nvme0n1p1 part vfat 512M /boot/efi 3A1A-00BE
└─nvme0n1p2 part ext4 238G / 28dae04c-15c9-4df9-a042-5905138656ef
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
UUID=3A1A-00BE /boot/efi vfat umask=0077 0 2
UUID=28dae04c-15c9-4df9-a042-5905138656ef / ext4 defaults,noatime 0 1
@dalto Could it be because his grub was installed inside his USB stick? I can think of no other sensible reason for his PC to only boot when his USB is plugged in.
Oops, efibootmgr uses partition UUIDs.
We need this command.
lsblk -o name,type,fstype,size,mountpoint,partuuid
Either that, or it is trying to mount it during the boot process.
NAME TYPE FSTYPE SIZE MOUNTPOINT PARTUUID
sda disk 931,5G
└─sda1 part ext4 931,5G /run/media/andrelbc/5fd00c25-0bc8-4baa-8175-53f203f6281c 872e5bc6-01
nvme0n1 disk 238,5G
├─nvme0n1p1 part vfat 512M /boot/efi 8315c795-8cf9-964f-84db-2f0008808fdc
└─nvme0n1p2 part ext4 238G / c60493e7-5244-0544-b530-50d0428b9814
I can also boot if I go through the boot menu and choose the endavouros drive.
Ah…that sounds like perhaps a bios/firmware issue.
What happens if you change the endeavouros to default in your bios?
Also, what happens if you pull the drive out? What is the actual error?
If I don’t have the usb stick plugged in, the only way I can boot is if I enter the boot menu by pressing F11, otherwise it just freezes in the motherboard logo.
I think in the bios setup it shows the same boot order, which is the endeavouros first.
This is exactly what happens…