I went from BIOS F4 to F10 today and now the system refuses to boot.
All drives are still detected, but none as bootable.
Switching CSM on (all disks are and always have been GPT) makes them show up and selectable in the boot menu, but actually booting does not work (no bootable device found).
Fiddled with just about everything else, too, including resetting CMOS, reflashing, but no dice.
It is possible to boot into my installation using an USB stick, tried reinstalling GRUB because I was out of ideas, didnât help.
The drive in question is a m.2 NVMe SSD. (970 EVO plus)
Does anyone have any ideas on how to salvage this/what else to try?
I donât particularly want to reinstall.
How big are your drive(s)? This could be used as a good excuse to take advantage of the recently lowered SSD prices and order a new system drive. 1TB Samsung 980 drives can be had for as little as $50 and a cheap-ish fast 4TB boot drive can be purchased for $270.
Sometimes a reinstall is what it takes to get everything going again, and in this case, it seems like the most straightforward solution if a rollback doesnât work. I know it isnât what you want to hear, but⌠And yes, you can reinstall in either case, no real need for new hardware, just thought it might make stuff easier.
I assume you have tried removing all drives, start the computer from cold boot, shut it off, insert ONE drive, start the computer, and see if that works?
The SSDs are both the same, 2TB each. The entire system is pretty new.
Havenât touched the hardware yesterday, apart from a CMOS reset, it was kind of late and I wasnât in the mood for a blood sacrifice (my half of the delicate hands and fingers is visiting family).
I moved them around today (from the CPU connected PCIe lanes to the chipset), but it didnât change anything. (I chose sliced knuckles over inside index finger, for anyone curious)
I guess Iâll reinstall and use the rest of my vacation to consider a career change.
All computers seem to do these days is get on my nerves
Oh, and as for rolling back:
F8 and F9 contained security fixes, which was the only reason I upgraded the BIOS in the first place - so I can go back 1 version, perhaps, butâŚif ending up with an unbootable system is something that can happen, Iâd rather go all the way.
âŹ: Tried F9 anyway, no difference.
Alright, I decided to chroot into my installation again and make absolutely sure I got GRUB right yesterday, and something changed - symbol grub is shim lock enabled not found
I stumbled across this thread, and figuredâŚwhy not try systemd-boot.
Not exactly sure how the problem came about, but systemd-boot works, no need to reinstall \o/
Yeah, Grub is kinda old and archaic nowadays, systemd-boot is better if all you are ever going to do with the computer is boot Linux. for multisystem boots via a hypervisor though you do still need Grub, though I wish systemd-boot would support that particular feature soon.
I donât even know why I used grub, I didnât on my previous system.
Probably wanted to claim my free copy of Windows 11 to never use, like I did with 10.
I should really stop doing this kind of work while inebriated.
I just had exactly the same problem with an Gigabyte X670 Aorus Elite, after updating from F6 to F21a. I also have two 2TB m.2 NVMe SSDs. Both of them were detected after the BIOS update (the Q-Flash tool can even list files/directories on them), but the system said âno bootable devices foundâ. As @Skollolol mentioned, switching CSM on makes the devices selectable, but booting still does not work.
I hope this helps anyone else:
I managed to solve the issue by booting from a USB flash drive and reinstalling GRUB, no need for systemd-boot.
I think the main problem here was that updating the BIOS enables secure boot. This creates the errors when reinstalling GRUB. So you if secure boot was disabled before the update, then you have to manually disable it.
For me, the BIOS setup refused to disable secure boot. This worked: Enable CSM â Select non-bootable device to boot (it fails) â Disable CSM â Now the BIOS should allow to disable secure boot.
I believe that reinstalling GRUB is not even really necessary. The real issue is probably âjustâ that updating the BIOS removes the entry in the firmware boot manager. I guess that could be fixed with efibootmgr or an UEFI shell (I did not try that, since grub-install worked for me)
And yes, you can reinstall in either case, no real need for new hardware, just thought it might make stuff easier.