Red Hat Bugzilla – Bug 494086
hard disk install non functional in fedora 11 beta
Last modified: 2009-04-04 14:11:43 EDT
Description of problem:
This grub entry points to the files I extracted from the DVD iso image:
title Install Fedora 11 Beta
kernel /boot/fed11/vmlinuz repo=hd:/dev/sdb2:/downloads/otherinbox/Fedora-11-Beta-x86_64-DVD
I had to unplug my USB drive to make this work since for some reason in the
kernel for the installer, the usb drive came up as /dev/sdb and the hard disk
which is normally /dev/sdb came up as /dev/sdc. With the usb drive unplugged
things get farther (but that is really just a side issue however weird it
The Fedora-11-Beta-x86_64-DVD directory referenced above looks like this:
-rw-r--r-- 1 tom users 1658 Apr 3 17:04 Fedora-11-Beta-x86_64-CHECKSUM
-rw-r--r-- 1 tom users 4356126720 Apr 3 20:37 Fedora-11-Beta-x86_64-DVD.iso
drwxr-xr-x 2 root root 4096 Apr 3 23:00 images
-rw-r--r-- 1 root root 105361408 Apr 3 23:00 install.img
The images/install.img file is copied from the images directory on the
I boot this grub entry, the kernel boots, it asks about the keyboard, I
get to the anaconda initial GUI and click on the Install Anyway button
when it asks about installing beta software, then the next thing
that comes up is an error dialog that says:
"The installation source given by /dev/sdb2 could not be found."
I try again with LABEL=ZOOTY instead of /dev/sdb2, but the same thing
It clearly claimed to be running anaconda and some GUI bits showed up,
so I assume it found something to start running, but then I guess it
lost track of it :-).
If the HD install procedurs have radically changed once again, I
couldn't find any pointers to the new procedures to use.
Version-Release number of selected component (if applicable):
Fedora 11 beta DVD image.
Steps to Reproduce:
1. see above
actually getting the install going would be nice
This is a known issue already documented in the F11 beta release notes.
There is a bug 491781 already opened for this. Hence I am closing this out an duplicate.
Fedora Bugzappers volunteer triage team
*** This bug has been marked as a duplicate of bug 491781 ***