kernel 2.6.10 panic: not syncing: VFS: ...

**skotperez** · 03-01-2005

hi everybody,

i have compiled the 2.6.10 kernel and there were no errors while compiling. when i restart and boot the new version i get the message:

Code:

VFS&#58; Cannot open root device "hdc2" or unknown-block&#40;0,0&#41;
Please append a correct "root=" boot option
kernel panic - not syncing&#58; VFS&#58; Unable to mount root fs on unknown-block&#40;0,0&#41;

hdc2 is the correct partition and i guess menu.lst (grub) is ok:

Code:

title        Debian GNU/Linux, kernel 2.6.10
root        &#40;hd0,1&#41;
kernel     /boot/vmlinuz-2.6.10 root=/dev/hdc2 ro
initrd       /boot/initrd.img-2.6.8-2-386
savedefault
boot

i compiled this way:

Code:

make-kpkg clean
make-kpkg --revision=786&#58;linux-2.6.10 kernel_image

then i did:

Code:

dpkg -i kernel-image-2.6.10_MyKernel2.6.10_i386.deb

finally i take a look of my menu.lst and it looks like i show you above.

what can be gone wrong?
skotperez[/list]

**Flatline** · 03-01-2005

It looks like you're using the initrd.img from your old kernel in that boot configuration.

**skotperez** · 03-03-2005

in grub i added the line

Code:

initrd       /boot/initrd.img-2.6.8-2-386

because i have no initrd.img-2.6.10... or i haven't found in anyplace. i guess it would be save in /boot like the others.

maybe i did something wrong during the compilation and make doesn't create init.rd-2.6.10...[/code]

**waryreacter** · 03-03-2005

I am getting the exact same error, and I am sorry but I still havent sussed it out. what is getting me is succesfully copying the new image over the old one, in order to make the new bzimage, bootable. Help anyone

**Flatline** · 03-03-2005

Waryreacter: You shouldn't have to copy the new image over the old one...they can exist in the same directory as long as their filenames are different. You just have to specify the new image in your bootloader.

Skotperez: Try:

Code:

cp /usr/src/linux-2.6.10/System.map /boot/System.map-2.6.10
mkinitrd -o /boot/initrd-2.6.10 /lib/modules/2.6.10

I think that will make an initrd image for you.

**skotperez** · 03-03-2005

thanks a lotk, Flatline.

your solution works!!
i think that the way i compiled didn't create the initrd image. why? or maybe it was anything in relation with 2.6.10 kernel. what do you think?

skotperez

**Flatline** · 03-03-2005

I think it's just one of the many options in your config (although I haven't compiled a kernel from scratch in probably a year, so don't hold me to that)...there's so many that it's easy to miss one.

**anumolu** · 05-29-2005

hi i had recompiled the kernel with 2.6.11 , everything went fine while installing but in the end it has shown so many dependencies. after i restarted my machine through new kernel it got strucked giving
"Mounting root file System
mount : error 19 mounting ext3
pivotroot: pivot_root(/sysroot,/sysroot/initrd) failed:2
umount /initrd/proc failed: 2
Freeing unused kernel memory : 268k freed
Kernel panic - not syncing: No init found . Try passing init = option to kernel "
I tried the above procedure it didn't wrk
for "mkinitrd -o /boot/initrd-2.6.10 /lib/modules/2.6.10"
it had accepted only "mkinitrd /boot/initrd-2.6.11.img 2.6.11" and given 2.6.11 is already there .

CAn any one could help me to recttify this problem.

**Flatline** · 05-29-2005

So you have created an initrd.img file? Is it specified to load in your bootloader config?

**anumolu** · 05-30-2005

"cp /usr/src/linux-2.6.11/System.map /boot/System.map-2.6.11"
it copied tht system.map-2.6.11 to boot
after that
" mkinitrd /boot/initrd-2.6.11.img 2.6.11"
this option it took but given tht 2.6.11 is already there

i am new to this i don't know rather than the above
Help me what is initrd??? what 's the purpose of tht??

Thread Tools

Display

kernel 2.6.10 panic: not syncing: VFS: ...

Posting Permissions