Tried to install my new M.2 SSD right now. Should have been an easy job right? Just pop it in, screw in the screw and done.
But noooo, of course not. Turns out, my screw is missing.
After trying to get a screw out of a laptop HDD, I decide to break it's PCB to get the screw out (didn't need that drive anyway). That works, it fits, the SDD is in place.
I try to boot. Long dark and than, BIOS. Hmm.
Try to reboot, again BIOS. Only two out of my 3 SATA drives get recognized.
1/2

Follow

Both are my HDD's, not my boot-SSD with Windows and my two Linux partitions.
Turns out, that two from my six SATA ports on the motherboard died in the process of screwing in a SSD... I don't know how, but at least it seems like that.
Connected my boot-SSD to a working port and voila, we are booting. But of course only into Windows, I have no f***ing clue, where GRUB disappeared to. Wanted to install a new Linux tomorrow anyway, why not also install a new bootloader

@Zeno Is the option to boot to Linux just gone from the BIOS entirely? Like, not from the post-POST bit of the boot process, but can you select it as a boot option if you go into the BIOS?

Windows has its own boot manager and this can be set to boot independently of GRUB.

@trekkie1701c
Yep, completely gone from the BIOS menu. The only thing there is the windows bootloader

@Zeno Sad to hear that that happened :(

If you use EFI for booting Linux and don't put your EFI file in the right place on the boot partition you have to create a new EFI-Entry when you plug your Drive into a different port :)

The path of the executable efi file needs to be /EFI/BOOT/BOOTX64.EFI (on your boot partition). This file will be detected by basically any UEFI BIOS without an EFI-Entry :)

Grub's installer has an option where you specify the EFI file path on install.

@Ghosty
Thanks for the tip, but I think I don't quite get it, could you elaborate?

I have Linux and Windows on that drive and it only finds the Windows bootloader. How would I go about positioning the EFI file, and does it even make sense in that context?
And did I get that right? GRUB generates EFI-entries replacing positioning the EFI file in the right place?

@Zeno I don't think that really matters as long as you create a separate boot partition for Linux (I guess).

Sorry for describing it in so a complicated matter. I wanted to explain the technical details behind your problem as well but am bad at explaining :P

It's rather easy to do with grub. You have to add the tag --removable when you run your grub-install (wiki.archlinux.org/title/GRUB/)

@Zeno FYI:
It is called removable because this feature is usually used for removable storage devices like live images (that's how your install USB can boot using EFI without a boot menu entry set, for example).

But besides that it is quite useful for normal installs as well. That makes sure that you can boot your setup on any EFI system without relying on a specific boot menu entry. :)

@Ghosty
Thanks anyway. It might have just gone over my head, I didn't look at the boot process that close before

@Zeno And yes GRUB creates EFI-entries in on your BIOS using efibootmgr. Per default, GRUB doesn't place the EFI-executable in the spot where a BIOS would normally look for. That's why GRUB relies on a boot menu entry. As soon as something as little as the drive's SATA-Slot changes, it can cause your bios to no longer find the executable using GRUB's boot menu entry. --removable gets rid of that issue by placing the EFI-Executable in a place which your BIOS scans on boot. (/EFI/BOOT...) :)

@Ghosty
Ah alright. Thanks for the explanation. That sounds rather practical. Might start to use this. TIL

Sign in to participate in the conversation
Fosstodon

Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.