Red Hat Bugzilla – Bug 199343
Anaconda [Errno 256] while attempting hard disk install ISO on IDE HD
Last modified: 2008-08-02 19:40:33 EDT
Description of problem:
FC5 Hard disk install failed with Errno 256, "no mirror" available from a custom
built FC5 distro re-roll.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Headless blade P3 with 40 GB IDE HD
2. Script successfully partitions & formats hdc as ext3
3. Move ISO to partitioned HD on extended partition hdc5
4. Begin installation with serial console & selinux=0 on kernel line
5. Fails BEFORE tty2 is enabled so limited logging available
6. Failed with repodata/repomd.xml [Errno 256]
Unable to read package meta data. This may be due to a missing rpodata
directory. Please ensure that your install tree has been correctly generated.
failure: repodata/repoxmd.xml from anaconda: [Errno 256] No more mirrors to try.
Expected it to find the ISO images on the Hard Disk in directory listed in log.
Successful installation of custom distro using ISO on VMware virtual machine
Also successful installation on other hardware (laptops) using CD.
Fails on blade computer BEFORE tty2 is enabled so attached anaconda.log & syslog
are captured by adding "rescue" to kernel line.
Able to loop mount ISO on hdc5 and check sha2sum files & permissions in
repodata/repomd.xml directory okay
Created attachment 132631 [details]
Created attachment 132632 [details]
This means you haven't correctly created -- see
Created attachment 132851 [details]
Directory tree of ISO image
Thanks Jeremy. I've carefully walked my scripting and used another posting's
scripting which also uses Mr. Nasrat's Anaconda Customization outline, but both
return the same error.
I've attached a slightly snipped directory tree of my current ISO image mounted
with loop to illustrate the location of repodata/repomd.xml.
I'm curious as to why the CD installation would work fine, but not on HD...
Have you tried this lately? I know there were various problems with hard drive
ISO install methods that could generate this sort of error message. I've fixed
a variety of them over the past release or two, but there may still be more. If
you could update this bug with the current status, I can take a look deeper into
it if things are still broken. Thanks.