this post was submitted on 24 Mar 2024
763 points (99.1% liked)

linuxmemes

21211 readers
119 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

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 sudo in 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
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    763
    Linux error starter pack (lemm.ee)
    submitted 7 months ago* (last edited 7 months ago) by sag@lemm.ee to c/linuxmemes@lemmy.world
    36 comments fedilink hide all child comments
     

    Alt Text

    Linux Error Messages That Go Hard Starter Pack

    ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.

    WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
   sysvinit initscripts (due to sysvinit) sysv-rc (due to sysvinit) util-linux
0 upgraded, 0 newly installed, 198 to remove and 3 not upgraded
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
 ?] 

    (12/19) upgrading linux-raspberrypi
WARNING: /boot appears to be a seperate partition but is not mounted.
         You probably just broke your system. Congratulations.
>>> Updating module dependencies. Please wait...

    [   0.895799] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs 
on unknown block(0,0)

      _______________________________
< Your System ate a SPARC! Gah! >
  ------------------------------
            \    ^__^
              \  (xx)\_________
                 (__)\         )\/\
                  U   ||-----w |
                      ||      ||

    Out of memory: Kill process 15745 (postgres) score 10 or sacrifice child

    all 37 comments
    sorted by: hot top controversial new old
    [–] HeyLow@lemmy.blahaj.zone 171 points 7 months ago (2 children)

    Can't forget about "This incident will be reported."

    [–] themoonisacheese@sh.itjust.works 69 points 7 months ago (1 children)

    Fun fact! It gets reported to /var/spool/mail/root ! If your mail spooler is properly configured (and your SMTP relay is also configured to send mail addressed to root to an actual user account) then you will get these alerts by email.

    [–] sag@lemm.ee 10 points 7 months ago (1 children)

    It got removed right?

    [–] BCsven@lemmy.ca 21 points 7 months ago (1 children)

    As SU type mail, you can read what meesages got sent to root@machinename

    [–] sag@lemm.ee 4 points 7 months ago

    Oh ok

    [–] 21Cabbage@lemmynsfw.com 15 points 7 months ago

    I first got that on a Mac in my school and actually got scared it was going to tell the IT desk. It didn't.

    [–] orsetto@lemmy.dbzer0.com 137 points 7 months ago (3 children)

    I'd like to add this one:

    Uhhuh. NMI received for unknown reason 31 on CPU 3.
Dazed and confused, but trying to continue

    I get this one like once a week and it always makes me laugh. One day I'll investigate

    [–] veroxii@aussie.zone 50 points 7 months ago

    I mean reason 31 could be anything. CPU 3 could be feeling a little tired, be pranking you, or just not be the brightest of the CPUs.

    [–] finkrat@lemmy.world 13 points 7 months ago

    Poor Tux, it's a rough life

    [–] JATtho@lemmy.world 5 points 7 months ago

    BIOS/UEFI likely tried to fuck up the CPU, or hardware fault. NMI => Non Maskable Interrupt.

    [–] OmnislashIsACloudApp@lemmy.world 102 points 7 months ago

    I love some of the dangerous upgrade commands too, my favorite:

    hdparm --fwdownload-mode7 firmwarefile.bin --yes-i-know-what-i-am-doing --please-destroy-my-drive /dev/sdb

    [–] AMDIsOurLord@lemmy.ml 59 points 7 months ago

    Legend has it that in the dark ages, when DEC (Digital Equipment Corp) licensed ARM from Acorn for their StrongARM processors, they took Arm's testing toolkit and ran it to find issues with their processor.

    Now, ARM was a tiny division and only had developed their tools for strictly internal usage. It was never supposed to go to some huge and professional enterprise like DEC.

    So when the DEC engineering team ran the tester, It shouted a SHIFTER FUCKED error right at them lmfao

    [–] piefedderatedd@piefed.social 39 points 7 months ago

    Can you insert Lp0 on fire as well ? :) https://en-academic.com/dic.nsf/enwiki/7306628

    lp0 on fire (aka Printer on Fire) is a semi-obsolete error message still generated on some Unix/Linux operating systems in response to certain types of printer errors. lp0 is the Unix device handle for the first line printer, but the error can be displayed for any printer attached to a Unix/Linux system.

    [–] DoomBot5@lemmy.world 34 points 7 months ago

    Sacrificing children is pretty common in Linux

    [–] TexMexBazooka@lemm.ee 33 points 7 months ago (3 children)

    Is there a version of this with some pixels in it?

    [–] possiblylinux127@lemmy.zip 37 points 7 months ago (1 children)

    1000002133

    [–] sag@lemm.ee 14 points 7 months ago

    Much better

    [–] ysjet@lemmy.world 20 points 7 months ago* (last edited 7 months ago) (3 children)

    Possibly, but I'll just transcribe it here for screenreaders and people who can't see through the pixelation:

    Linux Error Messages That Go Hard Starter Pack

    ERROR: Failed to mount the real root device.
