Can't boot on EOS after upgrading BIOS

General system Newbie
1

Hey guys i have a big problem.
I can’t boot on my Endeavour OS entry after updating the BIOS to a later version.
It says

Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block (0,0)

i’ve also WIndows and LInux MInt installed …

2

Which one is in control of the Grub, Mint or EnOS?
Could you get into your UEFI settings and set EnOS on top of the boot priority?

Could you boot up a Live EnOS session and post the output of the following commands?
(You could do this from your Mint install as well)

sudo parted -l

efibootmgr -v

3

sudo parted -l
[sudo] password for tasmat:
Model: ATA Samsung SSD 860 (scsi)
Disk /dev/sda: 1000GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 17,4kB 16,8MB 16,8MB Microsoft reserved partition msftres
2 16,8MB 738GB 738GB ntfs Basic data partition msftdata
3 738GB 1000GB 262GB btrfs root

Model: ATA WDC WDS250G2B0A (scsi)
Disk /dev/sdb: 250GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 538MB 537MB primary fat32 boot
2 539MB 250GB 250GB extended
5 539MB 250GB 250GB logical ext4

Model: Samsung Flash Drive FIT (scsi)
Disk /dev/sdc: 128GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags:

Number Start End Size Type File system Flags
1 1049kB 128GB 128GB primary boot
2 128GB 128GB 33,6MB primary fat16 esp

Model: Force MP510 (nvme)
Disk /dev/nvme0n1: 480GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Disk Flags:

Number Start End Size File system Name Flags
1 1049kB 106MB 105MB fat16 EFI system partition boot, esp
2 106MB 123MB 16,8MB ext4 Microsoft reserved partition msftres
3 123MB 205GB 205GB ntfs Basic data partition msftdata
4 205GB 206GB 641MB ntfs hidden, diag
5 206GB 480GB 274GB ext4 root

and …

efibootmgr -v
EFI variables are not supported on this system.

Mint is in control of the Grub. I’ll try that with the UEFI settings …

4

no … i can’t do anything from the UEFI settings …

5

Judging by the output of parted -l I can see a mishmash of disks with different partition tables (msdos and gpt) and perhaps different installation mode (MBR/Legacy and UEFI). It’s not obvious to me which system is where and in what install mode.

Could you please split the output for each disk and describe what you have in them and how you have installed your systems? What mode etc.?

6

If you upgraded your BIOS it has reset to factory defaults. This means all the things you had to disable like secure boot fast boot etc have to disabled again. As well as any raid settings.

3 Likes
7

i’ll try …
Linux Mint is in the Disk /dev/sdb: 250GB
Windows and EOS are on Disk /dev/nvme0n1: 480GB
i’ll check secure and fast boot now … thx

8

checked … secure boot is off
Additionally when i boot in UEFI mode i have the option to boot ONLY in Windows.
when i boot in CSM, then i see the options for the other drives
still no EOS …

9

I guess your issue is mostly due to having installed your systems in different modes, that is UEFI and MBR/Legacy.

If

is from your Mint install then it is obviously in MBR/Legacy mode.

However

indicates that your Windows and EnOS are in UEFI mode.
At this point I am a bit stumped about the fact that you are not getting any boot options for EnOs when you set your BIOS to UEFI mode.

10

any suggestions before making a new installation and lose all my settings ?

11

Personally, I would disable CSM and only go for UEFI installation.

You could then boot up your EnOS live usb and re-install its bootloader. There are instructions for this in EnOS’ wiki.

Please note that if you choose to do so, a Grub installed in UEFI mode won’t be picking up your Mint which is in MBR/Legacy mode.

My suggeston would be to re-install Mint in UEFI mode as well.
Create a new GPT disk and install in UEFI mode.

Let EnOS’ Grub to be in charge of the boot process. When all your installed systems are in the same mode, Grub will pick up on them and add them to the its boot menu.

1 Like
12

i re-installed Mint in UEFI just in case it would pick up my EOS.
it shows it, but when i hit Enter i get a black screen …
i can’t find any relative article in Wiki …

13

As far as I know Ubuntu/Mint grub is incapable of booting Arch (-based) systems. It simply won’t produce the correct entry for them in grub.cfg.

Could you post efibootmgr -v again booted into your Mint?

14

efibootmgr -v
BootCurrent: 0005
Timeout: 1 seconds
BootOrder: 0009,0005,0008
Boot0005* ubuntu HD(1,GPT,fa2edaaf-ee22-479c-8920-9b241045440d,0x800,0x32000)/File(\EFI\UBUNTU\SHIMX64.EFI)
Boot0008* UEFI: Samsung Flash Drive FIT 1100, Partition 2 PciRoot(0x0)/Pci(0x1,0x3)/Pci(0x0,0x0)/USB(2,0)/HD(2,MBR,0x8777a369,0xeef4200,0x10000)…BO
Boot0009* Windows Boot Manager HD(1,GPT,fa2edaaf-ee22-479c-8920-9b241045440d,0x800,0x32000)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)WINDOWS…x…B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}…

15

You don’t seem to have a boot entry for EnOS :thinking:

Here is how to reinstall Grub bootloader for a UEFI system:

Please have a read and if you feel you need more assistance please don’t hesitate to ask here.

16

commands don’t work on my system …

sudo su
root@tasmat-LM:/home/tasmat# mount /dev/nvme0n1 /mnt
mount: /mnt: /dev/nvme0n1 already mounted or mount point busy.
root@tasmat-LM:/home/tasmat# mount /dev/nvme0n1 /mnt/boot
mount: /mnt/boot: mount point does not exist.
root@tasmat-LM:/home/tasmat# mount /dev/nvme0n1 /mnt/boot/efi
mount: /mnt/boot/efi: mount point does not exist.

17

You need to do this from an EnOS live session.

Boot up your EnOS’ live usb. Open a terminal and run:

* sudo su
* mount /dev/nvme0n1p5 /mnt    (I suppose /dev/nvme0n1p5 is where your EnOS is installed)
* mount /dev/nvme0n1p1 /mnt/boot/efi
* arch-chroot /mnt 
* grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=EndeavourOS
* grub-mkconfig -o /boot/grub/grub.cfg

Now type exit to quit the chroot.

Check with efibootmgr -v to see if you have an entry for your EndeavourOS and it is first in boot order.

If that is the case, rebooting should take you into your EnOS.

If you don’t see boot entries for your other systems in the Grub boot menu, once booted into EnOS:

First, make sure os-prober is installed and if not install it:

sudo pacman -S --needed os-prober

then edit the main grub configuration file by adding:

GRUB_DISABLE_OS_PROBER=false

to

/etc/default/grub

and regenerate grub.cfg

sudo grub-mkconfig -o /boot/grub/grub.cfg

1 Like
18

i didn’t have the patience to wait for a solution and did a fresh install.
i’m sorry the blame is on me … whatever you may think of me guys it’s true …
again, i’m truly sorry and thank you for everything!

1 Like
19

s-l400

20

Is there not a wiki page or something given the number of times a “how do I restore GRUB?” question comes up?

3 Likes