December 12, 2017, 02:06:12 PM

News : LinuxSolved.com Linux Help Community Forum..


Author Topic: Kernel Panic: VFS: Unable to mount root fs on unknown-block  (Read 4860 times)

Offline Agent007

  • Linux Noob !
  • *
  • Posts: 17
Kernel Panic: VFS: Unable to mount root fs on unknown-block
« on: August 13, 2005, 10:57:00 AM »
I have installed Fedora Core 3 and installed all features. I have not found sources of kernel. I have downloaded the latest stable sources of kernel from www.kernel.org .
I have compiled it.

make mrproper
make xconfig (configuration was made)
make dep
Command “make dep” answered that this is not necessary.
make clean
make bzImage
make modules
make modules install

I have copied bzImage to /boot/vmlinuz
I have made chages in grub.conf
When I restarted I have got the following Error:
kernel panic - not syncing : VFS: unable to mount root FS on unknown-block (0, 0)



What I have noticed is that no initrd.img file was generated in compilation folder

I am not sure system.map is proper
What is for system.map and how it should be created or when it is created

EXTRAVERSION is not added to for the image and to any files

I think that problem is in it.

What do you think guys. Any body faced with this situation.

What for is initrd.img?

What for is bootspalsh. Can initrd.img be replace with bootsplash somehow?

Why Command “make dep” answered that this is not necessary?

Thanks in advance

Offline xyz

  • New Member
  • Posts: 2
Re: Kernel Panic: VFS: Unable to mount root fs on unknown-block
« Reply #1 on: June 11, 2007, 12:17:53 PM »
can you give your grub.conf file?

Offline xyz

  • New Member
  • Posts: 2
Re: Kernel Panic: VFS: Unable to mount root fs on unknown-block
« Reply #2 on: June 11, 2007, 12:21:03 PM »
initrd can be generated by

mkinitrd  <initrd file name > <Kernel version>
e.g
mkinitrd  initrd-TEST 2.6.10


for installing modules

make modules_install is necessary ...if you are bulilding cfs as module

Offline gauravbajaj

  • LST CareTaker
  • Experienced
  • *****
  • Posts: 658
Re: Kernel Panic: VFS: Unable to mount root fs on unknown-block
« Reply #3 on: June 13, 2007, 07:28:06 AM »
Hi,
Follow mentioned below steps from the scratch:

make mrproper
make oldconfig--------------------------------> This step is also necessary
make xconfig  -------> Be sure here to enable support for ext2 and ext3
make dep
make clean
make bzImage
make modules
make modules_install   -------> it should be make modules_install not make modules install
make install ------------------> This step is also necessary

After that reboot the system and then tell me.......about that..

Thanks
Gaurav
« Last Edit: June 13, 2007, 07:30:39 AM by gauravbajaj »

Offline dragoncity99

  • LST CareTaker
  • Experienced
  • *****
  • Posts: 551
Re: Kernel Panic: VFS: Unable to mount root fs on unknown-block
« Reply #4 on: December 26, 2007, 07:02:21 AM »
Ah a common problem when compiling a new kernel for a fresh start. Used to happen to me too on Red Hat based distros :)

1. What for is initrd.img?
Initial ramdisk  file is a binary file consists of a small kernel modules that you want to load before switching into your real root partition (ramdisk here as it runs on ur RAM). Red Hat always do this with for their filesystems (biasly referring to ext3 most of the time). So you will need 2 load kernel module (ext3) before VFS can use it mount that partition.

What for is bootspalsh. Can initrd.img be replace with bootsplash somehow?
Bootsplash is a new toy in your linux where when you boot your linux, you dont see those kernel log messages showing hardware detection but a nice splash screen with cool pictures and progress bar.

Bootsplash project tis here. I used to re-compile the kernel to support bootsplash on slackware. :)
--> http://bootsplash.org/Welcome_to_the_graphical_world_of_Linux

Why Command “make dep” answered that this is not necessary?
Depends on which kernel version you compile. And when u run it.
1. I presume u r compiling a kernel 2.6.x

2. If not you have just recompiled and ran once "make dep". So if you do so again without any change to existing binaries, you will get this message.
« Last Edit: December 26, 2007, 07:11:56 AM by dragoncity99 »