[SOLVED] Debian Kernel Panic!

AsadMoeen · 02-24-2012, 10:21 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, 04:16 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.

corp769 · 02-24-2012, 05:35 PM

Thread reported - Duplicate of http://www.linuxquestions.org/questi...c-help-931067/

Cheers,

Josh

colucix · 02-25-2012, 01:15 AM

Please post your thread in only one forum. Posting a single thread in the most relevant forum will make it easier for members to help you and will keep the discussion in one place. This thread is being closed because it is a duplicate.