Bailing out, you are on your own. Good luck.

    WARNING: The following essential packages will be removed.
This should NOT be done unless you know exactly what you are doing!
   sysvinit initscripts (due to sysvinit) sysv-rc (due to sysvinit) util-linux
0 upgraded, 0 newly installed, 198 to remove and 3 not upgraded
You are about to do something potentially harmful.
To continue type in the phrase 'Yes, do as I say!'
 ?] 

    (12/19) upgrading linux-raspberrypi
WARNING: /boot appears to be a seperate partition but is not mounted.
         You probably just broke your system. Congratulations.
>>> Updating module dependencies. Please wait...

    [   0.895799] ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs 
on unknown block(0,0)

      _______________________________
< Your System ate a SPARC! Gah! >
  ------------------------------
            \    ^__^
              \  (xx)\_________
                 (__)\         )\/\
                  U   ||-----w |
                      ||      ||

    Out of memory: Kill process 15745 (postgres) score 10 or sacrifice child
    [–] TexMexBazooka@lemm.ee 6 points 7 months ago (1 children)

    You’re a hero among us

    [–] Cannonhead2@lemmy.world 3 points 7 months ago

    Good human

    [–] sag@lemm.ee 2 points 7 months ago

    Thanks added to the post

    [–] TooLazyDidntName@lemmy.world 32 points 7 months ago (1 children)

    What goes hard about the kernel panic one?

    [–] lseif@sopuli.xyz 9 points 7 months ago

    u cant make popcorn without some kernels panicking

    [–] MonkderZweite@feddit.ch 32 points 7 months ago* (last edited 7 months ago)

    Add sudo insults for good measure.

    [–] gentooer@programming.dev 27 points 7 months ago (1 children)

    I remember not compiling the root filesystem in the kernel on my first Gentoo install, and being surprised it couldn't mount root at boot.

    [–] JATtho@lemmy.world 3 points 7 months ago* (last edited 7 months ago)

    The first kernel I built was not entirely happy with the .config I had made for it. Only thing it could do was BEEP-ing in panic for any key presses. [insert noot noot meme]

    [–] cley_faye@lemmy.world 25 points 7 months ago

    And yet all of them indicates the actual cause of error. It's nice to have a bit of fun sometimes.

    [–] BitingChaos@lemmy.world 21 points 7 months ago

    cowsay should be at the end of every script you run.

    [–] XEAL@lemm.ee 8 points 7 months ago* (last edited 7 months ago)

    Argh not the VFS kernel panic!

    [–] Napain@lemmy.ml 4 points 7 months ago (1 children)

    i have seen many of these memes, is there a website or something where all these are collected ?

    [–] brian@programming.dev 3 points 7 months ago

    Try removing essential packages from your system or unmounting /boot

    [–] croobat@lemmy.world 1 points 5 months ago

    On the second one if someone typed just "y" I would print "Please read the damn warning".

    [–] psud@aussie.zone 1 points 7 months ago

    I like the errors that strongly signal that the system was not produced by a corporation. They'd never get through coffee review where I work

    [–] pewgar_seemsimandroid@lemmy.blahaj.zone -1 points 7 months ago

    [insert the perfect meme to put here that has a baby and a fire here future self please]