Bug 431132 - hdiso installs fail due to "missing repodata" - isos not mounted
Summary: hdiso installs fail due to "missing repodata" - isos not mounted
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Chris Lumens
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 433269 (view as bug list)
Depends On:
Blocks: F9Blocker
TreeView+ depends on / blocked
 
Reported: 2008-01-31 21:50 UTC by Will Woods
Modified: 2008-02-25 20:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-02-12 21:16:03 UTC


Attachments (Terms of Use)
anaconda-hdiso.log (20.10 KB, text/plain)
2008-01-31 21:50 UTC, Will Woods
no flags Details

Description Will Woods 2008-01-31 21:50:09 UTC
I attempted a hdiso install of Fedora 9 Alpha for i386. Booted the machine from
the Rescue image. The CD isos were on a (vfat-formatted) USB drive. 

Told loader to fetch images from sdb1, in the directory 9-Alpha/Fedora/i386/iso
and it happily loaded stage2 and continued into the GUI. anaconda.log has the
following message:

19:49:11 INFO    : Found hd stage2, copying /tmp/loopimage///images/stage2.img
in RAM as stage2

So the installer *did* find sdb1 and mounted disc1 just fine.

I did the normal steps - choose timezone, partition drive, etc. When it tried to
get repo metadata, the installer popped up a message like:

"Unable to read package metadata. ... Cannot retrieve repository metadata
(repomd.xml) for repository: anaconda-FedoraBase-$(datestamp).i386. Please
verify its path and try again. [Abort]"

Checked tty2 - /dev/sdb1 was not mounted, and neither were any of the ISO images.

I'm attaching the anaconda.log from that system.

Comment 1 Will Woods 2008-01-31 21:50:09 UTC
Created attachment 293654 [details]
anaconda-hdiso.log

Comment 2 Chris Lumens 2008-02-25 20:45:59 UTC
*** Bug 433269 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.