View previous topic :: View next topic |
Author |
Message |
runny_yolk n00b
Joined: 07 Oct 2002 Posts: 17
|
Posted: Mon Oct 07, 2002 3:20 pm Post subject: Kernel panic on warm boot |
|
|
I am trying Gentoo 1.4rc1 for the first time on my laptop. For some reason, whenever I warm boot (ie shutdown -r ) and the kernel loads and starts trying to mount the root partition, I get the following error message:
VFS: Cannot open root device "hda6" or 03:06
Please append a correct "root=" boot option
The really weird thing is, if I just shutdown the machine and cold boot, everything works just fine. Any pointers on how to start debugging this issue? Here's some information about my system:
Thinkpad 570e one single FUJITSU 12GB IDE drive.
/dev/hda1 ==> /boot 100MB
/dev/hda5 ==> swap 500MB
/dev/hda6 ==> / 10GB
Both / and /boot are ext3, I have ext3, ide support compiled into the kernel (ie not configured as modules). My grub config looks like this:
default 0
timeout 5
title=Linux
root (hd0,0)
kernel /boot/bzImage root=/dev/hda6
My next thought is to try upgrading the BIOS. Is there anything else I should consider trying to get this to work? |
|
Back to top |
|
|
cpdsaorg Guru
Joined: 16 Oct 2003 Posts: 359
|
Posted: Sat Mar 27, 2004 8:06 pm Post subject: |
|
|
Bump!!!
I have this same problem on my thinkpad 570e. I am using kernel version 2.6.3-gentoo-r1. any ideas? |
|
Back to top |
|
|
cpdsaorg Guru
Joined: 16 Oct 2003 Posts: 359
|
Posted: Sat Mar 27, 2004 8:31 pm Post subject: |
|
|
for the record mine looks like this...
Code: | RAMDISK: Couldn't find valid RAM disk image starting at 0
VFS: Cannot open root device "<NULL>" or hda3
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on hda3 |
but on cold boot it works fine.
is it possible if i move my root partition to hda2 and my swap to hda3 and my home to hda4 and leave my boot at hda1 my problem will be soved because root is closer to the start of the drive??
Also, i get:
Code: | RAMDISK: Couldn't find valid RAM disk image starting at 0 |
after cold booting too. so that error message happens in both warm and cold boot. |
|
Back to top |
|
|
|