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/<CORRECT 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

  • Neuromancer49@midwest.social
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 天前

    If you do switch back to Linux I’ll note that Endeavour and other Arch forks have moved away from older NVIDIA cards because NVIDIA stopped supporting open source drivers. There’s community-maintained solutions out there though. I forget exactly how old, but my 1080 got the boot, and then I had to gety Grover’s from AUR for a bit, right before that security breach. That contributed to my decision to upgrade to a new AMD card.

    • ThunderComplex@lemmy.todayOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 天前

      I’m on a RTX 4080 so I’m most definitely not switching to AMD just for Linux’s sake. Tho as I sad EOS worked perfectly out of the box with all my hardware which was quite a surprise to me. I’ve had bad NVIDIA experience in the past, but that was also like 10 years ago with a Quadro card so… :D
      More surprising was that my audio interface worked, but since it doesn’t have Linux drivers, all Linux could do was play audio thru it, so most of the cool functionality just doesn’t work.