Date: Thu, 12 Aug 1999 20:06:24 -0600 (MDT) From: "Kenneth D. Merry" <ken@kdm.org> To: wolman@cs.washington.edu (Alec Wolman) Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: OS bug or hardware problem? Message-ID: <199908130206.UAA57880@panzer.kdm.org> In-Reply-To: <199908130030.RAA53343@miles.cs.washington.edu> from Alec Wolman at "Aug 12, 1999 05:30:29 pm"
index | next in thread | previous in thread | raw e-mail
Alec Wolman wrote... > > I just recently upgraded a machine from 3.1-19990403-STABLE to > 3.2-19990810-STABLE. After the upgrade, I now get SCSI parity > errors when I attempt to use one of the disks (da3): > > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 11 10 80 0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 1a 10 80 0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): WRITE(06). CDB: a 5 2f 90 80 0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): ABORTED COMMAND asc:47,0 > Aug 12 17:12:58 laver /kernel: (da3:ahc1:0:5:0): SCSI parity error > > > These look to me like the disk has a hardware problem, but its a little surprising > that the disk errors were introduced at exactly the same time at which > I performed the OS upgrade. Is it possible that in the old version > of the OS these errors were occuring but not being reported? > > Anyway, here is the relevant hardware info extracted from dmesg: [ ... ] > Aug 12 02:44:04 laver /kernel: da3 at ahc1 bus 0 target 5 lun 0 > Aug 12 02:44:04 laver /kernel: da3: <IBM DRHS36V 0110> Fixed Direct Access SCSI-3 device > Aug 12 02:44:04 laver /kernel: da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled > Aug 12 02:44:04 laver /kernel: da3: 35239MB (72170879 512 byte sectors: 255H 63S/T 4492C) [ ... ] > Any helpful hints would be most appreicated? My guess is that it is what it appears to be -- a parity error. I'm not sure why it didn't show up before. I would look for bent connector pins or other cabling type problems. Another possibility is a connector problem on the drive, like a loose solder point or something. Since that drive is the only one complaining, it could just be a bent pin on the connector for that drive. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the messagehelp
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199908130206.UAA57880>