Alright I'm at the end of the rope with my Linux knowledge. So I need your help.
I'm on EndeavourOS and just recently upgraded to Linux 7.1.5, all upgrades thus far have been without issue. I am dual-booting but have Linux on its own SSD, and grub handles booting into Linux or Windows.
Now, after booting into Windows and back into Linux, Linux won't start.
The error:
A start job is running for /dev/disks/by-uuid/
Let me tell you what I've already done:
- Regenerate mkinitrd with dracut
- Regenerate grub.cfg and verified via diff it is identical to the current one
- On a live usb verified that the UUIDs in the grub and fstab files are correct using the KDE partition manager (they are)
- Verify on a live usb the SSD still works (data and everything is still there)
- Changed the grub boot option on boot to check that the UUID is not hardcoded somewhere and can be changed (this is true, inputting a garbage UUID changes the boot error to A start job is running for /dev/disks/by-uuid/garbage-uuid
One last idea I had was to drop myself into the dracut emergency shell and actually check what's actually under /dev/disks/by-uuid and lo and behold: it's actually missing the drive.
Here's whats nuts tho: grub loads the drive by UUID as well, loads the initrd, and all that works. When I regenerated the initrd with dracut I could also tell that grub was now loading the newer initrd.
WHAT THE FUCK???
Help?
At this point I REALLY don't know wtf to do. Why doesnt the initramfs detect the drive? The only useful info I can add here is that all drives listed under /dev/disks/by-uuid had that shorter UUID with no dashes like ABCD1234, whereas the UUID for the correct drive/partition is the longer type UUID like abc1234-1234-0000-defg
Yeah so grub can see the disk but then the kernel can't. Efi and other tricks aren't involved.
I think your route is to find out why the kernel hates your ass. Probably an upd pulled a driver ... But who removes the SATA or nvme stuff?
Either way, it's in the kernel and not the boot or the core apps. I don't use endeavour, where I could provide better help, but I think the kernel is your best suspect for this crime.
well since endeavour is very close to arch I hope I'll find some solutions in that realm. But yeah I'm thinking something must've gone awry with the kernel.. hm I should downgrade that one too, only downgraded systemd but maybe 7.1.5 has some fuckery
Smart thinking. I don't use arch (btw) either, so I'm merely a cheerleader at this point. Yes, I'd downgrade the kernel for the sake of Science. Find a popular stable kernel, jump to that and see if it behaves better.
(That may be my bias: I only really do enterprise linux, so after 28 years since I moved from slackware I'm really risk-averse!)
You could install
linux-lts, I sometimes use that as a sanity check in case there is some kernel fuckery