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
Can’t forget about “This incident will be reported.”
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.
It got removed right?
As SU type mail, you can read what meesages got sent to root@machinename
Oh ok
I’d like to add this one:
Uhhuh. NMI received for unknown reason 31 on CPU 3. Dazed and confused, but trying to continueI get this one like once a week and it always makes me laugh. One day I’ll investigate
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.
Poor Tux, it’s a rough life
BIOS/UEFI likely tried to fuck up the CPU, or hardware fault. NMI => Non Maskable Interrupt.
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
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 FUCKEDerror right at them lmfaoCan 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.
Sacrificing children is pretty common in Linux
What goes hard about the kernel panic one?
u cant make popcorn without some kernels panicking
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.
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]
And yet all of them indicates the actual cause of error. It’s nice to have a bit of fun sometimes.
cowsayshould be at the end of every script you run.i have seen many of these memes, is there a website or something where all these are collected ?
Try removing essential packages from your system or unmounting /boot
[insert the perfect meme to put here that has a baby and a fire here future self please]
On the second one if someone typed just “y” I would print “Please read the damn warning”.
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
