Results 1 to 10 of 12
I'd installed and compiled the Kernel 2.6.12... but when i boot it, i got this error message:
Code:
VFS: Cannot open root device "hda6" or unknown-block(0,0)
Please append a correct ...
- 08-05-2005 #1Just Joined!
- Join Date
- Apr 2005
- Posts
- 11
problems with kernel 2.6.12
I'd installed and compiled the Kernel 2.6.12... but when i boot it, i got this error message:
what should i do??? what is this error for??Code:VFS: Cannot open root device "hda6" 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)
- 08-05-2005 #2forum.guy
- Join Date
- May 2004
- Location
- arch linux
- Posts
- 18,086
Looks like a possible problem with the bootloader. If you can post the contents of your /grub/menu.lst file, maybe someone can help you.
- 08-05-2005 #3Linux Engineer
- Join Date
- Nov 2004
- Location
- Ft. Polk, LA
- Posts
- 796
/boot/grub/menu.lst
Originally Posted by Ozar
- 08-06-2005 #4
If you're sure you compiled support for the root file-system then as mentioned post your menu.lst and it would also be helpful to provide your partition scheme.
Code:$ su # fdisk -l
It may be that your sole purpose in life is simply to serve as a warning to others.
- 08-06-2005 #5Just Joined!
- Join Date
- Apr 2005
- Posts
- 11
this is my menu.lst:
and this is my partition table scheme:Code:title Debian GNU/Linux, kernel 2.6.12 root (hd0,4) kernel /vmlinuz-2.6.12 root=/dev/hda6 ro savedefault boot title Debian GNU/Linux, kernel 2.6.12 (recovery mode) root (hd0,4) kernel /vmlinuz-2.6.12 root=/dev/hda6 ro single savedefault boot title Debian GNU/Linux, kernel 2.4.27-2-386 root (hd0,4) kernel /vmlinuz-2.4.27-2-386 root=/dev/hda6 ro initrd /initrd.img-2.4.27-2-386 savedefault boot title Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode) root (hd0,4) kernel /vmlinuz-2.4.27-2-386 root=/dev/hda6 ro single initrd /initrd.img-2.4.27-2-386 savedefault boot
how i can compile the support for root file-system ??? and also what is root file system??Code:Disk /dev/hda: 81.9 GB, 81961123328 bytes 255 heads, 63 sectors/track, 9964 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Device Boot Start End Blocks Id System /dev/hda1 1 9964 80035798+ 5 Extended /dev/hda5 * 1 486 3903732 83 Linux /dev/hda6 487 1702 9767488+ 83 Linux /dev/hda7 1703 2918 9767488+ 83 Linux /dev/hda8 2919 3647 5855661 83 Linux /dev/hda9 3648 4620 7815591 83 Linux /dev/hda10 4621 5593 7815591 83 Linux /dev/hda11 5594 6566 7815591 83 Linux /dev/hda12 6567 7539 7815591 83 Linux /dev/hda13 7540 7685 1172713+ 82 Linux swap / Solaris /dev/hda14 7686 9964 18306036 83 Linux
- 08-06-2005 #6Just Joined!
- Join Date
- Apr 2005
- Posts
- 11
HEY... WHAT SHOULD I DO???
- 08-06-2005 #7Please be a little discrete. I just woke up.
Originally Posted by lin_world 
The problem would appear to be that you don't have the correct kernel and initrd.img file names listed in your menu.lst. I could make a guess at what they should be, but instead please just post the contents of the following directoy: /boot.
To do this open a terminal and issue the command below.
Then copy/paste the output.
$ ls /boot
Also, where is your Debian installation?
Is the root directory on hda5?
Do you have a separate partition for your /boot path?
At present you have it setup in the menu.lst that:
root is on hda5 and /boot is on hda6
Is this correct?It may be that your sole purpose in life is simply to serve as a warning to others.
- 08-07-2005 #8Just Joined!
- Join Date
- Apr 2005
- Posts
- 11
this is my /boot directory:
and you r right : hda5 is my root directory and hda6 is my boot directory...Code:config-2.4.27-2-386 initrd.img-2.4.27-2-386.orig vmlinuz-2.4.27-2-386 config-2.6.12 lost+found vmlinuz-2.6.12 grub System.map-2.4.27-2-386 initrd.img-2.4.27-2-386 System.map-2.6.12
- 08-07-2005 #9If hda5 is root and hda6 is /boot then you need the setup below.
Originally Posted by lin_world
The line 'root (hd0,x)' refers to the /boot partition
The portion 'root=/dev/hdax' refers to the root partition.
(hd0,1) = hda2; (hd0,2) = hda3; (hd0,3) = hda4; and so forth.
You also didn't create a initrd.img for the 2.6 kernel.
This may or may not be necessary depending on you methods.
Code:title Debian GNU/Linux, kernel 2.6.12 root (hd0,5) kernel /vmlinuz-2.6.12 root=/dev/hda5 ro savedefault boot title Debian GNU/Linux, kernel 2.6.12 (recovery mode) root (hd0,5) kernel /vmlinuz-2.6.12 root=/dev/hda5 ro single savedefault boot title Debian GNU/Linux, kernel 2.4.27-2-386 root (hd0,5) kernel /vmlinuz-2.4.27-2-386 root=/dev/hda5 ro initrd /initrd.img-2.4.27-2-386 savedefault boot title Debian GNU/Linux, kernel 2.4.27-2-386 (recovery mode) root (hd0,5) kernel /vmlinuz-2.4.27-2-386 root=/dev/hda5 ro single initrd /initrd.img-2.4.27-2-386 savedefault boot
It may be that your sole purpose in life is simply to serve as a warning to others.
- 08-08-2005 #10Just Joined!
- Join Date
- Apr 2005
- Posts
- 11
thanks St. Joe,
but i got a mistake here: hda6 is root and hda5 is /boot ...
another question, how i can make initrd.img and is it really necessary, and alsoo what does this initrd.img do????
thanks again


Reply With Quote
