Date: Tue, 9 Jan 2001 09:35:18 -0800 (PST) From: Matthew Jacob <mjacob@feral.com> To: Jonathan Perkin <sketchy@netcraft.com> Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Aborted commands and parity errors Message-ID: <Pine.LNX.4.21.0101090931490.27687-100000@zeppo.feral.com> In-Reply-To: <20010109113131.B1688@netcraft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
It's either a bad cable or something that is corrupting data. Be thankful parity caught it. When was the last time you power cycled things? Sometimes a resetting termpwr fuse gets frotzed and termpwr stops being supplied by the drive that's supplying it, thus nullifying termination. It's also true, tho rare, that traces just sometimes go on drive or PC motherboards. Does your system and/or drives run hot? Try a powercycle. Let it cool down. Then boot up again and see. It always could be s/w but in this case I doubt it. > Hey guys, > > Found these in the logfiles this morning - box is: > > o 2.2.8-STABLE as of around Feb 1999 (with cam patches) > o Adaptec 2940 Controller Card > o 3 * Quantum XP34300W 4Gb disks held in an external enclosure > > sd1(ahc0:3:0): ABORTED COMMAND asc:48,0 > sd1(ahc0:3:0): Initiator detected error message received, retries:4 > sd1(ahc0:3:0): parity error during Data-In phase. > sd1(ahc0:3:0): ABORTED COMMAND asc:48,0 > sd1(ahc0:3:0): Initiator detected error message received , retries:3 > sd1(ahc0:3:0): parity error during Data-In phase. > sd1(ahc0:3:0): ABORTED COMMAND asc:48,0 > sd1(ahc0:3:0): Initiator detected error message received , retries:2 > sd1(ahc0:3:0): parity error during Data-In phase. > sd1(ahc0:3:0): ABORTED COMMAND asc:48,0 > sd1(ahc0:3:0): Initiator detected error message received , retries:1 > sd1(ahc0:3:0): parity error during Data-In phase. > sd1(ahc0:3:0): ABORTED COMMAND asc:48,0 > sd1(ahc0:3:0): Initiator detected error message received , FAILURE > > [ lather rinse repeat ] > > swap_pager: I/O error - pagein failed; blkno 77352, size 12288, error 0 > vm_fault: pager input (probably hardware) error, PID 29846 failure > > [ no doubt caused by not being able to access the swap partition ] > > I'd normally guess at a cabling/termination problem, but as this box > has been running fine for years with no problems like this, and the > fact all drives are external shared off the same cable, I'm wondering > if there could be a different problem? > > The box is still running fine, but obviously I can't chance this > happening again and the server crashing. sd1 and sd2 are striped > over ccd. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.21.0101090931490.27687-100000>