VFS: unable to mount fs root not found -block(0,0)

  • sidharth
  • Student
  • Student
  • sidharth
  • Posts: 68
  • Loc: india

Post 3+ Months Ago

Quote:
VFS: Cannot open root device "ram0" 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)



AFTER compliling complete kernel with following set of commands

Code: [ Select ]
make menuconfig
make -j2 bzImage
make modules
make modules_install
  1. make menuconfig
  2. make -j2 bzImage
  3. make modules
  4. make modules_install


everything fine added following entry in grub.conf

Code: [ Select ]
title new
root(hd0,7)             # root is on /dev/hda7
kernel /newkernel ro root=/dev/hda7
  1. title new
  2. root(hd0,7)             # root is on /dev/hda7
  3. kernel /newkernel ro root=/dev/hda7



during boot THIS new option lead to above mentioned error.....
anybody can tell.....WHAT CAN BE THE POSSIBLE SOLUTION
Moderator Remark: Added code tags
  • Anonymous
  • Bot
  • No Avatar
  • Posts: ?
  • Loc: Ozzuland
  • Status: Online

Post 3+ Months Ago

  • AnarchY SI
  • Web Master
  • Web Master
  • User avatar
  • Posts: 2521
  • Loc: /usr/src/MI

Post 3+ Months Ago

well did you move the new kernel from the folder it was compiled to into the boot folder on your hard drive? and if so, then the path to it would not be /newkernel, it would be /boot/newkernel
why are you specifying the ro option? verify that the new kernel you compiled exists in /boot and make sure its called 'newkernel' or make sure it has whatever name you want it to (id do something more descriptive) and then add an entry such as this to grub:
Quote:
title new
root(hd0,6)
kernel /boot/newkernel root=/dev/hda7

for the root() entry, its a 0 based counting system so /dev/hda1 would be hd0,0 /dev/hda2 would be hd0,1, etc
  • sidharth
  • Student
  • Student
  • sidharth
  • Posts: 68
  • Loc: india

Post 3+ Months Ago

i copied that root option already mentioned in grub.conf

as i m already having fedora 6 installed and grub.conf was like this before i edit

Quote:
title fedora
root(hd0,7)
kernel vmlinux ro root=LABEL=/1 rhgb quiet
initrd name


now i changd it to

Quote:
title fedora
root(hd0,7)
kernel vmlinux ro root=LABEL=/1 rhgb quiet
initrd name
title new
root(hd0,7)
kernel /newkernel ro root=LABEL=/1 rhgb quiet


isnt it fine or i have to make kernel name /boot/newkernel
or there is some other problem as well
  • AnarchY SI
  • Web Master
  • Web Master
  • User avatar
  • Posts: 2521
  • Loc: /usr/src/MI

Post 3+ Months Ago

ok, some clarity or maybe a little background information would help. if the partition is /dev/hda7, it would be (hd0,6). if the partition is /dev/hda8 it would be (hd0,7). do you understand that much? you're going to need the initrd for the entry titled "new" (i knew there was something missing..) here is a portion of my grub.conf from my fedora installation:
Quote:
title Fedora Core (2.6.18-1.2868.fc6)
root (hd0,2)
kernel /boot/vmlinuz-2.6.18-1.2868.fc6 ro root=LABEL=/ rhgb quiet
initrd /boot/initrd-2.6.18-1.2868.fc6.img

as you can see, its on /dev/hda3, and the kernel and initrd image are both inside a folder titled boot which exists on the root of the hard drive.
now, does the first entry you have up there titled "fedora" allow you to boot into fedora?
  • sidharth
  • Student
  • Student
  • sidharth
  • Posts: 68
  • Loc: india

Post 3+ Months Ago

i have boot on different partition....
thats why in my grub.conf it was written like this

Quote:
title fedora

root(hd0,7)

kernel /vmlinux ro root=LABEL=/1 rhgb quiet

initrd /initrd.img


now how can i compile new initrd for this new kernel
  • alias8700
  • Beginner
  • Beginner
  • alias8700
  • Posts: 43

Post 3+ Months Ago

Code: [ Select ]
mkinitrd -o /path/to/new/initrdfile <kernelversion>


Should do the trick for you. If you have any problems try

Code: [ Select ]
man mkinitrd
  • sidharth
  • Student
  • Student
  • sidharth
  • Posts: 68
  • Loc: india

Post 3+ Months Ago

ok..........i got problem solved .......but new problem is there kernel is showing a error........

init not found .try passing init=option to the kernel

help!
  • alias8700
  • Beginner
  • Beginner
  • alias8700
  • Posts: 43

Post 3+ Months Ago

Try changing your kernel entry

Code: [ Select ]
kernel /vmlinux ro root=LABEL=/1 rhgb quiet


to something like

Code: [ Select ]
kernel /vmlinux root=/dev/hda7 rhgb quiet


Make sure all parameters and paths are correct.
  • webseoservice
  • Newbie
  • Newbie
  • webseoservice
  • Posts: 7

Post 3+ Months Ago

sidharth wrote:
ok..........i got problem solved .......but new problem is there kernel is showing a error........

init not found .try passing init=option to the kernel

help!


PM me, R U indian? will solve this

Post Information

  • Total Posts in this topic: 9 posts
  • Users browsing this forum: No registered users and 68 guests
  • You cannot post new topics in this forum
  • You cannot reply to topics in this forum
  • You cannot edit your posts in this forum
  • You cannot delete your posts in this forum
  • You cannot post attachments in this forum
 
 

© 1998-2014. Ozzu® is a registered trademark of Unmelted, LLC.