I am reinstalling Fedora 12 on a system. I specified a custom partition layout and then I just reselect the partitions and format them, putting the same directories on each. I have done this 4 times on this system, as I develop my install procedure.
Well today after I do the reboot, I get:
Kernel panic - not syncing: VFS: Unalble to mount root fs on unknown-block(0,0)
So before I try yet again (it failed with my ks.cfg, so I did it the long-hand way).
What is the problem and how do I fix it? Will a 'simple' rebuild of the partition table by removing all the partitions then reconfiging them as I want will work, or will this take a bigger hammer?
On 12/03/2010 12:21 PM, Robert Moskowitz wrote:
I am reinstalling Fedora 12 on a system. I specified a custom partition layout and then I just reselect the partitions and format them, putting the same directories on each. I have done this 4 times on this system, as I develop my install procedure.
Well today after I do the reboot, I get:
Kernel panic - not syncing: VFS: Unalble to mount root fs on unknown-block(0,0)
So before I try yet again (it failed with my ks.cfg, so I did it the long-hand way).
What is the problem and how do I fix it? Will a 'simple' rebuild of the partition table by removing all the partitions then reconfiging them as I want will work, or will this take a bigger hammer?
Well I just went through a rebuild again. This time selecting to install on the whole drive, then customizing the layout. I get the same kernel panic on unknown-block(0,0).
On Fri, 2010-12-03 at 13:24 -0500, Robert Moskowitz wrote:
On 12/03/2010 12:21 PM, Robert Moskowitz wrote:
I am reinstalling Fedora 12 on a system. I specified a custom partition layout and then I just reselect the partitions and format them, putting the same directories on each. I have done this 4 times on this system,
--cut --
Well I just went through a rebuild again. This time selecting to install on the whole drive, then customizing the layout. I get the same kernel panic on unknown-block(0,0).
When I get really screwy results I start looking at other possibilities, such as bad drive or bad memory. Since the problem repeats itself exactly, I'd say it's not an intermittent, as a power supply would be.
William Stock wrote:
On Fri, 2010-12-03 at 13:24 -0500, Robert Moskowitz wrote:
On 12/03/2010 12:21 PM, Robert Moskowitz wrote:
I am reinstalling Fedora 12 on a system. I specified a custom partition layout and then I just reselect the partitions and format them, putting the same directories on each. I have done this 4 times on this system,
--cut --
Well I just went through a rebuild again. This time selecting to install on the whole drive, then customizing the layout. I get the same kernel panic on unknown-block(0,0).
When I get really screwy results I start looking at other possibilities, such as bad drive or bad memory. Since the problem repeats itself exactly, I'd say it's not an intermittent, as a power supply would be.
Just a reminder......Fedora 12 went eol yesterday so you may want to install F14 as F12 is no longer supported
On 12/03/2010 01:48 PM, William Stock wrote:
On Fri, 2010-12-03 at 13:24 -0500, Robert Moskowitz wrote:
On 12/03/2010 12:21 PM, Robert Moskowitz wrote:
I am reinstalling Fedora 12 on a system. I specified a custom partition layout and then I just reselect the partitions and format them, putting the same directories on each. I have done this 4 times on this system,
--cut --
Well I just went through a rebuild again. This time selecting to install on the whole drive, then customizing the layout. I get the same kernel panic on unknown-block(0,0).
When I get really screwy results I start looking at other possibilities, such as bad drive or bad memory. Since the problem repeats itself exactly, I'd say it's not an intermittent, as a power supply would be.
The system passed the memory test on the F14 install CD. I was able to mount the drive from the F12 rescue mode. I don't know what tests to perform on the disk to check on block(0,0). Probably to boot sector got zapped? There is NO windows cruft on this system; it did come to me with XP on it, but I only booted that once to check out that the system worked before installing Fedora 12 the first time.
I am having trouble with the DVD/CDrom as it does not open in a vertical position (as it will be in my rack), but I can't see how the drive not opening easily would cause a kernel panic.
So how should I test the drive, and if it is the boot sector I need to rewrite, how do I do that?
And I know that F12 is eol. Amahi on F14 is still in development, so I will be running F12 for a few more months.
On Sat, 04 Dec 2010 20:46:12 -0500 Robert Moskowitz rgm@htt-consult.com wrote:
Well I just went through a rebuild again. This time selecting to install on the whole drive, then customizing the layout. I get the same kernel panic on unknown-block(0,0).
[snip]
So how should I test the drive, and if it is the boot sector I need to rewrite, how do I do that?
And I know that F12 is eol. Amahi on F14 is still in development, so I will be running F12 for a few more months.
I found a reference to this problem here: http://www.linuxquestions.org/questions/fedora-35/fc2%3B-vfs-cannot-open-roo... that described how they had solved the problem, and said they found the solution here: https://bugzilla.redhat.com/show_bug.cgi?id=126953 Maybe it will point you in the right direction. From their description it sound like you have to run mkinitrd (on F12 that will work, it seems to be gone from F14 so you probably have to run dracut somehow on F14).
On Friday, December 03, 2010 12:21:58 pm Robert Moskowitz wrote:
Kernel panic - not syncing: VFS: Unalble to mount root fs on unknown-block(0,0)
....
What is the problem and how do I fix it? Will a 'simple' rebuild of the partition table by removing all the partitions then reconfiging them as I want will work, or will this take a bigger hammer?
Is there a valid initrd with the right modules for your hardware in /boot?
Reboot, edit the command line, and add 'rdshell' to the kernel line. This will drop you into a dracut shell from the initramfs, assuming it exists. You can then see what's going on in terms of the init ramdisk.
If this doesn't give you a dracut shell, then my guess is that your ks.cfg or something else didn't make an initrd using dracut.
A saw this exact error after a failed preupgrade from F13; the failure was caused by a corrupted moodle, which didn't error until preupgrade had already installed 90% of the packages, but hadn't done any cleanup. The F13 kernels were still there, but the F14 kernel didn't get an initramfs built, and gave the same error you list above. A yum reinstall of the kernel fixed it, and then I had fun getting rid of the duplicate packages.... but we're good now.
-
Lamar Owen -
Michael Miles -
Robert Moskowitz -
stan -
William Stock