[Solved]Kernal Panic after installation

abnordude · 2012-04-30 09:15:21

I had debian...
I installed arch...
When I rebooted, grub list didnt show debian...
So, I went to grub4dos from lucid puppy...
Then I can boot Debian...
But when I try arch linux...

I get sort of an error like...

Kernal Panic - not syncing vfs unable to mount root fs on......

Last edited by abnordude (2012-05-04 05:35:02)

abnordude · 2012-04-30 09:26:04

Here is my grub.cfg......
Hope it helps.....

#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
load_env
fi
set default="0"
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}

function load_video {
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
}

insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
if loadfont /usr/share/grub/unicode.pf2 ; then
set gfxmode=640x480
load_video
insmod gfxterm
fi
terminal_output gfxterm
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
set locale_dir=($root)/boot/grub/locale
set lang=en
insmod gettext
set timeout=5
### END /etc/grub.d/00_header ###

### BEGIN /etc/grub.d/05_debian_theme ###
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
insmod png
if background_image /usr/share/images/desktop-base/spacefun-grub.png; then
set color_normal=light-gray/black
set color_highlight=white/black
else
set menu_color_normal=cyan/blue
set menu_color_highlight=white/blue
fi
### END /etc/grub.d/05_debian_theme ###

### BEGIN /etc/grub.d/10_linux ###
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,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=7582e816-3a70-4de8-8608-6a1375a23b87 ro quiet
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
menuentry 'Debian GNU/Linux, with Linux 2.6.32-5-amd64 (recovery mode)' --class debian --class gnu-linux --class gnu --class os {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
echo 'Loading Linux 2.6.32-5-amd64 ...'
linux /boot/vmlinuz-2.6.32-5-amd64 root=UUID=7582e816-3a70-4de8-8608-6a1375a23b87 ro single
echo 'Loading initial ramdisk ...'
initrd /boot/initrd.img-2.6.32-5-amd64
}
### END /etc/grub.d/10_linux ###

### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###

### BEGIN /etc/grub.d/20_memtest86+ ###
menuentry "Memory test (memtest86+)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
linux16 /boot/memtest86+.bin
}
menuentry "Memory test (memtest86+, serial console 115200)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
linux16 /boot/memtest86+.bin console=ttyS0,115200n8
}
menuentry "Memory test (memtest86+, experimental multiboot)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
multiboot /boot/memtest86+_multiboot.bin
}
menuentry "Memory test (memtest86+, serial console 115200, experimental multiboot)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos3)'
search --no-floppy --fs-uuid --set 7582e816-3a70-4de8-8608-6a1375a23b87
multiboot /boot/memtest86+_multiboot.bin console=ttyS0,115200n8
}
### END /etc/grub.d/20_memtest86+ ###

### BEGIN /etc/grub.d/30_os-prober ###
menuentry "Arch (on /dev/sda1)" {
insmod part_msdos
insmod ext2
set root='(hd0,msdos1)'
search --no-floppy --fs-uuid --set ad3e5a76-df67-44eb-a418-4e01dd07bc5d
linux /boot/vmlinuz-linux root=/dev/sda1
initrd /boot/initramfs-linux.img
}
### END /etc/grub.d/30_os-prober ###

### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###

### BEGIN /etc/grub.d/41_custom ###
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###

abnordude · 2012-05-04 05:16:03

I found out the solution...

It was rather a simple one....

I just did a 'sudo update-grub' from debian, and it detected arch....

Thanks everyone for the help....

abnordude · 2012-05-04 05:16:54

Also....How to mark thread as 'solved'?

Gcool · 2012-05-04 05:24:08

Good to hear you managed to fix it.

For info about how to mark your thread as [SOLVED] and more (using code tags for bigger outputs,...), have a look at the forum rules.

Arch Linux

#1 2012-04-30 09:15:21

[Solved]Kernal Panic after installation

#2 2012-04-30 09:26:04

Re: [Solved]Kernal Panic after installation

#3 2012-05-04 05:16:03

Re: [Solved]Kernal Panic after installation

#4 2012-05-04 05:16:54

Re: [Solved]Kernal Panic after installation

#5 2012-05-04 05:24:08

Re: [Solved]Kernal Panic after installation

Board footer