Kernel Panic - Assuming its the new kernel.

Cirdan · 2006-09-29 05:51:17

I did the pacman -Syu and updated eveything. Now all of a suddent I get a kernel panic ...

No filesystem could mount root, tried:
Kernel Panic = not syncing: VFS: Unable to mount root fs on unknown-block(0,)

I know there was problems with the mkinitrd/mkinitramfs and it not being supported...but I have no idea at all what it is nor what udev is. Is there a way to boot the old kernel from grub?

Thanks

Deranger · 2006-09-29 06:49:21

Pay more attention to pacman's output, it's all explained when you install 2.6.18.

Change your bootloader (/boot/grub/menu.lst) to load the correct images.

initrd26.img is now known as kernel26.img
initrd26-full.img is now known as kernel26-fallback.img

rasat · 2006-09-29 15:27:32

The Lone Deranger wrote:

Pay more attention to pacman's output, it's all explained when you install 2.6.18.

Nothing in particular was said except "Generating image '/boot/kernel26.img'...SUCCESS". During 2.6.17.x upgrades it was mentioned mkinitrd will be removed in 2.6.18. I was surprised it was not removed but replaced, thereby getting the kernel panic error. And the worst part, the new update doesn't support "vga=788", so my screen got blank.

Mr Green · 2006-09-29 15:41:41

Not sure without checking but when kernel upgrades it only states check LILO ...

not grub!!!!!

rasat · 2006-09-29 15:47:55

If its then LILO or Grub, what's the replacement for this line:
initrd=/boot/initrd26.img

???=/boot/kernel26.img

phrakture · 2006-09-29 15:58:43

rasat wrote:

Nothing in particular was said

Hm, I guess I didn't notice that. Must have been an oops on our part.

rasat wrote:

And the worst part, the new update doesn't support "vga=788", so my screen got blank.

Interesting. This is unrelated to mkinitcpio - sounds like framebuffer changes...

Cirdan · 2006-09-30 00:22:08

So what do I need to do? Change the kernel that is loaded like rasat said?

EDIT:

I booted up D Small Linux, mounted the hard drive and went into the boot directory. The weird thing is, is there is nothing in there. I'm thinking its because of write protection. How would I fix the problem if I can't access the files? Do I need to reinstall, if so...what do I need to do to avoid this mess?

phrakture · 2006-09-30 04:43:56

Cirdan wrote:

The weird thing is, is there is nothing in there. I'm thinking its because of write protection.

Your boot is probably on another partition (hda1 ?) which you need to mount.

Also note, you're not changing the kernel that you boot, you're changing the initial ramdisk that is used. If you use grub, you can do this directly from grub by hitting "e".

Cirdan · 2006-09-30 06:28:22

Awesome, thanks for you help!

Arch Linux

#1 2006-09-29 05:51:17

Kernel Panic - Assuming its the new kernel.

#2 2006-09-29 06:49:21

Re: Kernel Panic - Assuming its the new kernel.

#3 2006-09-29 15:27:32

Re: Kernel Panic - Assuming its the new kernel.

#4 2006-09-29 15:41:41

Re: Kernel Panic - Assuming its the new kernel.

#5 2006-09-29 15:47:55

Re: Kernel Panic - Assuming its the new kernel.

#6 2006-09-29 15:58:43

Re: Kernel Panic - Assuming its the new kernel.

#7 2006-09-30 00:22:08

Re: Kernel Panic - Assuming its the new kernel.

#8 2006-09-30 04:43:56

Re: Kernel Panic - Assuming its the new kernel.

#9 2006-09-30 06:28:22

Re: Kernel Panic - Assuming its the new kernel.

Board footer