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. |
As root add this line to /etc/default/grub:
Code:
GRUB_DISABLE_OS_PROBER=false Code:
sudo update-grub |
Quote:
Code:
GRUB_DISTRIBUTOR="$(unset PRETTY_NAME; (. /etc/lsb-release; echo ${PRETTY_NAME:?}) 2>/dev/null || echo Debian)" Code:
/boot/efi/ [error opening dir] The lsblk -f output is: Code:
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS |
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. :p
/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. |
All times are GMT -5. The time now is 03:29 PM. |