LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Kernel (https://www.linuxquestions.org/questions/linux-kernel-70/)
-   -   kernel 2.6.16.9 panic at boot : Failure-22 (https://www.linuxquestions.org/questions/linux-kernel-70/kernel-2-6-16-9-panic-at-boot-failure-22-a-438399/)

slone 04-24-2006 12:45 PM

kernel 2.6.16.9 panic at boot : Failure-22
 
I'm tring to update my kernel version on my very old PentuimII PC here. Kernel 2.6.19.9 compiles just fine, but at boot I get the following kenel panic message:

RAMDISK: cramfs filesysem found at block 0
RAMDISK: Loading 1420KiB [1 disk] into ram disk... done
Mount JFS Failure: -22
Kernel panic - not syncing: VFS: Unable to mount root fs on unkown-block(2,3)


My primary hda1 is a IDE hard disk and kenel detects it just fine a few line before that. So please if ayone knows how to get out of this ... Should I avoid configuring ram disks in menuconfig??
Thanks in advance.

sundialsvcs 04-24-2006 04:33 PM

There are two possibilities...

(1) Where is the boot device? Did you specify it correctly when you built the boot-loader (Grub or Lilo) specification? It think's it's device (2,3); does that make sense?

(2) It's mounting a "JFS" filesystem? Really? Is that right? If it is right, did you properly format the drive?

The RAMDISK messages probably aren't part of the puzzle because it appears to me that they succeeded. What they were doing is loading the "initial RAM-disk" (initrd, initramfs), which controls the boot-process on most stock distros. It superficially appears to me that whatever went wrong, happened next.

rick.2g 04-24-2006 11:39 PM

Are you using the cramfs for anything in particular? That's usually used on portable devices - I'm not sure the initrd needs it.

slone 04-26-2006 09:29 AM

Thanks a lot for the advices. Block(2,3)seemed to be correct for hda2 which was root. Unfortunately ext3 partition was damaged and I tried to fix it with fsck, but that finally killed it. Then I reinstalled the whole debian sarge from the beginnig, and repartitioned. Now it's all fixed, but with brutal force. This time I've really given up :cry:


All times are GMT -5. The time now is 03:20 AM.