[SOLVED] fixing kernel panic

vienswuer · 04-29-2016, 10:17 PM

After updating Manjaro, I wasn't able to boot into it again. I got the error message '/boot/vmlinuz-310-x86_64 not found' which I understand is a Kernel panic.
So, I started Sabayon instead, which is installed in a separate partition, and chrooted into Manjaro. Firstly, I made a 'pacman -Syyu'. And then tried to install a new kernel following Manjaro's wiki (https://wiki.manjaro.org/index.php/M...ng_New_Kernels). So: 'sudo mhwd-kernel -i linux313'. But terminal returns this error message: 'error: no targets specified (use -h for help)' I couldn't troubleshoot that since not much info about that particular error appears within forums. I'm listening.

PD Updating went just fine.

Ztcoracat · 04-30-2016, 12:18 AM

I would start here and troubleshoot:-
https://wiki.archlinux.org/index.php/Kernel_Panics

Was there a patch to the kernel or an upgrade?

The kernel is in /usr/src/ check and see if it's still there.

I'm not sure what file in Manjaro your initrd would be but in Slackware it's in lilo.conf.
I'm guessing it's a grub.d file.
You might have to create a new initrd <or> Initial Ram Disk. Try the Arch WiKi first.

Quote:

error: no targets specified

Where you in the directory with the new kernel that you downloaded or were you just re-compiling the kernel you already had?

Was this the whole error message?

Code:

no targets specified and no makefile found

-::-You might want to post the output in the terminal when this error occurs so we can take a look at what is going on.-::-

syg00 · 04-30-2016, 01:48 AM

File not found is certainly not a kernel panic. Probably a simple grub configuration issue - mkconfig would be my first step to fixing it. Building a new kernel from source seems a bit extreme - but given that mhwd-kernel is touted as "Manjaros own" wouldn't their fora be better to pursue failures like this ?.

vienswuer · 04-30-2016, 06:17 AM

[QUOTE=Ztcoracat;5538539]I would start here and troubleshoot:-
https://wiki.archlinux.org/index.php/Kernel_Panics

The kernel is in /usr/src/ check and see if it's still there.

Was this the whole error message?

Code:

no targets specified and no makefile found

Yes, that was the whole error message. And the kernel is in that directory. Now checking the initrd you mentioned.

Ztcoracat · 04-30-2016, 08:31 PM

Quote:

Originally Posted by syg00

File not found is certainly not a kernel panic. Probably a simple grub configuration issue - mkconfig would be my first step to fixing it. Building a new kernel from source seems a bit extreme - but given that mhwd-kernel is touted as "Manjaros own" wouldn't their fora be better to pursue failures like this ?.

How would we know if it's a grub config issue?
Would the grub.d or the grub.cfg be compromised?

I agree with you, a new kernel is not only extreme but most likely not needed.

syg00 · 04-30-2016, 08:42 PM

Quote:

Originally Posted by Ztcoracat

How would we know if it's a grub config issue?
Would the grub.d or the grub.cfg be compromised?

Probably neither. I am guessing grub.cfg includes a kernel that has been deleted by the update. mkconfig is a quick and easy fix in that case.

Ztcoracat · 04-30-2016, 08:47 PM

syg00:

I've never used the mkconfig command. I've updated Grub before-
I'll read the man page for it-

Maybe these links will help?

https://www.gnu.org/software/grub/ma...dmkconfig.html
https://wiki.archlinux.org/index.php/GRUB

Ztcoracat · 04-30-2016, 08:49 PM

Quote:

Originally Posted by syg00

Probably neither. I am guessing grub.cfg includes a kernel that has been deleted by the update. mkconfig is a quick and easy fix in that case.

Got it-
A kernel that has been deleted from the grub.cfg file makes sense.

In that case OP would just have to edit the grub.cfg file and put the image back (menu entry) in the file and than run mkconfig? (make sure I understand while I'm learning form you)

syg00 · 04-30-2016, 09:06 PM

mkconfig is what builds grub.cfg - no need to risk finger-checks.

Ztcoracat · 04-30-2016, 09:07 PM

Quote:

Yes, that was the whole error message

In that case either the make file was missing, you were in the wrong directory or the tar.bz was corrupt.It doesn't look like you need a new kernel as syg00 said that's a bit extreame.

I'm waiting for him to answer me on the mkconfig and the grub.cfg file.

In the meantime if you want to take a look at the grub.cfg file it should be in /boot/grub2/grub.cfg.
Here's what my menu entry looks like for Korora that is based on Fedora.

Code:

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Korora (4.4.8-300.fc23.x86_64) 23 (Coral)' --class korora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.2.5-300.fc23.x86_64-advanced-a25329de-271d-453a-8d62-4d40c0f9c4ae' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'

The entry for Sabayon and Manjaro should be similar to my menuentry.

Ztcoracat · 04-30-2016, 09:13 PM

Quote:

Originally Posted by syg00

mkconfig is what builds grub.cfg - no need to risk finger-checks.

Finger checks? Do clarify:-

vienswuer · 05-01-2016, 12:25 AM

Quote:

Originally Posted by Ztcoracat

In that case either the make file was missing, you were in the wrong directory or the tar.bz was corrupt.It doesn't look like you need a new kernel as syg00 said that's a bit extreame.

I'm waiting for him to answer me on the mkconfig and the grub.cfg file.

In the meantime if you want to take a look at the grub.cfg file it should be in /boot/grub2/grub.cfg.
Here's what my menu entry looks like for Korora that is based on Fedora.

Code:

### BEGIN /etc/grub.d/10_linux ###
menuentry 'Korora (4.4.8-300.fc23.x86_64) 23 (Coral)' --class korora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.2.5-300.fc23.x86_64-advanced-a25329de-271d-453a-8d62-4d40c0f9c4ae' {
	load_video
	set gfxpayload=keep
	insmod gzio
	insmod part_msdos
	insmod ext2
	set root='hd0,msdos1'

The entry for Sabayon and Manjaro should be similar to my menuentry.

Yup, my grub.cfg looks the same for Manjaro entrie

Ztcoracat · 05-02-2016, 12:54 PM

After reading about the kernel online I learned that if the kernel doesn't have the driver for your rootfs or a driver for your SATA bus and etc. your kernel will panic; if it boots and can't access the necessary disks, partitions and or files.

-::-This wouldn't be the first time that I've heard of an update breaking drivers.-::-

Have you tried what is recommended in the Arch Wiki for kernel panic?

I hope you have performed a recent back up.-

http://linux.die.net/man/2/chroot

colorpurple21859 · 05-02-2016, 01:22 PM

This

Quote:

I got the error message '/boot/vmlinuz-310-x86_64 not found

indicates the kernel that grub is trying to load doesn't exist as syg00 has suggested.

Quote:

So, I started Sabayon instead, which is installed in a separate partition, and chrooted into Manjaro.

Did you try running grub-mkconfig after chrooting into Manjaro to see if that will fix the problem?

vienswuer · 05-11-2016, 11:59 AM

Quote:

Originally Posted by colorpurple21859

This indicates the kernel that grub is trying to load doesn't exist as syg00 has suggested. Did you try running grub-mkconfig after chrooting into Manjaro to see if that will fix the problem?

It didn't solve the problem.