[SOLVED] Arch won't boot after motherboard BIOS update

Banning · 2021-11-18 22:34:40

I've been getting completely random freezes, which are bad enough to force me to reboot. Researching, in this forum, led me to find that it is due to an outdated motherboard BIOS.
I downloaded the new BIOS version on a USB and followed the steps provided in this VIDEO.
I was updating from F20 to F31 and after It finished updating and rebooted, I get "Reboot and Select proper Boot device or Insert Boot Media in selected Boot device and press a key". What's worse is that reverting back to F20(I used the same method as the video) won't fix the issue. The update did went through, as the BIOS options says my version is on the one I updated too.
What happened that caused this problem and how can I revert my mistake? Is it because Q-Flash doesn't work on Linux?

My motherboard is a Gigabyte GA-AB350-Gaming 3

Last edited by Banning (2021-11-19 22:38:45)

Slithery · 2021-11-18 23:23:48

First of all you should never follow random outdated Youtube videos, they could be posted by anyone who doesn't have a clue what they're doing and cause you to completely brick your machine.

Updating the firmware on a UEFI machine usually always clears the NVRAM entries, you just need to follow the instructions on the Arch wiki for the bootloader that you use to reinstall them.

Xyne · 2021-11-18 23:47:32

I agree with Slithery. Following the wrong instructions when flashing your BIOS can brick your system. Manufacturers usually provide images and instructions and they should be your first choice to reduce the risk.

That said, it seems that it worked so update back to the latest BIOS version and then use a live install medium to chroot into your existing system and re-install the bootloader.

Banning · 2021-11-18 23:59:22

Oh, Okay. This looks like it could work.
Here's the sequence that I assume is the correct way, from what I've read:
1. Update back to latest BIOS version
2. reboot with a bootable usb with an Arch.iso
3. boot arch-Linux
4. Chroot
5. Re-install bootloader (GRUB)

Gonna try this now.

Last edited by Banning (2021-11-19 00:01:12)

Xyne · 2021-11-19 01:18:48

Banning wrote:

Oh, Okay. This looks like it could work.
Here's the sequence that I assume is the correct way, from what I've read:
1. Update back to latest BIOS version
2. reboot with a bootable usb with an Arch.iso
3. boot arch-Linux
4. Chroot
5. Re-install bootloader (GRUB)
Gonna try this now.

Yep. It's the same process as when you first installed, but without pacstrapping packages into the mounted chroot. You chroot directly in and from there you can optionally update your packages and then re-install and re-configure the bootloader. Follow the same instructions that you initially used to set it up.

Banning · 2021-11-19 02:26:17

When I looked at /boot/grub, when I chroot'ed, the entire grub directory was missing. So the cause of the problem is that updating my BIOS deletes the grub directory, for some reason.
So I reinstalled GRUB and the .cfg file using 'grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB' and then 'grub-mkconfig -o /boot/grub/grub.conf'.
When I rebooted, GRUB showed up, but the only option I could select was "UEFI Firmware Settings", which would take me to my motherboard BIOS settings.
How can I tell GRUB to boot to my Arch-Linux? May have to tinker with grub.cfg, I believe.

Last edited by Banning (2021-11-19 03:00:10)

seth · 2021-11-19 06:34:24

The /boot directory typically also holds kernel and initramfs which grub-mkconfig uses to build the menu - so you'll have to re-install the kernel from the chrooted system as well (then run grub-mkconfig)

Slithery · 2021-11-19 12:47:45

Banning wrote:

When I looked at /boot/grub, when I chroot'ed, the entire grub directory was missing. So the cause of the problem is that updating my BIOS deletes the grub directory, for some reason.

Are you sure that you didn't just forget to mount the boot directory as well as the root directory before chrooting?

Banning · 2021-11-19 21:44:43

seth wrote:

The /boot directory typically also holds kernel and initramfs which grub-mkconfig uses to build the menu - so you'll have to re-install the kernel from the chrooted system as well (then run grub-mkconfig)

I looked at the /boot directory and the only contents two directories: EFI and grub
cd'ing into EFI shows that the only content is a GRUB directory. cd'ing into that shows grubx64.efi
cd'ing into grub and it contains fonts, grub.cfg, grubenv, locale, themes, and x86_64-efi

Is there anything missing in the /boot directory? Wish there's something I could use to compare and contrast the /boot directory.

Slithery wrote:

Are you sure that you didn't just forget to mount the boot directory as well as the root directory before chrooting?

Now that you mention it,when I typed 'fdisk -l' the only partition that has the boot (*) flag was on the partition (sdb1) for the USB.
I have three partitions on my hard drive.
/dev/sda1 EFI System
/dev/sda2 Linux root (x86-64)
/dev/sda3 Linux swap
There's also sdb1, which is just the USB with arch.iso

Before I chroot'ed, I typed 'mount /dev/sda2 /mnt' and then 'mount /dev/sda1 /mnt/boot/'

This is important, I just realized that when I did the grub-mkconfig command, the command line typed out:

Generating grub configuration file ...
Warning: os-prober will not be executed to detect other bootable partitions
Systems on them wil not be added to the GRUB boot configurations.
Check GRUB_DISABLE_OS_PROBE documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
done

I missed acknowledging this at the first time I made the grub.cfg, I'm gonna check out the documentation right now.

Last edited by Banning (2021-11-19 21:48:00)

seth · 2021-11-19 21:47:53

Is there anything missing in the /boot directory?

Yes. The kernel… re-install it, then rebuild the grub.cfg.

Banning · 2021-11-19 22:34:57

seth wrote:

Is there anything missing in the /boot directory?
Yes. The kernel… re-install it, then rebuild the grub.cfg.

SOLVED!

I chroot'd and typed pacman -Sy linux linux-firmware, then rebuild the grub.cfg, and rebooted.
Grub now has options to launch Arch-Linux and I am able to log in to my beautiful desktop and everything!
Now I hope the new motherboard BIOS version was the solution for the completely random freezes that got me into this mess.

Last edited by Banning (2021-11-19 22:38:55)

Arch Linux

#1 2021-11-18 22:34:40

[SOLVED] Arch won't boot after motherboard BIOS update

#2 2021-11-18 23:23:48

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#3 2021-11-18 23:47:32

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#4 2021-11-18 23:59:22

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#5 2021-11-19 01:18:48

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#6 2021-11-19 02:26:17

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#7 2021-11-19 06:34:24

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#8 2021-11-19 12:47:45

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#9 2021-11-19 21:44:43

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#10 2021-11-19 21:47:53

Re: [SOLVED] Arch won't boot after motherboard BIOS update

#11 2021-11-19 22:34:57

Re: [SOLVED] Arch won't boot after motherboard BIOS update

Board footer