Fedora 12 Alpha on VirtualBox 3.0.4 won't boot 'Unable to mount root fs on unknown-block(0,0)'
Hello,
I try to install the Fedora 12 Alpha x86_64 install DVD into VirtualBox 3.0.4. After the Installation of the software, the next screen is the "reboot" now. I'm just wondering, since there was no question about grub configuration. Anyway, after reboot, the system doesn't come up because of this:
VFS: Cannot open root device "mapper/vg_fedora12vb-lv_root" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: 0800 62914560 sda driver: sd 0801 204800 sda1 0802 62705708 sda2 0b00 1048575 sr0 driver: sr Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I have no idea was is going on here, since this is a install on a fresh disk (use entire disk). The only notable thing maybe that I have enabled both repos, Install and Rawhide during the install. I filled a bug [1]. Did anyone else see this? Or did something may know which additional information should be add to the bug report? Thanks for your help!
[1] https://bugzilla.redhat.com/519350
-- Regards, Niels
Niels Haase написа:
I have no idea was is going on here, since this is a install on a fresh disk (use entire disk). The only notable thing maybe that I have enabled both repos, Install and Rawhide during the install. I filled a bug [1]. Did anyone else see this? Or did something may know which additional information should be add to the bug report? Thanks for your help!
When you see the "reboot now" screen in anaconda, can you switch to tty2 and grab some files and attach them to the bug?
- /tmp/anaconda.log - /mnt/sysimage/boot/grub/grub.conf
I personally think that your grub.conf is messed up.
2009/8/26 Alexander Todorov atodorov@redhat.com:
Niels Haase написа:
I have no idea was is going on here, since this is a install on a fresh disk (use entire disk). The only notable thing maybe that I have enabled both repos, Install and Rawhide during the install. I filled a bug [1]. Did anyone else see this? Or did something may know which additional information should be add to the bug report? Thanks for your help!
When you see the "reboot now" screen in anaconda, can you switch to tty2 and grab some files and attach them to the bug?
- /tmp/anaconda.log
- /mnt/sysimage/boot/grub/grub.conf
Thanks for your help Alexander. I've attached both files to the bug report.
-- Regards, Niels
I personally think that your grub.conf is messed up.
-- fedora-test-list mailing list fedora-test-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-test-list
On Wed, Aug 26, 2009 at 11:50:35AM +0200, Niels Haase wrote:
Hello,
VFS: Cannot open root device "mapper/vg_fedora12vb-lv_root" or unknown-block(0,0) Please append a correct "root=" boot option; here are the available partitions: 0800 62914560 sda driver: sd 0801 204800 sda1 0802 62705708 sda2 0b00 1048575 sr0 driver: sr Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
I have no idea was is going on here, since this is a install on a fresh disk (use entire disk). The only notable thing maybe that I have enabled both repos, Install and Rawhide during the install. I filled a bug [1]. Did anyone else see this? Or did something may know which additional information should be add to the bug report? Thanks for your help!
I ran into this as well--not sure of the cause, but you can get a bit further than that by being very quick, and hitting escape as soon as you get past the BIOS screen--this should cause grub to hesitate enough so that you can edit it. Changing the root=UUID=whatever to root=/dev/whatever will get you past that. In my case though, it then dies on unable to open initial console.
Maybe the kernel, like many individuals, thinks the whole UUID thing is just too much of a nuisance and wants to go back to more human usable /dev/sdX. :)
If you look at my posts from the weekend, Sunday, I think, you'll note my mention of the problem.
-
Alexander Todorov -
Niels Haase -
Scott Robbins