Linux

8594 readers

59 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
Be respectful: Treat fellow community members with respect and courtesy.
Quality over quantity: Share informative and thought-provoking content.
No spam or self-promotion: Avoid excessive self-promotion or spamming.
No NSFW adult content
Follow general lemmy guidelines.

founded 2 years ago

MODERATORS

MigratingtoLemmy

I messed up (lemmy.dbzer0.com)

submitted 1 week ago by [email protected] to c/linux

9 comments fedilink hide all child comments

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!

top 9 comments

sorted by: hot top controversial new old

[–] [email protected] 14 points 1 week ago (1 children)

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.

[–] [email protected] 5 points 1 week ago (1 children)

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.

[–] [email protected] 5 points 1 week ago

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

[–] serpineslair 9 points 1 week ago* (last edited 1 week ago) (1 children)

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.

[–] [email protected] 3 points 1 week ago

I think I do have a live media. I'll try this before I blow it up and reinstall.

[–] [email protected] 3 points 1 week 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.)

[–] [email protected] 2 points 1 week ago (1 children)

@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).

[–] [email protected] 2 points 1 week ago (1 children)

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 2 points 1 week ago

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