LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices


Reply
  Search this Thread
Old 12-24-2008, 02:03 PM   #1
SBN
Member
 
Registered: Jul 2006
Distribution: UBUNTU, CentOS, FEDORA 8
Posts: 474

Rep: Reputation: 30
kernel: Additional sense: Scsi parity error ()


Hey what kind of problem is this parity error?

here the ouput from dmesg:

Quote:
Vendor: HP Model: Ultrium 2-SCSI Rev: F6AW
Type: Sequential-Access ANSI SCSI revision: 03
Attached scsi tape st2 at scsi2, channel 0, id 8, lun 0
st2: try direct i/o: yes (alignment 512 B), max page reachable by HBA 4503599627370495
Attached scsi generic sg168 at scsi2, channel 0, id 8, lun 0, type 1
Vendor: HP Model: Ultrium 2-SCSI Rev: F6AW
Type: Sequential-Access ANSI SCSI revision: 03
Attached scsi tape st3 at scsi2, channel 0, id 8, lun 1
st3: try direct i/o: yes (alignment 512 B), max page reachable by HBA 4503599627370495
Attached scsi generic sg169 at scsi2, channel 0, id 8, lun 1, type 1
scsi0 (0,8,1) : reservation conflict
st1: Error 18 (sugg. bt 0x0, driver bt 0x0, host bt 0x0).
st0: Block limits 1 - 16777215 bytes.
st3: Block limits 1 - 16777215 bytes.
qla2400 0000:0c:00.0: qla2xxx_eh_abort: cmd already done sp=0000000000000000 timeout=0x14
st2: Block limits 1 - 16777215 bytes.
st1: Block limits 1 - 16777215 bytes.
qla2400 0000:0c:00.0: qla2xxx_eh_abort: cmd already done sp=0000000000000000 timeout=0x14
st0: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st1: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st2: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st3: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
qla2400 0000:0c:00.0: qla2xxx_eh_abort: cmd already done sp=0000000000000000 timeout=0x14
qla2400 0000:0c:00.0: Scheduling rescan for new luns...
qla2400 0000:0c:00.1: Scheduling rescan for new luns...
qla2400 0000:0f:00.0: Scheduling rescan for new luns...
qla2400 0000:0f:00.1: Scheduling rescan for new luns...
qla2400 0000:0c:00.0: Scheduling rescan for new luns...
qla2400 0000:0c:00.1: Scheduling rescan for new luns...
qla2400 0000:0f:00.0: Scheduling rescan for new luns...
qla2400 0000:0f:00.1: Scheduling rescan for new luns...
qla2400 0000:0c:00.0: Scheduling rescan for new luns...
qla2400 0000:0c:00.1: Scheduling rescan for new luns...
qla2400 0000:0f:00.0: Scheduling rescan for new luns...
qla2400 0000:0f:00.1: Scheduling rescan for new luns...
qla2400 0000:0c:00.0: Scheduling rescan for new luns...
qla2400 0000:0c:00.1: Scheduling rescan for new luns...
qla2400 0000:0f:00.0: Scheduling rescan for new luns...
qla2400 0000:0f:00.1: Scheduling rescan for new luns...
st2: Error with sense data: Current st2: sense key Aborted Command
Additional sense: Scsi parity error
st2: Error with sense data: Current st2: sense key Aborted Command
Additional sense: Scsi parity error
opcle[28221]: segfault at 0000000008000000 rip 00000000f7c68939 rsp 00000000ffffd17c error 4
opcle[4408]: segfault at 0000000008000000 rip 00000000f7c68939 rsp 00000000ffffd17c error 4
bma[4578]: segfault at 0000000000001f70 rip 00000000004850e4 rsp 0000007fbfffdee0 error 4
st2: Error with sense data: Current st2: sense key Aborted Command
Additional sense: Scsi parity error
st2: Error with sense data: Current st2: sense key Aborted Command
Additional sense: Scsi parity error
st2: Error with sense data: Current st2: sense key Aborted Command
Additional sense: Scsi parity error
st0: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st1: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st2: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st3: Error 10000 (sugg. bt 0x0, driver bt 0x0, host bt 0x1).
st2: Error 70000 (sugg. bt 0x0, driver bt 0x0, host bt 0x7).
st3: Error 70000 (sugg. bt 0x0, driver bt 0x0, host bt 0x7).
 
Old 12-24-2008, 02:21 PM   #2
stress_junkie
Senior Member
 
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335
The st device implies SCSI tape.

The segfault (segmentation fault) implies that the driver is trying to access a resource that it is not permitted to access. Either it doesn't have permission or the segment doesn't exist.

The parity error is usually associated with data on the tape being corrupt.

The error with sense data is usually associated with the tape controller configuration. It is possible that the SCSI tape does not have the jumper set correctly to identify its SCSI device number.

Those are all areas that could be involved with the above listed error messages. There may be other reasons but I think that those reasons are the most likely to be causing the problem.

It is VERY likely that you only have one problem. If you fix that then the other problems may go away.
 
Old 12-24-2008, 02:48 PM   #3
SBN
Member
 
Registered: Jul 2006
Distribution: UBUNTU, CentOS, FEDORA 8
Posts: 474

Original Poster
Rep: Reputation: 30
Is this a critical problem, what would be the effect to the system?
 
Old 12-24-2008, 06:40 PM   #4
stress_junkie
Senior Member
 
Registered: Dec 2005
Location: Massachusetts, USA
Distribution: Ubuntu 10.04 and CentOS 5.5
Posts: 3,873

Rep: Reputation: 335Reputation: 335Reputation: 335Reputation: 335
Quote:
Originally Posted by SBN View Post
Is this a critical problem, what would be the effect to the system?
It seems like your Ultrium tape drive isn't configured correctly. If it works properly then it may not be a problem. On the other hand some or all the data going onto the tapes may be corrupted. Or the error detection that is built into the tape drive may not work properly. You might not notice a problem until you put another SCSI device on the same SCSI controller. Who knows? It's hard to say without me sitting down at your computer and looking around, testing the tape drive, etc.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Parity error on scsi hardware oudoubah Linux - Hardware 0 05-12-2006 06:32 AM
SCSI parity error detected saavik Linux - Hardware 0 04-05-2006 01:39 AM
How to Stop SCSI Parity Error Messages MQMan Linux - Hardware 4 07-12-2005 01:31 PM
scsi parity error kev82 Linux - Hardware 2 09-14-2004 06:35 PM
SCSI Parity error Redhat 7.3 The Jesus Linux - Hardware 1 11-13-2002 03:14 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware

All times are GMT -5. The time now is 10:05 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration