Bug 89679
Summary: | [aic7xxx] "parity error" while installing in a SCSI drive with Adapctec 2940U | ||
---|---|---|---|
Product: | [Retired] Red Hat Linux | Reporter: | Oliver Schulze L. <oliver> |
Component: | kernel | Assignee: | Doug Ledford <dledford> |
Status: | CLOSED WONTFIX | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | ||
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: | 2004-09-30 15:40:50 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: |
Description
Oliver Schulze L.
2003-04-25 22:27:28 UTC
Appears to be a message from the kernel, reassigning. This problem ocurred when I was using 2 cp commands in background to copy data from one disk to another. Something like this: cp -a home usr /mnt/new & cp -a var boot /mnt/new & I was in rescue mode. Later, I booted again in rescue mode and issue one cp command at a time and could not see any error. At this stage I don't have too many info about the error message nor how to reproduce it. Maybe it was a problem with my SCSI adapter. I restored the default settings in the SCSI BIOS before I tryied again. Got more info. I manage to upgrade a RH70 to RH9 and while working on the server I noted the message again: "kernel: (scsi:A:6:0): parity error detected in Status phase. SEQADDR(0x7f) SCSIRATE(0x88)" The SEQADDR change with this values: 0x9e, 0xa5, 0x82 The Adaptec card is: AHA-2940 U/UW/D AIC-7881U The mobo is an ASUS P4S-533-MX running a Pentium 4 1700Mhz Thanks for the bug report. However, Red Hat no longer maintains this version of the product. Please upgrade to the latest version and open a new bug if the problem persists. The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases, and if you believe this bug is interesting to them, please report the problem in the bug tracker at: http://bugzilla.fedora.us/ |