Parity Error Detected In Message In Phase
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 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 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
during kernel boot encountered. Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] Greetings, I have an HP Proliant 380GL-D3 running 4.8-STABLE and, for the time 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 https://docs.oracle.com/cd/E19455-01/806-1075/msgs-2013/index.html final combination that made anything happen. I have the storage bay powered up, and the DLT settles down and shows a single green led. I then power up the server and after it gets to booting the kernel, the following messages appear on the console: (probe30:ahc1:0:0:0): parity error detected in https://lists.freebsd.org/pipermail/freebsd-scsi/2003-August/000500.html DT Data-in phase. SEQADDR(0x1a5) SCSIRATE(0x0) Unexpected non-DT Data Phase (probe30:ahc1:0:0:0): parity error detected in DT Data-out phase. SEQADDR(0x1a6) SCSIRATE(0x0) Unexpected non-DT Data Phase (probe30:ahc1:0:0:0): parity error detected in DT Data-out phase. SEQADDR(0x1a6) SCSIRATE(0x0) Unexpected non-DT Data Phase (probe30:ahc1:0:0:0): parity error detected in DT Data-out phase. SEQADDR(0x1a5) SCSIRATE(0x0) Unexpected non-DT Data Phase After several thousand of these go by, I get the following (retrieved from dmesg): (probe30:ahc1:0:0:0): SCB 0x8 - timed out >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<< ahc1: Dumping Card State while idle, at SEQADDR 0x16b Card was paused ACCUM = 0x8, SINDEX = 0x81, DINDEX = 0xe4, ARG_2 = 0x2 HCNT = 0x0 SCBPTR = 0x0 SCSIPHASE[0x1]:(DATA_OUT_PHASE) SCSISIGI[0x36]:(REQI|BSYI|ATNI|MSGI) ERROR[0x0] SCSIBUSL[0x0] LASTPHASE[0x1]:(P_BUSFREE) SCSISEQ[0x12]:(ENAUTOATNP|ENRSELI) SBLKCTL[0xa]:(SELWIDE|SELBUSB) SCSIRATE[0x0] SEQCTL[0x10]:(FASTMODE) SEQ_FLAGS[0x40]:(NO_CDB_SENT) SSTAT0[0x2]:(SPIORDY) SSTAT1[0x5]:(REQINIT|SCSIPERR) SSTAT2[0x1]:(DUAL_EDGE_ERR) SSTAT3[0x0] SIMODE0[0x8]:(ENSWRAP) SIMODE1[0xac]:(ENSCSIPERR|ENBUSFREE|ENSCSIRST|ENSELTIMO) SXFRCTL0[0x88]:(SPIOEN|DFON) DFCNTRL[0x0] DFSTATUS[0x8a]:(FIFOFULL|HDONE|PRELOAD_AVAIL) STACK: 0x34 0x34 0x34 0x16a SCB count = 20 Kernel NEXTQSCB = 7 Card NEXTQSCB = 7 QINFIFO entries: Waiting Queue ent
/proc/scsi/scsi Issues related to hardware problems Post Reply Print view Search Advanced search 6 posts • Page 1 of 1 ToddAndMargo Posts: http://www.centos.org/forums/viewtopic.php?t=22509 397 Joined: 2007/02/20 04:27:08 Location: Milky Way/Sol/Earth/USA/Nevada GMT-8 no tape drive in /proc/scsi/scsi Quote Postby ToddAndMargo » 2007/04/17 03:23:32 Hi All, I have an Exabyte VXA3 on an Adaptec 16160 scsi card. I am using CentOS 5.The VXA3 BIOS probes on ID=1 at boot up (Adaptec's BIOS). The drive doesnot show up in "cat /proc/scsi/scsi". In my messages log parity error I get the following boot messages:Apr 16 20:14:55 server kernel: scsi1 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0Apr 16 20:14:55 server kernel: Apr 16 20:14:55 server kernel: aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBsApr 16 20:14:55 server kernel: Apr 16 20:14:55 server kernel: (scsi1:A:1:0): parity error detected in Data-in phase. SEQADDR(0x1a6) SCSIRATE(0x0)Apr 16 20:14:55 server kernel: parity error detected Unexpected non-DT Data PhaseApr 16 20:14:55 server kernel: (scsi1:A:1:0): parity error detected in Message-in phase. SEQADDR(0x1a7) SCSIRATE(0x0)repeats 18 times.How do I fix this?Many thanks,-T Top ToddAndMargo Posts: 397 Joined: 2007/02/20 04:27:08 Location: Milky Way/Sol/Earth/USA/Nevada GMT-8 Re: no tape drive in /proc/scsi/scsi Quote Postby ToddAndMargo » 2007/04/17 03:56:06 Hi All, Mystery solved: I swapped a spare VXA 1 into the server gotthe following:cat /proc/scsi/scsiAttached devices:Host: scsi1 Channel: 00 Id: 05 Lun: 00 Vendor: ECRIX Model: VXA-1 Rev: 2A6A Type: Sequential-Access ANSI SCSI revision: 02The VXA 3 is still under hot swap. I will be exchanging it for a another unit.-T Top mtnbkr Posts: 2 Joined: 2007/06/01 19:14:26 Re: no tape drive in /proc/scsi/scsi Quote Postby mtnbkr » 2007/06/01 19:26:49 Any luck with the replacement VXA3? I Just got (2) VXA3 upgrade drives to put into my client's 1U Packetloaders and BOTH VXA3 drives are doing exactly the same thing you have described.Did you ever get a resolution to this?I am checking to see if a newer aic7xxx driver will fix this - ie: looking at lastest kernel