Bug 76398 - unhandled exception caused by bad sector?
unhandled exception caused by bad sector?
Status: CLOSED DUPLICATE of bug 66181
Product: Red Hat Linux
Classification: Retired
Component: anaconda (Show other bugs)
7.3
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Michael Fulbright
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2002-10-21 08:08 EDT by Need Real Name
Modified: 2007-04-18 12:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2002-10-21 08:09:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
prompted save from unhandled exception during install (59.66 KB, text/plain)
2002-10-21 08:09 EDT, Need Real Name
no flags Details

  None (edit)
Description Need Real Name 2002-10-21 08:08:28 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.0.1)
Gecko/20020823 Netscape/7.0

Description of problem:
anaconda doing an nfs upgrade from 5.2 (2.0.36-3) to 7.3 in 32M/500M throws an
unhandled exception, apparently (Ctrl-Alt-F4) on hitting a bad disk sector.
Also occured doing nfs install - during "check for bad sectors"!

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


How reproducible:
Always

Steps to Reproduce:
1.boot from bootnet.img floppy
2.answer questions
3.agree to start install
	

Actual Results:  unhandled exception error, goto buzilla, do not retain bootable
system

Expected Results:  red hat 7.3

Additional info:
Comment 1 Need Real Name 2002-10-21 08:09:46 EDT
Created attachment 81324 [details]
prompted save from unhandled exception during install
Comment 2 Michael Fulbright 2002-10-23 15:45:45 EDT
Your system has bad sector(s) - the installer did not handle this exception
correctly.


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

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