658
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Mar 2024
658 points (100.0% liked)
linuxmemes
21180 readers
801 users here now
Hint: :q!
Sister communities:
- LemmyMemes: Memes
- LemmyShitpost: Anything and everything goes.
- RISA: Star Trek memes and shitposts
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack members of the community for any reason.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
- These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudoin Windows. - No porn. Even if you watch it on a Linux machine.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.
Please report posts and comments that break these rules!
founded 1 year ago
MODERATORS
Full kernel corruption after a botched sudo full-upgrade.
I got the wonderful "bailing out you are on your own" shit as well.
Read a guide online about a hail mary ext file system journal recovery protocol, I ran it, like most things without reading too deeply.
Kernel was successfully repaired, Kubuntu kept on truckin'
What does that even mean?
Was the file system on which your kernel resided corrupt, or did something go wrong with a kernel upgrade/installation?
It was some combination of both, the system would post, past the bootloader, attempt to initialize drivers and other standard starting packages and then immediately panic and drop into an emergency terminal (/TTS), with a failure to mount the root partition, from what I can recall. It tried it a couple times and then there was an error message that said: "Bailing out, you are on you own, good luck"
What is this "bailing out you are on your own" shit ?
An error message you can get if you really manage to mess things up. I got it once a few years ago.
wow for real ? what causes it ? that sounds terrible. It's not informative at all