Red Hat General - SCSI Error

This is Interesting: Free IT Magazines  
Home > Archive > Red Hat General > April 2004 > SCSI Error





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author SCSI Error
TC

2004-04-19, 11:35 am



Hello,



I am having problem with SCSI device. I am getting irregularly SCSI
error msg once or twice per week. Can anyone point out where I should start
troubleshooting?

It's Dell PowerEdge 1600SC and running Redhat 3.0 AS.



Thanks





cat /var/log/message

..

Apr 18 09:48:22 server kernel: SCSI Error: (0:3:0) Status=02h (CHECK
CONDITION)

Apr 18 09:48:22 server kernel: Key=Bh (ABORTED COMMAND); FRU=00h

Apr 18 09:48:22 server kernel: ASC/ASCQ=47h/00h ""

Apr 18 09:48:22 server kernel: CDB: 2A 00 00 00 4A 5F 00 00 08 00

...





cat /proc/scsi/scsi



Host: scsi0 Channel: 00 Id: 06 Lun: 00

Vendor: ARCHIVE Model: Python 06408-XXX Rev: 9050

Type: Sequential-Access ANSI SCSI revision: 03

Host: scsi2 Channel: 00 Id: 00 Lun: 00

Vendor: SEAGATE Model: ST318432LW Rev: 2227

Type: Direct-Access ANSI SCSI revision: 03

Host: scsi2 Channel: 00 Id: 03 Lun: 00

Vendor: QUANTUM Model: ATLAS10K2-TY734J Rev: DDD6

Type: Direct-Access ANSI SCSI revision: 03







cat /proc/scsi/aic7xxx/0

Adaptec AIC7xxx driver version: 6.2.36

Adaptec 3960D Ultra160 SCSI adapter

aic7899: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs

Allocated SCBs: 6, SG List Length: 85



Serial EEPROM:

0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a

0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a 0xc33a

0xb8f4 0x7c5d 0x2807 0x0010 0x0300 0xffff 0xffff 0xffff

0xffff 0xffff 0xffff 0xffff 0xffff 0xffff 0x0250 0x964f



Target 0 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 1 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 2 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 3 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 4 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 5 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 6 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Goal: 80.000MB/s transfers (40.000MHz, offset 32, 16bit)

Curr: 80.000MB/s transfers (40.000MHz, offset 32, 16bit)

Channel A Target 6 Lun 0 Settings

Commands Queued 2154145

Commands Active 0

Command Openings 1

Max Tagged Openings 0

Device Queue Frozen Count 0

Target 7 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 8 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 9 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 10 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 11 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 12 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 13 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 14 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)

Target 15 Negotiation Settings

User: 160.000MB/s transfers (80.000MHz DT, offset 127, 16bit)


Scott Lurndal

2004-04-19, 2:35 pm

"TC" <shimashi@hotmail.com> writes:

>
>Apr 18 09:48:22 server kernel: SCSI Error: (0:3:0) Status=02h (CHECK CONDITION)
>Apr 18 09:48:22 server kernel: Key=Bh (ABORTED COMMAND); FRU=00h
>Apr 18 09:48:22 server kernel: ASC/ASCQ=47h/00h ""


ASC =47
ASCQ=0

Indicates a SCSI parity error when using the Quantum Atlas 10k disk drive. This is
a bus parity error - not a parity error of the data on the device, but rather
a parity error that occurs during data transfer between the device and the host.

These codes are enumerated in the SCSI Primary Commands ANSI Draft standard
avaiable for download from www.t10.org (spc3r17.pdf)

As for cause, look for a bad cable or loose connector first.

scott
Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com