Bug 151203 - Hard drive installation doesn't work
Summary: Hard drive installation doesn't work
Keywords:
Status: CLOSED DUPLICATE of bug 150887
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 4
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-15 23:59 UTC by Miloslav Trmač
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:08:18 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Miloslav Trmač 2005-03-15 23:59:50 UTC
Description of problem:
SSIA; after selecting the drive (/dev/hda1) and typing the correct path
(/home/mitr/iso), anaconda tells me there are no images in that directory.

Additional info:
Relevant part of log at VT3; typed by hand, sorry for any typos; I can recheck
any part if it looks wrong.

* partition /dev/hda1 selected
* mounting device hda1 for hard drive install
* mntloop loop7 on /tmp/loopimage as
/tmp/hdimage//home/mitr/iso/FC4-test1-i386-disc1.iso fd is 13
* mntloop loop0 on /mnt/runtime as /tmp/loopimage/Fedora/base/hdstg2.img fd is 13
* umounting loopback /tmp/runtime loop0
* LOOP_CLR_FD failed for /tmp/runtime loop0 (Device or resource busy)
* umounting loopback /tmp/loopimage loop7
* LOOP_CLR_FD failed for /tmp/loopimage loop7 (Device or resource busy)
* Path to valid iso is /tmp/hdimage//home/mitr/iso/FC4-test1-i386-disc1.iso
* Looking for updates for HD in /tmp/hdimage//home/mitr/iso/updates.img
* mntloop loop0 on /tmp/loopimage as
/tmp/hdimage//home/mitr/iso/FC4-test1-i386-disc1.iso fd is 12
* LOOP_SET_FD failed: Device or resource busy
* umounting loopback /tmp/loopimage loop0
* LOOP_CLR_FD failed for /tmp/loopimage loop0 (Device or resource busy)

Comment 1 Jeremy Katz 2005-03-16 00:16:06 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 19:08:18 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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