Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 335131 - Can't run network installation with the rescue cd
Can't run network installation with the rescue cd
Status: CLOSED DUPLICATE of bug 330641
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
All Linux
low Severity low
: ---
: ---
Assigned To: Anaconda Maintenance Team
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-10-16 15:24 EDT by Jean-Philippe Dionne
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-10-22 16:10:31 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jean-Philippe Dionne 2007-10-16 15:24:29 EDT
Description of problem:

On a system with only cdrom as boot method, the Fedora-7.92-x86_64-rescuecd.iso,
 does not allow to launch a network install through http.

From the main interface the error message is: "Unable to retrive the install
image".   Thought the image is accessible and the logs in the third vty informs
the file transfer of images/stage2.img is proceeding.

10:30:00 INFO: transferring
to a fd
10:30:02 INFO: mntloop loop0 on /mnt/runtime as /tmp/ramfs/stage2.img fd is 16
10:30:02 ERROR: LOOP_SET_FD failed: Device or ressource busy
10:30:02 ERROR: Error mounting /dev/loop0 on /mnt/runtime (Device or ressource busy)

How reproducible: Always

Steps to Reproduce:
1. Boot with the rescue cd
2. In grub, select the install option
3. Setup an http network install
Actual results: Can't install the system

I have proceeded with the same steps but with a cdrom from boot.iso and the
installation succeeded.
Comment 1 Jeremy Katz 2007-10-22 16:10:31 EDT

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

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