Alright, here’s one for you.
I have Manjaro and MXLinux installed on an internal SSD. That’s my boot drive.
I also have an internal HDD which I use for media storage. That’s my data drive.
sda and sdb.
As we know, drive designations are assigned arbitrarily on boot, so my install drive can be either sda or sdb depending on the weather. This generally isn’t a problem as both grub and my fstab use UUID only.
However, if I install updates or run update-grub in Manjaro on a rainy day when my boot drive happens to be sdb, MX won’t boot. Or rather, grub points me to the kernel without issue but once MX begins to boot I’m dropped into a initramfs/busybox shell (with which I have no familiarity but have bookmarked and will be reading up on in due course). I won’t be able to boot into MX again until I run update-grub in Manjaro on a sunny day when my boot drive happens to be sda.
This isn’t really a problem, more of an annoyance and I’d like to find out what’s causing it for my own personal enlightenment.
I’ve dug around a bit but come up mostly empty, that or the results I’m looking for are being lost in the sea of unfortunate souls who can’t figure out how to dual-boot Windows and Ubuntu. The closest match I found was somebody who was using a dodgy ext2 extension (in 2017 no less!) to access their Ubuntu partition from windows and consequently corrupting their file system.
I would like to stress that this is not a help request, if it were I’d post over at the debian or MX forum. I’m just curious whether anybody else has encountered or heard of the same issue before with a multi-boot system.
I’ll probably remove MXLinux or install something else over it once I get this figured out. I don’t care for it at all but to remove it now would be to admit defeat.