Bug 59448 - Error 16 - Device or resource busy
Error 16 - Device or resource busy
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
i586 Linux
medium Severity medium
: ---
: ---
Assigned To: Jeremy Katz
David Lawrence
Depends On:
  Show dependency treegraph
Reported: 2002-02-07 22:38 EST by Need Real Name
Modified: 2007-04-18 12:40 EDT (History)
0 users

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

Attachments (Terms of Use)
list of error messages generated by linux install module (1.23 KB, text/plain)
2002-02-08 01:01 EST, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-02-07 22:38:11 EST
Description of Problem:
During installation at about 90% done, there was a interruption of the 
installation process and a lot of error messages were reported.

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

How Reproducible:

Steps to Reproduce:

Actual Results:
I started again in a custom installation, removed some utilities and I could 
finish the installation. Linux now is running, but without utilities installed.

Expected Results:

Additional Information:
See error messages attached
Comment 1 Need Real Name 2002-02-08 01:01:23 EST
Created attachment 44937 [details]
list of error messages generated by linux install module
Comment 2 Tim Waugh 2002-02-08 02:32:33 EST
Changing component (not a package bug).
Comment 3 Jeremy Katz 2002-02-28 17:58:59 EST
There should be more text in the full traceback message, but my first guess
would be a bad CD.
Comment 4 Michael Fulbright 2002-04-10 14:21:31 EDT
Closing due to inactivity, please reopen if you contine to have problems.
Comment 5 Red Hat Bugzilla 2006-02-21 13:48:25 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.