VFS: Cannot open root device "LABEL=/" or 00:00 Pleas append a correct "root=" boot option Kernal panic: VFS :Unable to mount root fs on 00:00 I have try exchange LABEL=/ to If it is another digit (like 8), it is unable to identify the file system (but is able to access the hardware). For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. Pleas append a correct "root=" boot option Kernal panic: VFS :Unable to mount root fs on 00:00 03-02-2005 #7 sgzlit View Profile View Forum Posts Private Message View Articles Just Joined!
Vfs Cannot Open Root Device Or Unknown-block(0 0)
The time now is 01:33 AM. Calculating ...5(5+4(4+3(3+2(2+1(1))))) What is a satisfactory result of penetration testing assessment? Straight line equation Can you dispel a magic effect you can't perceive? Home Forum Today's Posts | FAQ | Calendar | Community Groups | Forum Actions Mark Forums Read | Quick Links View Site Leaders | Unanswered Posts | Forum Rules Articles Marketplace
Find a mistake in the following bogus proof GO OUT AND VOTE My cat sat on my laptop, now the right side of my keyboard types the wrong characters Basic Geometric Join Date Mar 2004 Location Sweden Posts 5 Kernal panic: VFS : Unable to mount root fs on 00:00 Hi I am new on linux and having proble. Check if the kernel parameter for root= is pointing to the correct partition. Vfs Cannot Open Root Device Redhat RAMDISK: Compressed image found at block 0 Freeing initrd memory: 162k freed VFS: Mounted root (ext2 filesystem).
Either your root filesystem is not labelled correctly or not labelled at all. Please Append A Correct Root= Boot Option if it is on /dev/hda2 for instance, try running e2label /dev/hda2 what does that show you? root (hd0,5) kernel (hd0,5)/boot/vmlinuz root=/dev/hda6 vga=788 initrd (hd0,5)/boot/initrd what`s the reason? Please login or register.Did you miss your activation email? 1 Hour 1 Day 1 Week 1 Month Forever November 11, 2016, 01:33:38 AM News : LinuxSolved.com Linux Help Community Forum..
if it returns nothing it means that there isn;t a filesystem label associated with that parition. Please Append A Correct Root= Boot Option Here Are The Available Partitions Please visit this page to clear all LQ-related cookies. The other two files are the same: -rw-r--r-- 1 root root 1236945 Oct 3 2003 vmlinuz-2.4.21-4.EL -rw-r--r-- 1 root root 1252573 Apr 15 21:34 vmlinuz-2.4.21-32.EL Any ideas? To set a filesystem label run e2label /dev/hda2 / Alternatively in grub.conf set root= part to your partition containing your root filesystem instead of using a label.
Please Append A Correct Root= Boot Option
Why is the 'You talking to me' speech from the movie 'Taxi Driver' so famous? Generally speaking one can say that, if the first digit is 0, then the kernel is unable to identify the hardware. Vfs Cannot Open Root Device Or Unknown-block(0 0) share|improve this answer answered Feb 27 '12 at 4:51 Nitin Venkatesh 12.6k84979 1 Hi, it passed a lot of time, but thanks. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option Success!
more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed check over here Try switching hda with sda (and hdb with sdb, and ...). Google™ Search FedoraForum Search Red Hat Bugzilla Search Search Forums Show Threads Show Posts Tag Search Advanced Search Go to Page... Check if the kernel that is being boot by the boot loader is the correct kernel. Vfs Cannot Open Root Device Centos
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org?
Please click the link in the confirmation email to activate your subscription.
Also I am sure the root partion is correct,but the KERNEL PINC was occured .
With Promising RAID 0 Mirror Volume .
Registration is quick, simple and absolutely free.
Try running the following lscpi command, and paste its output on http://kmuto.jp/debian/hcl/.
Several reasons can result in such a failure: the kernel configuration is missing drivers for your HDD controller (cases 1, 4, 5) the kernel configuration is missing drivers for the bus
FedoraForum.org is privately owned and is not directly sponsored by the Fedora Project or Red Hat, Inc.
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.
Red Hat nash version 3.5.14 starting Loading jbd.o module Journalled Block Device driver loaded Loading ext3.o module Mounting /proc filesystem Creating block devices VFS: Cannot open root device "LABEL=/" or 00:00 Search this Thread 05-04-2006, 05:17 AM #1 venkatesh111 Member Registered: Mar 2006 Posts: 34 Rep: VFS: cannot open root device "LABEL=\" or 00:00 hi i have recompiled my kernel But now I try whith 2.4.25 and then I get a problem when I try to boot with that kernal in my grub.conf: default=0 timeout=10 splashimage=(hd0,0)/grub/splash.xpm.gz title Red Hat Linux (2.4.20- his comment is here up vote 0 down vote After reading this answer which explains what is going on, try using the [Boot-Reapir CD]: https://help.ubuntu.com/community/Boot-Repair Worked great at repairing the "the device is misidentified in
Join Date Apr 2004 Location India Posts 1 Kernal panic: VFS : Unable to mount root fs on 08:30 Hi I have installed fresh Fedora on Intel Server board 875wp1-E .
This means that # all kernel and initrd paths are relative to /, eg. # root (hd0,3) # kernel /boot/vmlinuz-version ro root=/dev/hda4 # initrd /boot/initrd-version.img #boot=/dev/hda default=2 timeout=500500500500500 splashimage=(hd0,3)/boot/grub/splash.xpm.gz title Fedora VFS: Cannot open root device "LABEL=/" or 00:00 Pleas append a correct "root=" boot option Kernal panic: VFS :Unable to mount root fs on 00:00 Try change "LABEL=/" to "/dev/hda0" (note Latest LQ Deal: Linux Power User Bundle Blogs Recent Entries Best Entries Best Blogs Blog List Search Blogs Home Forums HCL Reviews Tutorials Articles Register Search Search Forums Advanced Search Search Vfs Cannot Open Root Device Mapper using /dev/sda2 and compile with SCSI buslogic 04-01-2004 #6 nitin virmani View Profile View Forum Posts Private Message View Articles Just Joined!
It's giving the following error. Make sure the file system support is built in the kernel. notageek View Public Profile Find all posts by notageek Tags 0000, device, kernal, label, open, panic, root, vfs « Previous Thread | Next Thread » Thread Tools Show Printable Version Display As a result, they copy the kernel to the root file system (/) whereas the boot loader still expects the kernel image to be on the /boot partition.
The site will show you which kernel drivers you need to select for your system.