So... I have a problem. Just switched back to Fedora, and it was going fine, until I restarted today, and now my system is stuck in "emergency mode". Says "Press enter to continue" and gets stuck on "Starting default.target".

So, I have no idea what to do to fix this. There were no error messages. I tried checking the fstab, and that's fine. I checked the btrfs partition for errors, and there weren't any. I disabled the nvidia hibernation services (using chroot), and that didn't fix anything.

So now I'm stuck on a live usb because I can't get into my ssd system. Any help to fix this would be appreciated.

Posted in: s/Linux

๐Ÿš€ clseibold [๐Ÿ›‚ Code of Conduct rule 1 violations]

2025-07-11 ยท 10 months ago

๐Ÿ”’ Locked

4 Comments โ†“

๐Ÿš€ clseibold [OP, ๐Ÿ›‚] ยท 2025-07-11 at 15:26:

I ended up figuring out the problem: I forgot I deleted a partition that was still in the fstab.

How great that Linux's fstab gets so out of sync from such simple changes! If only some PhD student could invent a way for the fstab to be automatically modified/synced based on partition changes... /s

๐Ÿ‘ป darkghost ยท 2025-07-11 at 15:30:

Sounds boring. Let's take away more user options. -A GNOME developer, probably

๐Ÿ›ฐ๏ธ repeater ยท 2025-07-12 at 04:55:

Despite all of the great open-source software out there, you two still complain about the people who are doing all of the work. Tsk, tsk.

If you used a tool to edit your partitions and you reasonably expected your fstab to be updated automatically and it wasn't, file a bug. If you just didn't think to edit the fstab, well, PEBKAC happens. Next time, use `findmnt --verify` to make sure you didn't break anything before rebooting.

As for the Gnome developers, Gnome Disks will actually let you edit partitions and mount points in a single program. I'm not sure whether it handles this case properly though (see https://gitlab.gnome.org/GNOME/gnome-disk-utility/-/issues/260).

๐Ÿš€ clseibold [OP, ๐Ÿ›‚] ยท 2025-07-12 at 09:17:

@repeater My system wouldn't start because one entry in the fstab no longer applied, and you're here trying to tell me this is normal? For gosh sakes, you wouldn't know good software if it hit you in the head. All you are doing is making excuses for bad design decisions.

Yes, I reasonably expect that KDE's partition manager at the very least notify me of an entry in the Fstab that would break my system. Even more so should it modify the fstab. Even more so should Linux still boot even when there is one non-essential entry in the fstab that doesn't work.

AND GUESS WHAT @repeater? WINDOWS DOES ALL OF THE ABOVE. You people expect users to hate all of the work that has been put into making Windows usable, and at the same time hate us for pointing out that some things Windows just does better. How about that?

You know, it does actually matter whether all of someone's work is good or not. Just because someone spent years making a crappy program doesn't mean we have to respect it just because they are "doing all the work".

And of course you would be a Gnome defender, lmao. The Gnome developers are the worst of the worst of the Linux ecosystem. To suggest they are the only ones doing all the work is propagandic. But that's what I would expect from a Gnome fanatic who treats people like crap for expecting one's computer to behave in the most logical fashion possible.

People wouldn't have to complain if this shit wasn't so crappy, especially when I had to spend 7 hours the other day trying to get rpm fusion and the nvidia drivers installed properly, and Firefox properly using hardware video decoding. But then again, maybe more developers, like Nvidia, would put more effort into making Linux work better with their software if Linux people like you didn't treat everone like crap all the time.