[Nobara] Help fixing boot situation
from Libra@lemmy.ml to linux@lemmy.ml on 13 Jun 18:14
https://lemmy.ml/post/31640922

So I have a weird situation that I’m not sure how to fix, and it’s going to require some background.

I have 4 drives in my machine:

  1. A ~15 year old 128GB SATA SSD (windows, ntfs)
  2. An ~8 year old 512GB SATA SSD (libraries, ntfs)
  3. A ~5 year old 1TB NVMe SSD (nobara, btrfs)
  4. A ~1 year old 2TB NVMe SSD (games, ntfs)

I’ve gone a month now without booting into windows so I figure it’s time to clean up my windows install and reclaim/retire those drives, but my boot situation is kinda weird. #1 is my current default boot drive in bios, and it has both the boot loader for windows and for a previous ubuntu install I also had on the current-nobara install, and then #3 has another one (but won’t boot when I select it in bios for whatever reason), so what I really need to do is clean up all these extraneous boot-loaders and set one up on drive #3 to be my main boot from now on. But I’m very nervous about messing with that sort of thing and rendering my system unbootable (I know, I still have the install USB I could use, but still.) I’ve tried reading guides and such on how to do bootloader stuff in general, but I am not confident in my ability to not fuck it up.

Although now that I think about it if I don’t care about the windows boot drive I can just pull it, I just need to make sure I can boot off drive #3 before I do do that and I have no idea how to go about setting that up with my current situation.

#linux

threaded - newest

just_another_person@lemmy.world on 13 Jun 18:38 collapse

You should have a UEFU compatible setup, so just change the boot target to #3. If it’s not loading because it’s completely missing EFInboot info, I would be shocked.

Libra@lemmy.ml on 13 Jun 18:52 collapse

I tried this before and it wouldn’t boot off of drive #3 for some reason. When I hit F11 in the bios I can select ‘Nobara (BPXP)’ (BPXP is the people who made drive #3) and it works tho? shrug

just_another_person@lemmy.world on 13 Jun 19:13 collapse

Well that’s the definition of targeting an EFI volume to boot. Sounds like you have a config issue in your BIOS. Go through the menus and make sure it’s not looking for legacy boot types first, and only looking for UEFI, then set #3 as the primary boot target.

Or I guess just remove #1 as you said.

Libra@lemmy.ml on 13 Jun 19:44 collapse

Hm, that may be, I’ll have to go poke at it, thank you.