Bug 82388 - Boot disk creation fails
Boot disk creation fails
Status: CLOSED DUPLICATE of bug 82298
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
Mike McLean
:
Depends On:
Blocks: 79578
  Show dependency treegraph
 
Reported: 2003-01-21 15:21 EST by Bernd Bartmann
Modified: 2008-01-17 12:49 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:17 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
Anaconda screenshot from Phoebe2 boot disk creation screen (48.11 KB, image/png)
2003-01-21 15:22 EST, Bernd Bartmann
no flags Details

  None (edit)
Description Bernd Bartmann 2003-01-21 15:21:48 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20021003

Description of problem:
The creation of a boot disk during installation fails. I get an error message
indicating that the disk is probably broken (which it is definitely not, cause I
tested al least 3 different disks). I've attached a screenshot with the german
error message from anaconda. As the creation of the boot disk takes much longer
than on any other earlier Red Hat release I suspect that the disk is simply
full. Creating the boot disk using mkbootdisk on the freshly installed system
works without any problem.

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


How reproducible:
Always

Steps to Reproduce:
1. Try to create a boot disk at install time
2.
3.
    

Additional info:
Comment 1 Bernd Bartmann 2003-01-21 15:22:52 EST
Created attachment 89484 [details]
Anaconda screenshot from Phoebe2 boot disk creation screen
Comment 2 Jeremy Katz 2003-01-22 22:48:32 EST

*** This bug has been marked as a duplicate of 82298 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:51:17 EST
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.