Parity Error Detected In Data In Phase
Case and Cooling Fetish CPU & Motherboard Technologia Mobile Computing Outpost Networking Matrix Other Hardware Agora Classifieds Ars DIY Forum (Name TBD!) Operating Systems & Software Battlefront Microsoft OS & Software Colloquium Linux Kung Fu Windows Technical Mojo Distributed Computing Arcana Macintoshian Achaia Programmer's Symposium The Server Room Ars Lykaion Gaming, Extra Strength Caplets The Lounge The Soap Box The Boardroom The Observatory Ars Help & Feedback Ars Subscription Member Areas Image Galleries SCSI Tape backup problem: parity error detected in Data-out phase 5 posts Deffexor Moderator et Subscriptor Registered: Aug 17, 1999Posts: 7576 Posted: Sat Nov 12, 2005 12:58 am Last night I took a backup on a customer's new DDS4 drive and everything went swimmingly. I did something like:tar -cvzpf /dev/st0 *This was fine, except that I realized that the DDS4 drive had hardware compression built-in and enabled, so compression thru the OS was unnecessary.So tonight we popped in a new tape and did basically the same backup except without the "z" switch. Unfortunately, the first time I tried to backup, the tape job ended prematurely after 3 minutes due to an I/O error with the tape drive. The error message from syslog:Nov 12 00:39:36 axiom kernel: (scsi0:A:0:0): parity error detected in Data-out phase. SEQADDR(0x83) SCSIRATE(0x95) Nov 12 00:39:36 axiom kernel: st0: Error 60000 (sugg. bt 0x0, driver bt 0x0, host bt 0x6).I rewound and tried again. Again the job died after 30 minutes due to an I/O error.Nov 12 01:26:08 axiom kernel: (scsi0:A:0:0): parity error detected in Data-out phase. SEQADDR(0x85) SCSIRATE(0x95) Nov 12 01:26:08 axiom kernel: st0: Error 60000 (sugg. bt 0x0, driver bt 0x0, host bt 0x6).What does this error mean exactly? I'm assuming this means there is a problem with the tape drive? But SEQADDR and SCSIRATE in hex codes mean nothing to me. So does the Error 60000 and sugg bt, driver bt, and host bt.Right now I'm just wondering if I have
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://arstechnica.com/civis/viewtopic.php?t=345452 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
Date: Fri, 03 Jan 2003 14:56:38 Delivered-to: freebsd-stable@freebsd.org Delivery-date: Fri, 03 Jan 2003 23:57:02 +0200 Envelope-to: archive@lists.atm.tut.fi List-archive: (Web Archive) List-help: (List Instructions) List-id: List-subscribe: List-unsubscribe: Sender: owner-freebsd-stable@FreeBSD.ORG References: 20021124193031.GA18148@nvg.ntnu.no http://www.atm.tut.fi/list-archive/freebsd-stable/msg08013.html On Nov 24, 2002 in freebsd-stable, taliesin@nvg.ntnu.no wrote: >Then these turned up today: > >(da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x56) SCSIRATE(0x93) >(da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8a) https://bbs.archlinux.org/viewtopic.php?id=40729 SCSIRATE(0x93) >(da0:ahc0:0:0:0): parity error detected in Data-in phase. SEQADDR(0x8a) SCSIRATE(0x93) >(da0:ahc0:0:0:0): READ(10). CDB: 28 0 0 8f df 22 0 0 70 0 >(da0:ahc0:0:0:0): ABORTED COMMAND asc:48,0 >(da0:ahc0:0:0:0): Initiator detected error parity error message received >(da1:ahc0:0:1:0): parity error detected in Data-in phase. SEQADDR(0x8b) SCSIRATE(0x93) >etc. I'm having the same problem since adding a second hard drive to the 68-pin LVD/SE cable on an Adaptec 29160 on Dec. 20th. At this point, I believe it to be a software problem. The machine has two PPro 200 cpus, 384MB ram, Linksys lne100tx NIC, generic PCI USB card, parity error detected Elsa Synergy II-32 PCI video card, Adaptec 1510 ISA SCSI controller (for a scanner) and SoundBlaster Vibra16 ISA card. There are two drives on the LVD/SE cable and neither is terminated as the cable is terminated. There is a SCSI CDRW on the 50-pin SE connector and a 9.2GB drive on the 68-pin SE connector. Both are terminated. Many months before, 4.0 was installed on the 18Gb drive and upgraded to 4.4. When I tried 4.4 from the HD, after adding the second LVD drive, parity errors over-ran the screen and the machine automatically rebooted. Trying the 4.0 CD produced the same parity errors and a stall. Removing _all_ drives and cables but drive 0, the 18GB drive containing the earlier FreeBSD didn't work. There are now no circumstances that allow FreeBSD to install on that drive. Booting the 4.7 CD didn't work, but allowed getting debug output. All unnecessary cards were removed from the machine, leaving just the Adaptec and video card in hopes that something would improve, but it didn't. The Adaptec 29160 has the latest BIOS, 3.1, but this issue started w
From: Erie, PA Registered: 2005-10-15 Posts: 200 SCSI issues I just installed a SCSI card in my system, but the drives don't show up in dev. DMESG says:scsi0 : Adaptec AIC7XXX EISA/VLB/PCI SCSI HBA DRIVER, Rev 7.0 aic7880: Ultra Wide Channel A, SCSI Id=7, 16/253 SCBsscsi 0:0:0:0: Direct-Access SEAGATE ST336607LC 0002 PQ: 0 ANSI: 3scsi0:A:0:0: Tagged Queuing enabled. Depth 32 target0:0:0: Beginning Domain Validation target0:0:0: wide asynchronous(scsi0:A:0:0): parity error detected in Data-in phase. SEQADDR(0x7c) SCSIRATE(0x80)(scsi0:A:0:0): parity error detected in Data-in phase. SEQADDR(0x7c) SCSIRATE(0x80)(scsi0:A:0:0): parity error detected in Data-in phase. SEQADDR(0x7d) SCSIRATE(0x80) target0:0:0: Wide Transfers Fail target0:0:0: FAST-10 SCSI 10.0 MB/s ST (100 ns, offset 15)scsi 0:0:0:0: timing out command, waited 20s target0:0:0: Domain Validation detected failure, dropping back target0:0:0: FAST-10 SCSI 6.8 MB/s ST (148 ns, offset 15)scsi 0:0:0:0: timing out command, waited 20s target0:0:0: Domain Validation detected failure, dropping back target0:0:0: asynchronousscsi 0:0:0:0: timing out command, waited 20s target0:0:0: Domain Validation detected failure, dropping back target0:0:0: asynchronousscsi 0:0:0:0: timing out command, waited 20s target0:0:0: Domain Validation detected failure, dropping backscsi 0:0:0:0: timing out command, waited 20s target0:0:0: Domain Validation detected failure, dropping backscsi 0:0:0:0: timing out command, waited 20s target0:0:0: Domain Validation Failure, dropping back to Asynchronous target0:0:0: Domain Validation skipping write tests target0:0:0: Ending Domain Validationscsi 0:0:0:0: timing out command, waited 24sAny ideas on where to start? The drives test good with IBM's diag tool. Offline #2 2007-12-07 13:10:40 bt Member Registered: 2007-04-11 Posts: 191 Re: SCSI issues The ST336607LC is an Ultra 320 drive. Does the Adaptec 2940 handle this drive? It may be the wrong card. Last edited by bt (2007-12-07 13:13:12) Offline #3 2007-12-07 15:20:45 byte Member From: Düsseldorf (DE) Registered: 2006-05-01 Posts: 2,045 Re: SCSI issues I can get U160 drives to work on an -UW controller, but U320 might be a different beast, although it should be downwards-compatible.Check your jumpers, controller bios setup, cabling... 1000 Offline Pages: 1 Index »Applications & Desktop Environments »SCSI issues Board footer Jump to Newbie Corner Installation Kernel & Hardware Applications & Desktop Environments Laptop Issues Networking, Server, and Protection Multimedia and Games System Administration Other Arch