LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)
-   -   New kernel boot failure. (https://www.linuxquestions.org/questions/linux-newbie-8/new-kernel-boot-failure-453187/)

tripmix 06-09-2006 10:30 AM

New kernel boot failure.
 
I just upgraded from Debian stable to testing and found out I needed a new kernel to. I compiled and installed in the normal debian way useing my old config file.

I get this error on boot:

VFS: Cannot open root device "hda2" or unknown-block(0,0)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(0,0)

This is my grub menu file:

title Debian GNU/Linux, kernel 2.6.15
root (hd0,1)
kernel /boot/vmlinuz-2.6.15 root=/dev/hda2 ro
savedefault
boot

title Debian GNU/Linux, kernel 2.6.15 (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.15 root=/dev/hda2 ro single
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-386
root (hd0,1)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda2 ro
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot

title Debian GNU/Linux, kernel 2.6.8-2-386 (recovery mode)
root (hd0,1)
kernel /boot/vmlinuz-2.6.8-2-386 root=/dev/hda2 ro single
initrd /boot/initrd.img-2.6.8-2-386
savedefault
boot

Kernel 2.6.8 boots fine, but 2.6.15 fails. File says to boot on (0,1) while boot looks like it tries to boot at (0,0) for the 2.6.15 kernel.

Sure hope someone here knows whats going on, cuz I sure can't figgure it out.

Thanks for any help.

PS: don't know if this is important but my device.map has this entery:
(hd0) /dev/hda

kaz2100 06-09-2006 10:35 AM

Did you use your old "config"?

If yes, run
Code:

make oldconfig
then install new kernel, then see what happens.

If no, wait until some other penguin helps.

tripmix 06-09-2006 10:56 AM

I asume I have to run make oldconfig then recompile the kernel...?
Like:
make-kpkg clean
make oldconfig
make-kpkg --revision=custom2.6.15 kernel_image

Right..?

weibullguy 06-09-2006 11:14 AM

You may want to edit your grub.conf to include the initrd line for your new kernel.

tripmix 06-09-2006 11:29 AM

Good point... can't belive I didnt notice that...
Anyway there is no initrd.img for my new kernel in /boot
What could have gone wrong? Well, atleast now I have something to work with.

Beads 06-09-2006 11:59 AM

Tripmix, try removing the root=/dev/hda2 ro statement from your grub list. Believe it or not, it worked for me having the same problem!

tripmix 06-09-2006 01:18 PM

Thanks for all the tips, I got it now. All I had to do was:

mkinitrd -o /boot/initrd.img-2.6.15 2.6.15

Then add the new img that was created to grubs menu.lst


All times are GMT -5. The time now is 06:31 AM.