The file system I was using was the new reiser4. Are you new to LinuxQuestions.org? I researched and tried every suggestion to fix the problem. Second part, initrd Another possibility is that your system cannot open a root device because it does not have the proper drivers to do so. navigate here
I notice that after the computer probes for IDE interfaces it brings up hda and it doesn't know what fs it is. Please visit this page to clear all LQ-related cookies. I tansfered my old linux system with dd to the new computer via the portable drive. Then one day I compiled a new kernel and got the UDF-fs: No partition found error.
Vfs Cannot Open Root Device Or Unknown-block(0 0)
RAMDISK: Compressed image found at block 0 Freeing initrd memory: 162k freed VFS: Mounted root (ext2 filesystem). The problem will usually manifest after kernel upgrades. So that is as it should be. (Btw setting this to hd1,5 will cause the system to hang much earlier with a different error message, as I have no kernel images
How about donating some dinero to Dedoimedo?
Ionexchange View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Ionexchange 12-24-2005, 07:52 AM #11 InspectorClusea LQ Newbie Registered: Mar 2004 Distribution:
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.
The kernel image is relative to this path.
You must make sure you do not override essential parts necessary for proper functioning of the system.
Ask questions about Fedora that do not belong in any other forum.
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
Though I could not resize the root partiton for some reason. It reads: Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0). You most likely don't, so here's a quick check-up. Vfs Cannot Open Root Device Redhat Whatever strings are passed to the Kdump kernel are bad and interfere with the loading.
So there appears to be a problem in the way the FC2 installer constructs the initrd that it installs on some systems. Please Append A Correct Root= Boot Option Not the answer you're looking for? Background I got a new PC. To fix this, I ran the following: mkinitrd --preload=scsi_mod --preload=sd_mod --with=ata_piix \ /boot/initrd.img-2.6.5-sata 2.6.5-1.358 and then I modified my grub parameters in two ways: - I changed the initrd line to
Hot Network Questions Single word for the act of being susceptible? Please Append A Correct Root= Boot Option Here Are The Available Partitions grub.conf is on a secondary master, though this hasn't been a problem in the past. kudzu could prolly fix it for me, but it's waiting for a keyboard press to activate Anyway, I'll com back and open an other thread, should I not be able to up vote 7 down vote favorite 3 whenever I try to boot with linux kernel 126.96.36.199 (the one installed by the upgrades) I get a Kernel Panic error: VFS: Cannot open
Generally speaking one can say that, if the first digit is 0, then the kernel is unable to identify the hardware. check over here So fara so good. The partitions were also resized to take advantage of the increased disc-space. Distribution: Fedora 7 Posts: 65 Original Poster Rep: Thanx, but I actually tried that, out of desperation and tiredness. Vfs Cannot Open Root Device Centos
Check if the kernel parameter for root= is pointing to the correct partition. 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 Thread Tools Search this Thread Display Modes #1 17th March 2009, 11:16 AM shibujohn Offline Registered User Join Date: Mar 2009 Posts: 1 Kernal panic VFS cannot open his comment is here Solution is here: https://bugzilla.redhat.com/bugzilla....cgi?id=126953 Quote: Additional Comment #1 From C.Laurence Gonsalves on 2004-06-30 14:50 ------- It looks like the problem was due to the initrd being incomplete.
Departing from airport before visa is valid, but arriving when it is Teenage daughter refusing to go to school Polyglot Anagrams Robbers' Thread Is calling a function with local side-effects twice Cannot Open Root Device Mapper/volgroup-lv_root 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 the primary boot device is on the second channel and currently I'm booting on the second drive of the 2nd channel.
It seems that when you compile a new kernel, the reiser file system will not access the hard drive without some manipulation with the reiserfs tools.
This is the kernal boot options in my pc. Join our community today! grub.conf: Code: # 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. Vfs Cannot Open Root Device Mapper My new PC has 2 250Gb SATA drives + 1 160Gb portable PATA hd.
Since the new kernel is more up to date, I would much rather try to get the other on working. I have seen people who, after building a first kernel (which doesn't boot), forget that they have to mount /boot before the overwrite the kernel with a new one. If you'd like to contribute content, let us know. Though it has always said that, iirc.
If it does, it might help you identify if you misselected a partition (in the example given at the beginning of this section, only two partitions are found whereas the kernel Starchild View Public Profile View LQ Blog View Review Entries View HCL Entries Find More Posts by Starchild 12-22-2004, 04:22 PM #2 masand LQ Guru Registered: May 2003 Location: What do you do now? The "older" kernel , 2.4.21-4.EL, is running just fine.
GO OUT AND VOTE As a monk, can I use Deflect Missiles to protect my ally? The problem here is that the kernel that you are booting cannot translate the root=/dev/... The kernel images are found and loaded fine, until we need the stuff on root. Join Us!
weird ... –Dan Soap Nov 28 '11 at 16:19 add a comment| 2 Answers 2 active oldest votes up vote 8 down vote accepted You haven't provided much information with logs Using the eval command twice How good should one be to participate in PS? For example, if you plan on using LVM, it seems quite necessary to add the lvm module. Read more Donate to Dedoimedo!
Open the kernel configuration wizard (the make menuconfig part) so that you can update the kernel configuration accordingly. Registration is quick, simple and absolutely free. 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