The main difference I observe is that up to 184.108.40.206, the grub conf tries to identify the hard disk using its UUID, 220.127.116.11 now uses /dev/sda6 .. Find More Posts by sundialsvcs Thread Tools Show Printable Version Email this Page Search this Thread Advanced Search Posting Rules You may not post new threads You may not post Subscribed! 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. weblink
This is not because kernels are inconsistent with each other, but because of the drivers used: older drivers use the hda syntax, newer sda. up vote 7 down vote favorite 3 whenever I try to boot with linux kernel 18.104.22.168 (the one installed by the upgrades) I get a Kernel Panic error: VFS: Cannot open Open the kernel configuration wizard (the make menuconfig part) so that you can update the kernel configuration accordingly. Page 1 of 2 1 2 Last Jump to page: Results 1 to 10 of 11 Thread: Kernal panic: VFS : Unable to mount root fs on 00:00 Thread Tools Show
Register All Albums FAQ Today's Posts Search Using Fedora General support for current versions. Make sure the file system support is built in the kernel. parameter you gave it (inside the boot loader configuration) into a real, accessible file system.
Since the new kernel is more up to date, I would much rather try to get the other on working. Join our community today! Regards Scienitca (registered user #335819 - http://counter.li.org ) -- A master is nothing more than a student who knows something of which he can teach to other students. 03-18-2004 #3 nikhil Vfs Cannot Open Root Device Redhat I have successfuly got kernal 2.4.20-8 to run.
Success! Please Append A Correct Root= Boot Option 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 What do I do? 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
Where should I append the correct root= option? Please Append A Correct Root= Boot Option Here Are The Available Partitions Not the answer you're looking for? Join Date Feb 2005 Location China Posts 7 I just meet the same issue! Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the
If it doesn't, it is most likely because the kernel doesn't know the device to begin with (so it can't attempt to display partitions). 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 Vfs Cannot Open Root Device Or Unknown-block(0 0) Notices Welcome to LinuxQuestions.org, a friendly and active Linux Community. Vfs Cannot Open Root Device Please Append A Correct Root Boot Option Join Date Feb 2005 Posts 9 How do I get the name for the drive/partition where I'm running Linux? 09-24-2007 #10 ipodlinuxnoob View Profile View Forum Posts Private Message View Articles
How can I open the next/previous file alphabetically? http://bovbjerg.net/cannot-open/vfs-cannot-open-root-device-nfs.php Logged gauravbajaj LST CareTaker Experienced Posts: 658 VFS:cannot open root device "LABEL=/" or 00:00 « Reply #1 on: June 15, 2005, 08:36:35 AM » ok its possible that ur boot directory root (hd0,5) kernel (hd0,5)/boot/vmlinuz root=/dev/hda6 vga=788 initrd (hd0,5)/boot/initrd what`s the reason? Start a coup online without the government intervening Is calling a function with local side-effects twice in the same expression undefined behavior? Vfs Cannot Open Root Device Centos
shibujohn View Public Profile Find all posts by shibujohn #2 18th March 2009, 03:57 PM notageek Offline Registered User Join Date: Jan 2008 Location: N/A Posts: 2,148 All 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 Kmod: failed to exec/sbin/mod probe -S -K ide omitting the many-dozens of others that are typically included with a "distro." (If and when the hardware changes, presumably I'll know that I did it and will have prepared ahead of http://bovbjerg.net/cannot-open/vfs-cannot-open-root-device-label-or-unknown-block0-0.php 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
share|improve this answer answered Sep 30 '13 at 12:25 madcap66 1 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign Cannot Open Root Device Mapper/volgroup-lv_root Join Date Mar 2004 Location Sweden Posts 5 How do I get the name for the drive/partion when running Linux in VMwere ie I am running linux on a virtuall disk 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..
Fixing Unix is better than working with Windows. Click Here to receive this Complete Guide absolutely free. Having a problem logging in? Vfs Cannot Open Root Device Mapper Password Forgot Password?
Doing a quick Google search led me to link 1, link 2, link 3 Following is the excerpt from a link referred to by one of the links above: Most likely Not a member yet? Generally speaking one can say that, if the first digit is 0, then the kernel is unable to identify the hardware. this content This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant.
Home Search Login Register Linux Forums - Linux Help,Advice & support community:LinuxSolved.com » Linux in General » Linux Kernel » VFS:cannot open root device "LABEL=/" or 00:00 « previous next » RAMDISK: Compressed image found at block 0 Freeing initrd memory: 162k freed VFS: Mounted root (ext2 filesystem). This isn't as stupid as it sounds. The problem here is that the kernel that you are booting cannot translate the root=/dev/...
Main Menu LQ Calendar LQ Rules LQ Sitemap Site FAQ View New Posts View Latest Posts Zero Reply Threads LQ Wiki Most Wanted Jeremy's Blog Report LQ Bug Syndicate Latest Ask questions about Fedora that do not belong in any other forum. paralizer Using Fedora 5 2nd March 2007 08:12 AM Cannot open root device "LABEL=/" or 00:00 on 2.4.26 kernel savudin Using Fedora 4 8th June 2004 01:39 AM Current GMT-time: 01:33 Now the fedora is not booting properly.
I had a faulty CD-Rom, removing that everything worked fine! –lucacerone Mar 13 '12 at 17:36 add a comment| Did you find this question interesting? Most likely this is PCI support, SATA support (which is beneath SCSI device support), ... if it returns nothing it means that there isn;t a filesystem label associated with that parition. Straight line equation Can you dispel a magic effect you can't perceive?
With Promising RAID 0 Mirror Volume . 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 Incapsula incident ID: 544000050008222197-67979428136747098 UbuntuCommunityAsk!DeveloperDesignDiscourseHardwareInsightsJujuShopMore ›AppsHelpForumLaunchpadMAASCanonical current community chat Ask Ubuntu Ask Ubuntu Meta your communities Sign up or log in to customize your list.
I prefer to put all of the device-drivers required by my hardware directly into the kernel... LinuxQuestions.org > Forums > Linux Forums > Linux - Software > Linux - Kernel VFS: cannot open root device "LABEL=\" or 00:00 User Name Remember Me? asked 5 years ago viewed 35978 times active 3 years ago Linked 3 Kernel panic in version 3.0.0-13 prevents login (“VFS not syncing” error) Related 1Kernel panic: unable to mount root