Hello All,
I have a problem with my endavouros, it does not boot and i cant provide any information on screen.
My system is nvme1 endavouros, nvme2 windows, the bios boots endavouros by default and the bootloader systemd gives me the options lts, zen and windows.
What did I do, update with yay yesterday and that is it. Afterwards it tries to boot, shut down and booted windows which is odd. Anyways I removed my windows drive, because we dont want the mess with that and so it would not boot windows and i can potentially see some message on screen and I cant switch up the drives. Surprisingly with the windows drive removed i now have a windows recover screen.
So now I have 1 or potentially 2 issues; the initial issue which prevented the system to boot and the second because if I would have a bootloader issue with the windows shit, I would have had see it earlier where is could not boot.
Well I dont really have an good idea how to get my eos install working again. I think first to fix the bootloader after which the initial problem becomes visible, maybe
Thanks for helping,
From live environment,
sudo lsblk -f
sudo mount /dev/nvme0n1p2 /mnt
sudo cat /mnt/etc/fstab
sudo mount /dev/nvme0n1p1 /mnt/efi
sudo arch-chroot /mnt
yay
bootctl install
reinstall-kernels
Which did not work?
sudo bootctl install --path=/mnt/efi
efibootmgr
pacman -S linux linux-headers
efibootmgr, shows and linux boot entry
cactux
November 19, 2025, 7:40pm
3
Can you post the ouput of some commands from the live usb?
lsblk -f
sudo parted -l
efibootmgr
lsblk -f
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
loop0 squashfs 4.0
sda
└─sda1 ext4 1.0 Backup 33d4258d-179e-4dbe-99c1-fcfe2285e6aa
sdb
├─sdb1 exfat 1.0 Ventoy 4E21-0000
│ └─ventoy iso9660 Joliet Extension EOS_202503 2025-03-19-11-30-07-00
└─sdb2 vfat FAT16 VTOYEFI 223C-F3F8
sr0
nvme0n1
├─nvme0n1p1 vfat FAT32 8467-7159 621.8M 39% /efi
└─nvme0n1p2 ext4 1.0 endeavouros 1f2c6774-29b5-4fcb-8c9e-80aba42ffe87 526.6G 37% /
sudo parted -l
Model: ATA CT250MX500SSD1 (scsi)
Disk /dev/sda: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 17.4kB 250GB 250GB ext4
Model: INTEL SS DPEKKW256G7 (scsi)
Disk /dev/sdb: 256GB
Sector size (logical/physical): 512B/4096B
Partition Table: msdos
Disk Flags:
Number Start End Size Type File system Flags
1 1049kB 256GB 256GB primary boot
2 256GB 256GB 33.6MB primary fat16 esp
Model: Samsung SSD 980 1TB (nvme)
Disk /dev/nvme0n1: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 2097kB 1076MB 1074MB fat32 EFI boot, esp
2 1076MB 1000GB 999GB ext4 endeavouros
efibootmgr
BootCurrent: 0006
Timeout: 1 seconds
BootOrder: 0000,0004,0006,0001,0002,0005
Boot0000* Linux Boot Manager HD(1,GPT,0e4c3641-0519-4e89-80c0-2b8aa7b03e05,0x1000,0x200000)/\EFI\systemd\systemd-bootx64.efi
Boot0001* Hard Drive BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0200)0000474f00004e4fc9000000010000008f00530061006d00730075006e0067002000530053004400200039003800300020003100540042000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600041d0101060000000317100001000000002538da31a011677fff040001043c00ef47642dc93ba041ac194d51d01b4ce6530061006d00730075006e00670020005300530044002000390038003000200031005400420000007fff04000000424f00004e4fb5000000010000008500430054003200350030004d00580035003000300053005300440031000000050109000200000000010416008b12e85cec2cf040837280640e3dc85802007fff040002010c00d041030a0000000001010600001703120a000400ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce63000320032003300320045004600420039003500430039002000200020002000200020002000200000007fff04000000424f
Boot0002* CD/DVD Drive BBS(CDROM,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0300)0000474f00004e4fc900000001000000850048004c002d00440054002d00530054002000420044002d00520045002000200042004800310036004e005300350035000000050109000300000000010416008b12e85cec2cf040837280640e3dc85803007fff040002010c00d041030a0000000001010600001703120a000100ffff00007fff040001043e00ef47642dc93ba041ac194d51d01b4ce64900530039004b00470048005000350035004500330034002000200020002000200020002000200000007fff04000000424f
Boot0004* Windows Boot Manager HD(1,GPT,0e4c3641-0519-4e89-80c0-2b8aa7b03e05,0x1000,0x200000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI0000424f
Boot0005* USB HDD BBS(HD,,0x0)/VenHw(5ce8128b-2cec-40f0-8372-80640e3dc858,0900)0000474f00004e4fbd00000001000000790049004e00540045004c002000530053004400500045004b004b00570032003500360047003700200033003100300032000000050109000200000000010416008b12e85cec2cf040837280640e3dc85809007fff040002010c00d041030a000000000101060000140305060002007fff040001043600ef47642dc93ba041ac194d51d01b4ce6300031003200330034003500360037003800390041004200430044004500460000007fff04000000424f
Boot0006* UEFI OS HD(2,MBR,0x26c6223f,0x1dce32b0,0x10000)/\EFI\BOOT\BOOTX64.EFI0000424f
cactux
November 19, 2025, 7:53pm
5
Would you please post the contents of /etc/fstab:
sudo mount /dev/nvme0n1p2 /mnt
cat /mnt/etc/fstab
and the output of:
sudo blkid
Anyway I removed every sata device, with only the eos nvme left. still boots windows stuff. In the bios I now have a choice between linux bootloader and windows, so after switching everything is fine again.
cactux
November 19, 2025, 8:14pm
7
ZekerPixels:
Boot0004* Windows Boot Manager HD(1,GPT,0e4c3641-0519-4e89-80c0-2b8aa7b03e05,0x1000,0x200000)/\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI0000424f
You seem to have some Microsoft’s stuff in the same partition as your Linux Boot Manager:
ZekerPixels:
Boot0000* Linux Boot Manager HD(1,GPT,0e4c3641-0519-4e89-80c0-2b8aa7b03e05,0x1000,0x200000)/\EFI\systemd\systemd-bootx64.efi
In your ESP, that is.
I don’t have more info about your dualboot setup to be able to say more.