Hi, I read your comments on the failed harddisk installation.In my case after the Device/Resource busy screen I was dropped in the repo screen aswell. But anaconda could not make a network connection, so the complete installation failed.
I noticed, that in the repo screen there is no "Harddisk" option. Should there be no "Harddisk" option?
As I saw your anaconda-ks.cfg file, you installed in a IPv4 environment. I installed in a IPv6 environment. I have seen in earlier situations, that anaconda fails when it can not detect an IPv4 although there is an IPv6 network. These observations lead me to the conclusion that anaconda indeed tries to find packages on a HTTP repo after the connection to the harddisk repo fails. In your situation it found one, in mine it did not.
If you do a harddisk installation without a network cable connected, does it succeed?
Koos. Michael Schwendt schreef:
On Tue, 21 Sep 2010 10:30:12 +0100, Adam wrote:I install on /dev/sda. When I install, I get an error "(16, Device or resource busy)".Before I file a bug against F14, can someone acknowledge that my installation setup is correct?This sounds like a case of: https://bugzilla.redhat.com/show_bug.cgi?id=627789 Brian notes in that report - "Hit ok and a blank repe edit dialog is shown. Hit cancel and it then finds the correct repositories and proceeds with the install." so you could try that.That is how I ended up with a broken "transparent" http install from a stale mirror, getting the old non-working firstboot package. The "Installation Repo" will be missing due to the error and clicking Cancel.
Attachment:
smime.p7s
Description: S/MIME Cryptographic Signature
-- test mailing list test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
