Arch Linux

Wyrm88

Member

Registered: 2010-05-05

Posts: 53

[SOLVED] Kernel panic after not realizing /tmpfs was full

Hi all,

Wasn't sure whether to post this here or in the Newbie Corner. Apologies if I've omitted any important cues/commands one would usually perform when it comes to kernel panics, since I've never encountered one thus far.

Long story short, for the past couple of weeks I've been running some Python scripts which utilize all 4 cores on my i5, as well as often extend into the swap partition for additional memory. This coupled with the fact that I haven't rebooted my system for the past two weeks or so, have made my /tmpfs full. I have only realized this earlier today, when I was performing a system-wide update. The new kernel/mkinitcpio step of 'pacman -Syu' were complaining with numerous errors about there not being enough space available. I figured this was due to the tmpfs being full, so (silly me) I decided to reboot my system.

Needless to say, I was welcomed with a kernel panic upon rebooting. Here is a screenshot of the output. I'm unavailable to type anything into the prompt, if you could even call it that.

I've decided to post my question here, especially before I run a live USB and start fixing on my own. Furthermore, this type of error -13 is something I haven't encountered googling about this issue...

falconindy's post led me to the conclusion that my full /tmpfs was most likely the culprit. If anyone has any recommendations or advice on how to approach this issue, I would greatly appreciate it.

Last edited by Wyrm88 (2016-05-09 19:41:55)

\hbar

Member

Registered: 2014-03-15

Posts: 165

Re: [SOLVED] Kernel panic after not realizing /tmpfs was full

It looks like you no longer have a working initial ramdisk image (given that mkinitcpio crashed while generating a new image). If you run mkinitcpio, or reinstall the kernel from a live USB, your system should work again.

Wyrm88

Member

Registered: 2010-05-05

Posts: 53

Re: [SOLVED] Kernel panic after not realizing /tmpfs was full

It looks like you no longer have a working initial ramdisk image (given that mkinitcpio crashed while generating a new image). If you run mkinitcpio, or reinstall the kernel from a live USB, your system should work again.

Thx \hbar, re-running mkinitcpio from a live CD did the trick. Marked as solved.