Bug 66199 - Installer Stall when trying to install checking for bad blocks
Summary: Installer Stall when trying to install checking for bad blocks
Status: CLOSED DUPLICATE of bug 66181
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda   
(Show other bugs)
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-06-06 02:41 UTC by Jack
Modified: 2007-04-18 16:43 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-06-17 21:28:20 UTC
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 error log (58.77 KB, text/plain)
2002-06-06 02:46 UTC, Jack
no flags Details

Description Jack 2002-06-06 02:41:08 UTC
Description of Problem:


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


How Reproducible:


Steps to Reproduce:
1. 
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Jack 2002-06-06 02:46:15 UTC
Created attachment 59825 [details]
anaconda error log

Comment 2 Michael Fulbright 2002-06-06 15:53:58 UTC
Did you choose to check for bad blocks? Please try without if so, there is a
problem with bad blocks checking.

Comment 3 Michael Fulbright 2002-06-17 21:28:14 UTC
This error occurs when the badblocks command detects bad blocks on the system. 
The traceback occurred because the output from the badblocks command has
changed, fooling our parser.

If you get this traceback it means you have bad blocks on the drive it was testing.

In the future an error dialog will be presented saying bad blocks have been
detected.

Comment 4 Michael Fulbright 2002-06-17 21:31:42 UTC

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

Comment 5 Michael Fulbright 2002-12-20 17:38:25 UTC
Time tracking values updated


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