Bug 154757

Summary: DVD ISO fails to mount on FC4-test2 installation
Product: [Fedora] Fedora Reporter: Richard Plana <rplana>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED DUPLICATE QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-04-14 21:16:23 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Richard Plana 2005-04-13 23:38:21 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6) Gecko/20050323 Firefox/1.0.2 Fedora/1.0.2-1.3.1

Description of problem:
Using the rescuecd.iso image to boot Anaconda from the CD-ROM. The DVD ISO image is on /dev/hda6 of an 80GB harddisk. After selecting Hard Disk as medium, /dev/hda6 and the proper subdirectory (/fedora/linux/core/test/3.91/i386/iso), something in the installation process triggers what looks like a kernel oops (hard to tell because of the output format as a result of being in ncurses mode).

Snippets of errors I see: "/sbin/loader", "buffer overflow"

I tried booting into Rescue mode and mounting the DVD ISO image:

# mkdir /tmp/hdimage
# mkdir /tmp/loopimage
# mount /dev/hda6 /tmp/hdimage
# mount -t iso9660 -o ro,loop /tmp/hdimage/fedora/linux/core/test/3.91/i386/iso/FC4-test2-i386-DVD.iso /tmp/loopimage

to no avail. Depending on the mount options, I'd either get "File too large." "Could not setup loop device" (using "-o loop") or invalid file descriptor (using "-o loop,ro").

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
(See Description.)

Additional info:
Comment 1 Jeremy Katz 2005-04-14 21:16:23 UTC 

*** This bug has been marked as a duplicate of 154715 ***