I renamed one of my partitions and now Mint won’t boot up. I go into recovery mode, run a file check and get the following:

Any help would be appreciated.

TIA!

  • jdnewmil@lemmy.ca
    link
    fedilink
    English
    arrow-up
    13
    ·
    10 days ago

    You must have done more than rename a partition… it is looking for the partition UID and not finding it. Since the UID is never supposed to change until the partition gets wiped, this is very odd indeed.

    Also, putting external volumes (usb stick?) into fstab is not a good idea… let the automount find it when you put it in and want to access it.

    • harrys_balzac@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      5
      ·
      10 days ago

      Yeah, I think I really messed up. The drive it can’t find is an internal SSD.

      I am pretty sure I have a live usb so I might just reinstall. Most of my important files are not on the problem drive.

      • N.E.P.T.R
        link
        fedilink
        English
        arrow-up
        5
        ·
        10 days ago

        You dont have to install over the drive. Retrieve any important files from the drive by booting a USB live OS.

  • serpineslair@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    edit-2
    10 days ago

    I would create a live media if you don’t already have one. Boot into that, try to mount your partition and chroot into it. Run

    lsblk -f
    

    Look for the UUID of the partition and copy it. Edit /etc/fstab and swap the UUID of the partition with the one you just copied.

    Try that. Not a definite fix, but that would be the first thing I try, from memory.

    EDIT: this assumes it is your main partition that is not being found, otherwise, you should be able to access /etc/fstab without a live media.

  • Sundray@lemmy.sdf.org
    link
    fedilink
    English
    arrow-up
    4
    ·
    10 days ago

    That’s funny, I had the same thing happen to me last week – except I didn’t do anything with partitions or disk management. (Ended up installing Silverblue, since it wasn’t my primary machine.)

  • Charlie@social.veraciousnetwork.com
    link
    fedilink
    arrow-up
    2
    ·
    10 days ago

    @harrys_balzac Is it complaining that /media/ext_EXT4_drive isn’t mounting? If your root drive (/) is mounting and you have access to /etc/fstab, you can just edit that file with the new UUID of the drive.

    ls -lha /dev/disk/by-uuid/  
    

    To see what the new UUID is, (assuming you know the device path).

    • harrys_balzac@lemmy.dbzer0.comOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      10 days ago

      I see. I will try that in a little bit. I’ve had to take a break. It’s been a long afternoon and my patience has worn thin.

      • mvirts@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        8 days ago

        You may also want to add the nofail option to prevent that mount from stopping the boot process if it’s not essential.