[SOLVED] Kernel Panic Help

AsadMoeen · 02-24-2012, 10:07 AM

I compiled a new kernel 3.2 with RT patch. Installation went fine. I did not use initrd image because I used the correct drivers for the setup. On booting process, it gives me this error.

Code:

kernel panic not syncing VFS unable to mount on unknown device etc.

While the original kernel works fine. On Googling it appears to be a problem with the device its mounting on. Here is my grub cfg content:

Code:

menuentry 'Debian GNU/Linux, with Linux 3.2.6-rt13' --class debian --class gnu-linux --class gnu --class os {
	insmod part_msdos
	insmod ext2
	set root='(hd0,msdos1)'
	search --no-floppy --fs-uuid --set 4c912b0a-53a1-494e-b8c1-359686e1fbe6
	echo	'Loading Linux 3.2.6-rt13 ...'
	linux	/boot/vmlinuz-3.2.6-rt13 root=/dev/xvda1 ro  quiet
}

menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64' --class debian --class gnu-linux --class gnu --class os {
	insmod part_msdos
	insmod ext2
	set root='(hd0,msdos1)'
	search --no-floppy --fs-uuid --set 4c912b0a-53a1-494e-b8c1-359686e1fbe6
	echo	'Loading Linux 2.6.32-5-amd64 ...'
	linux	/boot/vmlinuz-2.6.32-5-amd64 root=UUID=4c912b0a-53a1-494e-b8c1-359686e1fbe6 ro  quiet
	echo	'Loading initial ramdisk ...'
	initrd	/boot/initrd.img-2.6.32-5-amd64

It appears both are trying to mount on /dev/xvda1

What could be the solution?

liberalchrist · 02-24-2012, 05:55 PM

Try editing the new menu entry and use the same "root=UUID=" statement as the old one. The new kernel doesn't change where the root file system is.

AsadMoeen · 02-24-2012, 11:38 PM

Okay so I remove /dev/xvda1?

AsadMoeen · 02-25-2012, 12:26 AM

Okay I tried to make it similar to the working Kernel by setting UUID but it still gave the same error.

AsadMoeen · 02-25-2012, 01:10 AM

I might also mention that while compiling the kernel and after setting up the config, while I was doing "make":

It asked me a lot of questions regarding different things like (N/y) (NEW) but I did not enter anything as I was unaware of them all so I just ignored and pressed enter to approximately all of the 300 times it asked me while compiling and installing. I don't know if thats right but I think it should be good to go if that was all in the config.

AsadMoeen · 02-25-2012, 04:16 AM

On creating initial ramdisk file, it booted successful.

But how to boot without it?

liberalchrist · 02-25-2012, 07:08 AM

You seem to have made some progress while I was sleeping. How you choose to answer the 300 questions does have a bearing on how you boot your kernel. To boot without a ramdisk, you have to compile support for your file system directly into the kernel. If you compile it as a module instead, it doesn't load right away and you have to have the ramdisk as a temporary file system until the kernel boots. Here is the best free resource I know on kernel configuration: http://www.kroah.com/lkn/. This book is a little older, but it is free and the basics of configuration are still the same.

Anders Lind · 02-25-2012, 09:24 PM

Quote:

Originally Posted by AsadMoeen

On creating initial ramdisk file, it booted successful.

But how to boot without it?

Hi,
I have similar problem also,
Can you say more about your solution? I don't quite get it.
Thanks

AsadMoeen · 03-16-2012, 02:08 AM

Just recompile with the proper drivers and original kernel's config file or modifying that.

http://wiki.fragaholics.de/index.php...el_Compilation

That may help.