I was following some instructions for entering an advanced BIOS menu, but all it did was somehow reset all my BIOS settings, and in turn deleting my EOS from the boot menu. I only have options for the Windows instance which was part of my dual boot.
Any chance to rescue and reinstate my EOS back to the BIOS boot menu?
Thanks!!!
What filesystem: BTRFS, EXT4?
What bootloader: Grub, systemd-boot?
Also boot up your live usb and post the output of the folowing commands:
sudo parted -l
efibootmgr -v
EXT4
Default, should be systemd-boot yes
$ sudo parted -l
Model: USB3.0 Super Speed (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/4096B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 1000GB 1000GB fat32 Main Data Partition msftdata
Model: WDC PC SN520 SDAPNUW-512G-1014 (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot, esp
2 106MB 123MB 16.8MB Microsoft reserved partition msftres
3 123MB 404GB 404GB ntfs Basic data partition msftdata
6 404GB 405GB 1049MB fat32 boot, esp
7 405GB 457GB 51.6GB ext4 endeavouros
4 457GB 511GB 54.5GB ntfs Basic data partition msftdata
5 511GB 512GB 1074MB ntfs Basic data partition hidden, diag
$ efibootmgr -v
BootCurrent: 0000
Timeout: 0 seconds
BootOrder: 0002,0001,2001,2002,2003
Boot0000* USB HDD: USB3.0 Super Speed PciRoot(0x0)/Pci(0x14,0x0)/USB(3,0)/HD(1,GPT,e0de8101-d89e-4eb0-9f4f-09d5126bb6a8,0x800,0x7470658f)RC
dp: 02 01 0c 00 d0 41 03 0a 00 00 00 00 / 01 01 06 00 00 14 / 03 05 06 00 03 00 / 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 8f 65 70 74 00 00 00 00 01 81 de e0 9e d8 b0 4e 9f 4f 09 d5 12 6b b6 a8 02 02 / 7f ff 04 00
data: 52 43
Boot0001* Windows Boot Manager HD(6,GPT,ff347e10-282a-bd40-8b5e-74477f6aac16,0x2f036add,0x1f4000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
dp: 04 01 2a 00 06 00 00 00 dd 6a 03 2f 00 00 00 00 00 40 1f 00 00 00 00 00 10 7e 34 ff 2a 28 40 bd 8b 5e 74 47 7f 6a ac 16 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 52 43
Boot0002* Windows Boot Manager HD(1,GPT,643dbb4f-27db-420a-9e93-70fd0403fa14,0x800,0x32000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400
dp: 04 01 2a 00 01 00 00 00 00 08 00 00 00 00 00 00 00 20 03 00 00 00 00 00 4f bb 3d 64 db 27 0a 42 9e 93 70 fd 04 03 fa 14 02 02 / 04 04 46 00 5c 00 45 00 46 00 49 00 5c 00 4d 00 69 00 63 00 72 00 6f 00 73 00 6f 00 66 00 74 00 5c 00 42 00 6f 00 6f 00 74 00 5c 00 62 00 6f 00 6f 00 74 00 6d 00 67 00 66 00 77 00 2e 00 65 00 66 00 69 00 00 00 / 7f ff 04 00
data: 57 49 4e 44 4f 57 53 00 01 00 00 00 88 00 00 00 78 00 00 00 42 00 43 00 44 00 4f 00 42 00 4a 00 45 00 43 00 54 00 3d 00 7b 00 39 00 64 00 65 00 61 00 38 00 36 00 32 00 63 00 2d 00 35 00 63 00 64 00 64 00 2d 00 34 00 65 00 37 00 30 00 2d 00 61 00 63 00 63 00 31 00 2d 00 66 00 33 00 32 00 62 00 33 00 34 00 34 00 64 00 34 00 37 00 39 00 35 00 7d 00 00 00 00 00 01 00 00 00 10 00 00 00 04 00 00 00 7f ff 04 00
Boot2001* EFI USB Device RC
dp: 7f ff 04 00
data: 52 43
Boot2002* EFI DVD/CDROM RC
dp: 7f ff 04 00
data: 52 43
Boot2003* EFI Network RC
dp: 7f ff 04 00
data: 52 43
Try the following:
Boot up your Live USB
Chroot into your system.
If 6 and 7 are esp resp. system partition:
sudo mount /dev/nvme0n1p7 /mnt
sudo mount /dev/nvme0n1p6 /mnt/efi
sudo arch-chroot /mnt
bootctl install
reinstall-kernels
exit
This should create an EFI boot entry in BIOS and menu entries on the systemd-boot menu.
Verify with efibootmgr to see that an entry has actually been created.
If you get any errors at any of the steps above, please post them on the forum.
Also, I see two EFI boot entries in your output. I suppose one is the remnant of an earlier Windows install.
THANK YOU!!!
The two boot options were 1. Normal windows boot and 2. Windows Troubleshoot/Repair Options
pebcak, so my computer has worked just fine but today I tried getting into EOS through the boot menu and I got this error as seen in the picture.
I tried loading bios and it also freezes, just goes into a black screen with a cursor underscore on the top left.
Only windows will boot. I can’t use a thumb drive because I can’t select in bios to make it an option, and f12 just gives me windows or Linux to boot from.
Not being able to enter the BIOS is very strange and without it it will be hard. What is your PC / laptop model? How do you try to load BIOS? Does it stay with underscore?
Post your screen after pressing F12, where you can choose Windows / Linux. I assume USB is inside your computer?
Read through the following article for how to boot into the firmware settings (bios) from within windows:
Once in the bios, change the boot priority. Put booting from USB first. Exit.
Plug in your USB and start up your machine. This should boot you into the live session.
Once in the live session, launch Gparted. Right click on your installed system partition, choose Check from the pop up menu. Apply the operation from the tool bar 
When done, shut down the system. Unplug the USB and start up your machine.
Let’s hope this would fix the issue.
All standard restarts into bios tricks didn’t work.
Got into defaulted bios by removing the bios battery and holding another little button on the MB down.
New issue, I can only boot to windows and windows is going blue screen on me of inaccessible boot device. It restarts into automatic repair but hangs there and does nothing.
Bios will not let me include USB as a default boot option either. Even if I enable fast boot in bios, it still doesn’t show up on the list.
Any other idea to boot from USB?
I’m afraid I don’t have any experience of having dealt with the kind of problem you are facing with your BIOS. Hopefully other forum members will chime in and help you out with this one.
Ok, got the issue fixed by reinstalling windows and updating my BIOS.
The new issue I’m having is when I type in sudo arch-chroot /mnt it gives me an error as seen below.
Make sure your system partition is unmounted first. Then run a check on it as I described previously.
Try chrooting again.
Also, post the terminal output as text. Copy, paste, highlight and press Ctrl+E to format. This would make it easier to copy and quote for the sake of troubleshooting and also it will be searchable by the forum search function.
I’m trying my best here, thank you for all your patience!
Model: WDC PC SN520 SDAPNUW-512G-1014 (nvme)
Disk /dev/nvme0n1: 512GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:
Number Start End Size File system Name Flags
1 1049kB 106MB 105MB fat32 EFI system partition boot, esp
2 106MB 123MB 16.8MB Microsoft reserved partition msftres
3 123MB 12.0GB 11.9GB linux-swap(v1) Basic data partition msftdata
4 162GB 189GB 26.9GB ext4 Basic data partition msftdata
5 189GB 254GB 65.0GB ext4 Basic data partition msftdata
6 254GB 319GB 65.0GB ext4 Basic data partition msftdata
7 319GB 341GB 21.8GB ext4 Basic data partition msftdata
8 341GB 422GB 80.7GB ntfs Basic data partition msftdata
9 422GB 423GB 1049MB fat32 boot, esp
10 423GB 474GB 51.6GB ext4 endeavouros
11 475GB 511GB 36.2GB ntfs Basic data partition msftdata
12 511GB 512GB 1074MB ntfs Basic data partition hidden, diag
[root@EndeavourOS liveuser]# sudo umount /dev/nvme0n1p1
umount: /dev/nvme0n1p1: not mounted.
[root@EndeavourOS liveuser]# sudo umount /dev/nvme0n1p10
umount: /dev/nvme0n1p10: not mounted.
[root@EndeavourOS liveuser]# sudo umount /dev/nvme0n1p9
umount: /dev/nvme0n1p9: not mounted.
[root@EndeavourOS liveuser]# sudo umount -a
umount: /run/user/1000: target is busy.
umount: /tmp: target is busy.
umount: /sys/fs/cgroup: target is busy.
umount: /: target is busy.
umount: /run/archiso/bootmnt: target is busy.
umount: /run: target is busy.
umount: /dev: target is busy.
[root@EndeavourOS liveuser]# sudo mount /dev/nvme0n1p10 /mnt
[root@EndeavourOS liveuser]# sudo mount /dev/nvme0n1p9 /mnt
[root@EndeavourOS liveuser]# sudo arch-chroot /mnt
mount: /mnt/proc: mount point does not exist.
dmesg(1) may have more information after failed mount system call.
==> ERROR: failed to setup chroot /mnt
Please format the pasted text for better readability.
Highlight the text and press Ctrl-E.
Also, did you run a check on the filesystem?
[root@EndeavourOS liveuser]# e2fsck /dev/nvme0n1p10
e2fsck 1.47.0 (5-Feb-2023)
/dev/nvme0n1p10 is mounted.
e2fsck: Cannot continue, aborting.
[root@EndeavourOS liveuser]# e2fsck /dev/nvme0n1p9
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/nvme0n1p9
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>
/dev/nvme0n1p9 contains a vfat file system
[root@EndeavourOS liveuser]# e2fsck -b 8193 /dev/nvme0n1p9
e2fsck 1.47.0 (5-Feb-2023)
e2fsck: Bad magic number in super-block while trying to open /dev/nvme0n1p9
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
/dev/nvme0n1p9 contains a vfat file system
[root@EndeavourOS liveuser]# e2fsck -b 32768 /dev/nvme0n1p9
e2fsck 1.47.0 (5-Feb-2023)
e2fsck: Invalid argument while trying to open /dev/nvme0n1p9
The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193
or
e2fsck -b 32768
Launch Gparted.
Right click on your system partition. That would be P10.
Unmount it.
Right click again and choose Check from the menu.
Apply from the tool bar.
Gotcha, I wasn’t sure what type of check you were referring to.
During the check it said:
An error occurred while applying the operations
Check and repair file system (ext4) on /dev/nvme0n1p10 00:00:53 ( ERROR )
calibrate /dev/nvme0n1p10 00:00:00 ( SUCCESS )
path: /dev/nvme0n1p10 (partition)
start: 825838175
end: 926654337
size: 100816163 (48.07 GiB)
check file system on /dev/nvme0n1p10 for errors and (if possible) fix them 00:00:53 ( ERROR )
e2fsck -f -y -v -C 0 '/dev/nvme0n1p10' 00:00:53 ( ERROR )
Run this manually in a terminal and see if it gives some more info on what error that might be.
You need to run it with sudo.
$ sudo e2fsck -f -y -v -C 0 '/dev/nvme0n1p10'
e2fsck 1.47.0 (5-Feb-2023)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory entry for '.' in ... (401568) is big.
Split? yes
Missing '..' in directory inode 401568.
Fix? yes
Directory entry for '.' in ... (1712143) is big.
Split? yes
Missing '..' in directory inode 1712143.
Fix? yes
Directory entry for '.' in ... (393413) is big.
Split? yes
Missing '..' in directory inode 393413.
Fix? yes
Directory entry for '.' in ... (396513) is big.
Split? yes
Missing '..' in directory inode 396513.
Fix? yes
Directory entry for '.' in ... (396523) is big.
Split? yes
Missing '..' in directory inode 396523.
Fix? yes
Directory entry for '.' in ... (396659) is big.
Split? yes
Missing '..' in directory inode 396659.
Fix? yes
Directory entry for '.' in ... (399005) is big.
Split? yes
Missing '..' in directory inode 399005.
Fix? yes
Directory entry for '.' in ... (399021) is big.
Split? yes
Missing '..' in directory inode 399021.
Fix? yes
Directory entry for '.' in ... (399069) is big.
Split? yes
Missing '..' in directory inode 399069.
Fix? yes
Directory entry for '.' in ... (399130) is big.
Split? yes
Missing '..' in directory inode 399130.
Fix? yes
Directory entry for '.' in ... (399137) is big.
Split? yes
Missing '..' in directory inode 399137.
Fix? yes
Directory entry for '.' in ... (399175) is big.
Split? yes
Missing '..' in directory inode 399175.
Fix? yes
Directory entry for '.' in ... (399184) is big.
Split? yes
Missing '..' in directory inode 399184.
Fix? yes
Directory entry for '.' in ... (399214) is big.
Split? yes
Missing '..' in directory inode 399214.
Fix? yes
Directory entry for '.' in ... (399483) is big.
Split? yes
Missing '..' in directory inode 399483.
Fix? yes
Directory entry for '.' in ... (399664) is big.
Split? yes
Missing '..' in directory inode 399664.
Fix? yes
Directory entry for '.' in ... (399743) is big.
Split? yes
Missing '..' in directory inode 399743.
Fix? yes
Directory entry for '.' in ... (399825) is big.
Split? yes
Missing '..' in directory inode 399825.
Fix? yes
Directory entry for '.' in ... (399910) is big.
Split? yes
Missing '..' in directory inode 399910.
Fix? yes
Directory entry for '.' in ... (399927) is big.
Split? yes
Missing '..' in directory inode 399927.
Fix? yes
Directory entry for '.' in ... (399932) is big.
Split? yes
Missing '..' in directory inode 399932.
Fix? yes
Directory entry for '.' in ... (399942) is big.
Split? yes
Missing '..' in directory inode 399942.
Fix? yes
Directory entry for '.' in ... (1065920) is big.
Split? yes
Missing '..' in directory inode 1065920.
Fix? yes
Directory entry for '.' in ... (1070500) is big.
Split? yes
Missing '..' in directory inode 1070500.
Fix? yes
Directory entry for '.' in ... (1068017) is big.
Split? yes
Missing '..' in directory inode 1068017.
Fix? yes
Directory entry for '.' in ... (1071402) is big.
Split? yes
Missing '..' in directory inode 1071402.
Fix? yes
Directory entry for '.' in ... (1071464) is big.
Split? yes
Missing '..' in directory inode 1071464.
Fix? yes
Pass 3: Checking directory connectivity
'..' in /lost+found/#393413 (393413) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/cmd/snapd-apparmor (396513) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/cmd (396060).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/cmd/decode-mount-opts (396523) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/cmd (396060).
Fix? yes
'..' in /lost+found/#396659 (396659) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/tests/main/snapd-reexec-prompt (399005) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/tests/main (398641).
Fix? yes
'..' in /lost+found/#399021 (399021) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/tests/main/prepare-image-classic (399069) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/tests/main (398641).
Fix? yes
'..' in /lost+found/#399130 (399130) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#399137 (399137) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#399175 (399175) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/tests/main/snap-connectivity-check (399184) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/tests/main (398641).
Fix? yes
'..' in /lost+found/#399214 (399214) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/tests/main/unhandled-task (399483) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/tests/main (398641).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/tests/main/refresh-classic (399664) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/tests/main (398641).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/tests/main/refresh-delta (399743) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/tests/main (398641).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/tests/main/interfaces-timezone-control (399825) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/tests/main (398641).
Fix? yes
'..' in /lost+found/#394213/snapd-2.58.3/tests/main/user-mounts (399910) is <The NULL inode> (0), should be /lost+found/#394213/snapd-2.58.3/tests/main (398641).
Fix? yes
'..' in /lost+found/#399927 (399927) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#399932 (399932) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#399942 (399942) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#401568 (401568) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#1065920 (1065920) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#1068017 (1068017) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#1070500 (1070500) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#1071402 (1071402) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /lost+found/#1071464 (1071464) is <The NULL inode> (0), should be /lost+found (11).
Fix? yes
'..' in /root/.cache/mesa_shader_cache/ce (1712143) is <The NULL inode> (0), should be /root/.cache/mesa_shader_cache (1703947).
Fix? yes
Pass 4: Checking reference counts
Inode 2 ref count is 0, should be 16. Fix? yes
Pass 5: Checking group summary information
endeavouros: ***** FILE SYSTEM WAS MODIFIED *****
531970 inodes used (16.87%, out of 3153920)
1065 non-contiguous files (0.2%)
376 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 522156/176/1
10778382 blocks used (85.53%, out of 12602020)
0 bad blocks
7 large files
478576 regular files
43689 directories
0 character device files
0 block device files
0 fifos
2617 links
9695 symbolic links (9629 fast symbolic links)
0 sockets
------------
534577 files
Looks like it passed the check without errors.
Could you try chrooting again:
sudo mount /dev/nvme0n1p10 /mnt
sudo mount /dev/nvme0n1p9 /mnt/efi
sudo arch-chroot /mnt
If it says mount has failed because some directory is missing, post the output of:
ls -al /mnt