my 2 distros' installers (and boot repair programs) delete each other's bootloader entries
Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
my 2 distros' installers (and boot repair programs) delete each other's bootloader entries
I had a vexing little problem with the installer on one of my distros, MX. Then I just discovered that another distro I am exploring, Peppermint, causes the same problem when installed.
Each distro's installer is of course theoretically supposed to detect the other distro, and write it into the grub menu; but in practice, they often fail to. I find that MX's installer is unpredictable about this: sometimes it successfully detects the other distro (Peppermint or whatever else I am installing at the time), and sometimes it doesn't. I supposed that was an MX issue, really because normally MX is all I run. (I think I've tried repeatedly re-writing the grub menu, and have observed different results.)
Today, I restarted after installing Peppermint from a liveUSB. To my surprise, the Peppermint installer did the same thing: wrote a grub menu with no entry for my MX installation. I sighed, and ran the MX liveUSB to reinstall MX's bootloader. What else could I do? Unfortunately, it just did the opposite: wrote a new grub menu that left Peppermint out.
So, I guess I can't have both distros. Their installers (or grub re-writing programs) cancel each other out. Any ideas? Um, well, I guess I could manually write the menu, if I want to invest the time, right?
Please provide the value for GRUB_DISTRIBUTOR= from each installation.
Please provide from each, input/output from tree /boot/efi/, and from lsblk -f, using code tags.
I don't know where to find GRUB_DISTRIBUTOR=. Oh, wait, never mind. I was following Color's instructions, and I see that GRUB_DISTRIBUTOR= is in /etc/default/grub. The line says:
I meant for you to boot either of your installed installations to collect data, not a USB stick, and asked for GRUB_DISTRIBUTOR= from each installation.
/boot/efi/ doesn't exist on an MBR partitioned disk, as yours apparently is. That tells us you didn't install either OS in UEFI mode. That affects how to repair. colorpurple21859's instruction is probably all you need to follow, booted from each installed system, or via chroot.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.