Parity Error Detected In Dt Data Out Phase
message: AIC7899's 2 SCSI channels infect with each other in target mode? Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Wilko Bulte wrote: > On Tue, Aug 19, 2003 at 05:34:40PM +0200, David Landgren wrote: > >>Greetings, >> >>I have an HP Proliant 380GL-D3 running 4.8-STABLE and, for the time > > > DL380-G3 I suppose ;) Ah yes, one of them :) > >>being, a GENERIC kernel. I also have an external Compaq Storageworks >>DLT bay. Both the server and the tape bay both have two SCSI ports, >>and of course it was only the final combination that made anything happen. > > > Tape bay.. what exactly do you have? Can you give me a part# of the > enclosure? Well here's the thing. When the machine arrived, it came with an HP StorageWorks DLT VS 40/80, which is an external stand-alone unit that allows you to select the SCSI ID and daisy chain to another peripheral. It also came with a huge 3U rackable affair simply marked Compaq StorageWorks (no other details) with the room for installing 4 devices, but it was empty, apart from power supply and internal SCSI cables. (I did specify that I wanted to be able to rack the tape drive). So I extracted the DLT unit out of the first enclosure and put it in this enclosure, but the DL380 didn't see it at the BIOS level. Since then, I have come back to the initial setup: the device is now sitting back in its non-rackable external enclosure, and the DL380 BIOS sees it just fine. Curiously enough, the external unit selector was on 6, and the BIOS reported it as ID 12. I changed the selector to 2 and the BIOS now reports it as 4 (i.e. BIOS == selector * 2). In either case, when I run 'camcontrol devlist' it does not show up. As it turns out, I've cleared up the parity error messages. The server has a PCI-X card installed with two SCSI ports (the new thin type). I was trying these ports. What I didn't notice is that there was also a port on the chassis, connected, I guess, directly to the motherboard. The external device is connected to this third port and that cleared up the boot error messages. One suspicious item is that the unit was not delivered with a terminator. Reading the docs, however, hints that it may not be necessary if it's the only device on the chain. Be
Arg list too longNext: SCSI transport failed: reason 'reset'SCSI bus DATA IN phase parity error Cause The most common cause of this problem is http://lists.freebsd.org/pipermail/freebsd-scsi/2003-August/000504.html unapproved hardware. Some SCSI devices for the PC market do not meet the high I/O speed requirements for the UNIX market. Other possible causes of this problem are improper https://docs.oracle.com/cd/E19455-01/806-1075/msgs-2013/index.html cabling or termination, and power fluctuations. Data corruption is possible, but unlikely to occur, because this parity error prevents data transfer. Action Check that all SCSI devices on the bus are Sun-approved hardware. Then verify that all cables measure no longer than six meters total and that all SCSI connections are properly terminated. If power fluctuations are occurring, invest in an uninterruptible power supply. Previous: save: SYSTEM error, Arg list too longNext: SCSI transport failed: reason 'reset' © 2010, Oracle Corporation and/or its affiliates
Format For Printing -XML -Clone This Bug -Last Comment First Last Prev Next This bug is not in your last search results. Bug172552 - aic7xxx detects https://bugzilla.redhat.com/show_bug.cgi?id=172552 `data overrun' for any AHA-39160 devices Summary: aic7xxx detects `data overrun' for any AHA-39160 devices Status: CLOSED WONTFIX Aliases: None Product: Red Hat Enterprise Linux 3 Classification: Red Hat Component: kernel (Show other bugs) Sub Component: --- Version: 3.0 Hardware: i386 Linux Priority medium Severity medium TargetMilestone: --- TargetRelease: --- Assigned To: Tom Coughlan QA Contact: Brian Brock Docs Contact: URL: Whiteboard: Keywords: Depends On: Blocks: parity error Show dependency tree /graph Reported: 2005-11-07 00:58 EST by James Ashton Modified: 2007-11-30 17:07 EST (History) CC List: 1 user (show) petrides See Also: Fixed In Version: Doc Type: Bug Fix Doc Text: Story Points: --- Clone Of: Environment: Last Closed: 2007-10-19 14:51:43 EDT Type: --- Regression: --- Mount Type: --- Documentation: --- CRM: Verified Versions: Category: --- oVirt Team: --- RHEL 7.3 requirements from Atomic Host: parity error detected Cloudforms Team: --- Attachments (Terms of Use) Add an attachment (proposed patch, testcase, etc.) Groups: None (edit) Description James Ashton 2005-11-07 00:58:37 EST Description of problem: Hardware: Dell PowerEdge 1850 with integrated RAID (PERC 4/Di, LSI Logic MegaRAID 521S) and Dual Ultra 320 PCI SCSI card AHA-39160. OS installed on mirrored SCSI drives. Tape robot with two LTO3 drives on one channel of AHA-39160. Connecting any SCSI device to either AHA-39160 SCSI bus generates messages during boot: kernel: (scsi0:A:1:0): data overrun detected in Data-in phase. Tag == 0x5. kernel: (scsi0:A:1:0): Have seen Data Phase. Length = 50. NumSGs = 1. The robot always generates kernel: (scsi0:A:0:0): parity error detected in Data-in phase. SEQADDR(0x83) SCSIRATE(0x0) kernel: (scsi0:A:0:0): parity error detected in Message-in phase. SEQADDR(0x1a5) SCSIRATE(0x0) last message repeated 647 times four times before the kernel gives up: kernel: scsi: device set offline - not ready or command retry failed after bus reset: host 0 channel 0 id 0 lun 0 The tapes drives then operate correctly but the robot is inaccessible. Relevant kernel boot messages: kernel: SCSI subsystem driver Revision: 1.00 kernel: scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 6.2.36 kernel: