Bug 199416 - Initial Installation is receiving an error; Using 3 SCSI Hard Drives
Summary: Initial Installation is receiving an error; Using 3 SCSI Hard Drives
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: anaconda
Version: 4.0
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-07-19 13:55 UTC by optimus
Modified: 2007-11-30 22:07 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2006-07-19 14:09:44 UTC


Attachments (Terms of Use)
anaconda dump of error (694.73 KB, text/plain)
2006-07-19 13:55 UTC, optimus
no flags Details

Description optimus 2006-07-19 13:55:58 UTC
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.Attempting to install Linux
2.Using 3 Seagate 74gb SCSI (standalone)drives 
3.Have tried differing Boot orders in the BIOS
4.The installation gets all the way through the initial setup i.e setup 
partition/date/root password etc..., errors when attempting to start 
installation of files
  
Actual results:
Upon the POST, the scsi controller on the LSI chipset motherboard does report 
that one of the drives is "set too narrow".  This is being investigated 
seperately.

Expected results:


Additional info:

Comment 1 optimus 2006-07-19 13:55:59 UTC
Created attachment 132683 [details]
anaconda dump of error

Comment 2 Chris Lumens 2006-07-19 14:09:44 UTC
From the kernel messages in your traceback, it appears you have problems with
the drive, termination, cabling, or something else hardware related.

<4>SCSI error : <0 0 2 0> return code = 0x8000002
<4>Info fld=0x0, Current sdb: sense key Aborted Command
<4>Additional sense: Information unit CRC error detected
<4>end_request: I/O error, dev sdb, sector 0
<3>Buffer I/O error on device sdb, logical block 0
<4>lost page write due to I/O error on sdb


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