Bug 181816

Summary: Crash when booting to linux resuce mode
Product: Red Hat Enterprise Linux 4 Reporter: Cove Schneider <cove>
Component: anacondaAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Mike McLean <mikem>
Severity: medium Docs Contact:
Priority: medium    
Version: 4.0   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2006-02-17 19:29:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Anaconda crash dump from floppy none

Description Cove Schneider 2006-02-16 20:14:46 UTC 
Description of problem:

System can't mount file system anymore, mount 22 error (what ever that means). Boot into linux rescue 
disk, at the time it probes the file system it pops up a screen with a back trace and asks me to save it to 
a floppy and report it.

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

Not sure.

How reproducible:

Not sure.

Steps to Reproduce:
1.
2.
3.
  
Actual results:

Back trace from exception.

Expected results:

No expection.

Additional info:
Comment 1 Cove Schneider 2006-02-16 20:14:46 UTC 
Created attachment 124782 [details]
Anaconda crash dump from floppy
Comment 2 Chris Lumens 2006-02-17 19:29:33 UTC 
You appear to be having hardware-related problems, as shown by the following
sample from your exception dump:

<4>read_callback: read failed, status = 5
<4>SCSI error : <0 0 0 0> return code = 0x8000002
<4>Info fld=0x0, Current sda: sense key Hardware Error
<4>Additional sense: Internal target failure
<4>end_request: I/O error, dev sda, sector 265197
<3>JBD: Failed to read block at offset 5434
<4>JBD: recovery failed
<3>EXT3-fs: error loading journal.
Comment 3 Cove Schneider 2006-02-17 21:06:39 UTC 
Yup, there was something wrong with the disk. The dialog box that poped up told me that it had 
encountered a bug and to report it.