Bug 181816 - Crash when booting to linux resuce mode
Summary: Crash when booting to linux resuce mode
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda
Version: 4.0
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-16 20:14 UTC by Cove Schneider
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-17 19:29:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Anaconda crash dump from floppy (57.43 KB, text/plain)
2006-02-16 20:14 UTC, Cove Schneider
no flags Details

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.


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