Kernel panic-not syncing unable to mount the root file system on unknown block(0,0)
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Kernel panic-not syncing unable to mount the root file system on unknown block(0,0)
Hello,
Can any one please help me for this error.
Kernel Panic!!! -Not Syncing VFS:Unable to mount root FS on unknown - block
(0,0)
Please find the grub.conf. I am using RHEL-4. I rebuild the 2.6.9 kernel .I have applied KDB patch. Patch was applied succesfully and kernel compilation also well. But if I boot my machine with this kernel I am getting above error. Below are my details
[root@localhost linux-2.6.9-kdb]# fdisk -l
Disk /dev/sda: 40.0 GB, 40000000000 bytes
255 heads, 63 sectors/track, 4863 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 1 4 32098+ de Dell Utility
/dev/sda2 * 5 1309 10482412+ 7 HPFS/NTFS
/dev/sda3 1310 4862 28539472+ f W95 Ext'd (LBA)
/dev/sda5 1310 3982 21470841 7 HPFS/NTFS
/dev/sda6 3983 4862 7068568+ 7 HPFS/NTFS
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 2 10200 81923467+ f W95 Ext'd (LBA)
/dev/sdb2 * 10201 10213 104422+ 83 Linux
/dev/sdb3 10214 10474 2096482+ 82 Linux swap
/dev/sdb4 10475 19457 72155947+ 83 Linux
/dev/sdb5 2 10200 81923436 7 HPFS/NTFS
#cat /boot/grub/grub.conf
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd1,1)
# kernel /vmlinuz-version ro root=/dev/sdb4
# initrd /initrd-version.img
#boot=/dev/sda
default=3
timeout=5
splashimage=(hd1,1)/grub/splash.xpm.gz
hiddenmenu
title Red Hat Enterprise Linux WS (2.6.9)
root (hd1,4)
kernel /vmlinuz-latest new ro root=LABEL=/dev/sdb4 rhgb quiet
initrd /initrd-2.6.9.img
title Red Hat Enterprise Linux WS (2.6.9-5.ELsmp)
root (hd1,1)
kernel /vmlinuz-2.6.9-5.ELsmp ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-5.ELsmp.img
title Red Hat Enterprise Linux WS-up (2.6.9-5.EL)
root (hd1,1)
kernel /vmlinuz-2.6.9-5.EL ro root=LABEL=/ rhgb quiet
initrd /initrd-2.6.9-5.EL.img
title Windows
rootnoverify (hd0,1)
chainloader +1
I have copied bzImage and System.map into boot.
[root@localhost linux-2.6.9-kdb]# ll /boot/
total 23604
-rw-r--r-- 1 root root 48177 Jan 6 2005 config-2.6.9-5.EL
-rw-r--r-- 1 root root 47672 Jan 6 2005 config-2.6.9-5.ELsmp
drwxr-xr-x 2 root root 1024 Aug 13 14:31 grub
-rw-r--r-- 1 root root 489233 Aug 7 17:07 initrd-2.6.9-5.EL.img
-rw-r--r-- 1 root root 480812 Aug 7 17:07 initrd-2.6.9-5.ELsmp.img
-rw-r--r-- 1 root root 305107 Aug 9 11:43 initrd-2.6.9.img
-rw-r--r-- 1 root root 305113 Aug 8 16:04 initrd-2.6.9.img-kdb
drwx------ 2 root root 12288 Aug 7 22:33 lost+found
-rw-r--r-- 1 root root 23108 Dec 3 2004 message
-rw-r--r-- 1 root root 21282 Dec 3 2004 message.ja
lrwxrwxrwx 1 root root 16 Aug 9 11:43 System.map -> System.map-2.6.9
-rw-r--r-- 1 root root 987854 Aug 9 11:43 System.map-2.6.9
-rw-r--r-- 1 root root 712698 Jan 6 2005 System.map-2.6.9-5.EL
-rw-r--r-- 1 root root 741143 Jan 6 2005 System.map-2.6.9-5.ELsmp
-rw-r--r-- 1 root root 987854 Aug 13 11:53 System.map-latest
lrwxrwxrwx 1 root root 13 Aug 9 11:43 vmlinuz -> vmlinuz-2.6.9
-rw-r--r-- 1 root root 2007136 Aug 9 11:43 vmlinuz-2.6.9
-rw-r--r-- 1 root root 1433988 Jan 6 2005 vmlinuz-2.6.9-5.EL
-rw-r--r-- 1 root root 1400620 Jan 6 2005 vmlinuz-2.6.9-5.ELsmp
-rw-r--r-- 1 root root 2007136 Aug 13 11:53 vmlinuz-latest
FYI :
[root@localhost linux-2.6.9-kdb]# mkinitrd --preload=scsi_mod --preload=sd_mod --with=ata_piix \/boot/initrd-2.6.9.img-sata 2.6.9
No module ata_piix found for kernel 2.6.9, aborting.
I dont know whether SATA disk requres ata_piix or not.
I am not up on Redhat's "LABEL" system, but here is what I can see:
You have root(hd1,4) for one of your kernels, and root(hd1,1) for the others. If your kernels are all in the same /boot directory, then one of these is wrong. It looks like hdb2 is where /boot is, so they should all be root (hd1,1)
Similarly, you have root=LABEL=/ in some kernel lines, and root=LABEL=/dev/sdb4 for another.
>>>root=LABEL=/ in some kernel lines, and root=LABEL=/dev/sdb4 for another
Previously it was root=LABEL=/ only . I made it into root=LABEL=/dev/sdb4
Thanks!
Quote:
Originally Posted by pixellany
I am not up on Redhat's "LABEL" system, but here is what I can see:
You have root(hd1,4) for one of your kernels, and root(hd1,1) for the others. If your kernels are all in the same /boot directory, then one of these is wrong. It looks like hdb2 is where /boot is, so they should all be root (hd1,1)
Similarly, you have root=LABEL=/ in some kernel lines, and root=LABEL=/dev/sdb4 for another.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.