linux4noobs

1386 readers

1 users here now

linux4noobs

Noob Friendly, Expert Enabling

Whether you're a seasoned pro or the noobiest of noobs, you've found the right place for Linux support and information. With a dedication to supporting free and open source software, this community aims to ensure Linux fits your needs and works for you. From troubleshooting to tutorials, practical tips, news and more, all aspects of Linux are warmly welcomed. Join a community of like-minded enthusiasts and professionals driving Linux's ongoing evolution.

Seeking Support?

Mention your Linux distro and relevant system details.
Describe what you've tried so far.
Share your solution even if you found it yourself.
Do not delete your post. This allows other people to see possible solutions if they have a similar problem.
Properly format any scripts, code, logs, or error messages.
Be mindful to omit any sensitive information such as usernames, passwords, IP addresses, etc.

Community Rules

Keep discussions respectful and amiable. This community is a space where individuals may freely inquire, exchange thoughts, express viewpoints, and extend help without encountering belittlement. We were all a noob at one point. Differing opinions and ideas is a normal part of discourse, but it must remain civil. Offenders will be warned and/or removed.
Posts must be Linux oriented
Spam or affiliate links will not be tolerated.

founded 1 year ago

MODERATORS

PlutoParty

[help] Triple boot system lost one of the drives in Grub. (sh.itjust.works)

submitted 2 months ago* (last edited 2 months ago) by [email protected] to c/linux4noobs

7 comments fedilink hide all child comments

I added more hard drives to my windows PC to dual boot as a test, then added another drive to actually play since I was enjoying Linux. My third OS isn't bootable any more. What have I done wrong?

Started off with Windows 10 on a SATA drive with an M.2 drive for more data.

Added a 2Gb NVME with Debian - this has become my daily driver. I haven't been to windows more than a few minutes a week.

Added another 250Gb SATA drive to test and play with another Debian install so I don't break my daily driver.

Tried today to boot into the test OS and It's just missing from GRUB? It doesn't show up as a bootable drive in my UEFI BIOS either, though the drive itself is seen.

From KDE Partition Manager in my daily driver Debian, the drives are:

/dev/nvme01 - the daily driver Debian

/dev/sda - the Windows OS drive

/dev/sdb - the windows M.2 drive

/dev/sdc - the test Debian drive (not booting)

I would appreciate help. While there's not much on that drive, I would like to continue my playing around.

Thanks in advance.

top 7 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 3 weeks ago (1 children)

Boot problems are really tricky to fix on the computer that's having them.

If any of your other OS's still boot, then use them to download a live ISO of your preferred linux distro, and write it to a USB stick.

Then you can diagnose the problem using a new boot environment that doesn't rely on the main disk.

[–] [email protected] 1 points 2 weeks ago (1 children)

Thanks. I haven't really tried to fix it very hard, but that's an obvious step I should have tried.

[–] [email protected] 2 points 2 weeks ago (1 children)

If the Debians you installed weren't Live ISOs, then I recommend Arch or Artix for CLI, and Manjaro or Ubuntu for GUI.

You'll have to mount the drives, chroot into the one on the drive that has the EFI partition, then grub-install and grub-mkconfig into the EFI partition.

[–] [email protected] 1 points 2 weeks ago

Thank you, I shall try it.

[–] autokludge 2 points 2 months ago (1 children)

I'm thinking you may have updated grub at some stage from Deb, and didn't have the test OS mounted at the time, or os-prober not enabled :- therefore not detected when grub.cfg was regenerated.

https://wiki.archlinux.org/title/GRUB#Detecting_other_operating_systems
https://wiki.debian.org/Grub#Dual_Boot

I ended up using rEFInd myself, as it does automatic OS detection/scans for bootable partitions.

[–] [email protected] 1 points 2 months ago (1 children)

I didn't update GRUB intentionally, but who knows. Installing and reading docs, thanks for the tip.

[–] [email protected] 1 points 2 months ago

I can get into initramfs on that drive now, but the first thing it says is "no root device specified. Boot arguments must include a root= parameter". I assume I'd add that to GRUB, if I could see the OS in GRUB!

Then from the BusyBox initramfs prompt, i try vgchange -ay to try and activate the LVM partitions....? , and it activates three logical volumes from each of the two Debians. I figured out that I can pass it my correct LVM group, and it only activated those three. I exit from the initramfs Prompt and it says it can't find some files in /root/proc, then it hangs forever.

Man, all the stack overflow stuff I see says things like "mount the root to a new folder, then fix the problem, then reboot." But doesn't ever explain how to actually do some of it. I'm just too new to follow the "yada yada"!