Bug 47756 - Error Mounting Image During HTTP Install
Summary: Error Mounting Image During HTTP Install
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2001-07-06 19:10 UTC by Thornton Prime
Modified: 2007-04-18 16:34 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2001-07-10 15:29:32 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Thornton Prime 2001-07-06 19:10:37 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux 2.4.2-2 i686; en-US; rv:0.9.1)

Description of problem:
Could not mount image during HTTP install. No ability to go back. No
message to debug with.

How reproducible:
Couldn't Reproduce

Steps to Reproduce:
1. During HTTP install, download runtime image.
2. Image download corrupt or incomplete? No idea.

Actual Results:  
Error mounting /dev/loop0 on
/mnt/runtime (Invalid argument)
This shouldn't happen, and I'm
rebooting your system now.

Expected Results:  I'm not sure what caused this. There was not enough
information to figure out if it was a bad image download or what.

It would be great to be able to go back, retry or even re-select a
different install method.

At the very least we can hopefully get some error message indcating what is

Maybe an MD5 check of the image after the download will help?

Additional info:

Comment 1 Michael Fulbright 2001-07-09 14:50:33 UTC
Did it work when you retried?

Comment 2 Thornton Prime 2001-07-09 14:54:26 UTC
Yes, but it required a reboot.

It may be more of a RFE but it would be nice to go back to retry the download
(or even select a new download method rather than getting to a dead end and
having to start over.

Comment 3 Jeremy Katz 2001-07-16 15:25:37 UTC
Unfortunately, once we get to that point, going back and retrying is hard (we'd
have to do more magic with the ramdisk as far as reinitializing is concerned and

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