Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Aug 1999 17:30:29 -0700
From:      "Alec Wolman" <wolman@cs.washington.edu>
To:        freebsd-scsi@freebsd.org
Subject:   OS bug or hardware problem?
Message-ID:  <199908130030.RAA53343@miles.cs.washington.edu>

next in thread | raw e-mail | index | archive | help

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: chip0: <Intel 82443BX host to PCI bridge> rev 0x02 on pci0.0.0
Aug 12 02:44:04 laver /kernel: chip1: <Intel 82443BX host to AGP bridge> rev 0x02 on pci0.1.0
Aug 12 02:44:04 laver /kernel: chip2: <Intel 82371AB PCI to ISA bridge> rev 0x02 on pci0.7.0
Aug 12 02:44:04 laver /kernel: chip3: <Intel 82371AB Power management controller> rev 0x02 on pci0.7.3
Aug 12 02:44:04 laver /kernel: ahc0: <Adaptec aic7895 Ultra SCSI adapter> rev 0x04 int a irq 10 on pci0.14.0
Aug 12 02:44:04 laver /kernel: ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs
Aug 12 02:44:04 laver /kernel: ahc1: <Adaptec aic7895 Ultra SCSI adapter> rev 0x04 int b irq 10 on pci0.14.1
Aug 12 02:44:04 laver /kernel: ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs
Aug 12 02:44:04 laver /kernel: da1 at ahc0 bus 0 target 3 lun 0
Aug 12 02:44:04 laver /kernel: da1: <IBM DGHS18U 0350> Fixed Direct Access SCSI-3 device 
Aug 12 02:44:04 laver /kernel: da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
Aug 12 02:44:04 laver /kernel: da1: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
Aug 12 02:44:04 laver /kernel: da2 at ahc1 bus 0 target 0 lun 0
Aug 12 02:44:04 laver /kernel: da2: <IBM DGHS18U 03B0> Fixed Direct Access SCSI-3 device 
Aug 12 02:44:04 laver /kernel: da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
Aug 12 02:44:04 laver /kernel: da2: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C)
Aug 12 02:44:04 laver /kernel: da4 at ahc1 bus 0 target 6 lun 0
Aug 12 02:44:04 laver /kernel: da4: <SEAGATE ST423451W 0011> Fixed Direct Access SCSI-2 device 
Aug 12 02:44:04 laver /kernel: da4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
Aug 12 02:44:04 laver /kernel: da4: 22130MB (45322644 512 byte sectors: 255H 63S/T 2821C)
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)
Aug 12 02:44:04 laver /kernel: da0 at ahc0 bus 0 target 0 lun 0
Aug 12 02:44:04 laver /kernel: da0: <SEAGATE ST39173W 5698> Fixed Direct Access SCSI-2 device 
Aug 12 02:44:04 laver /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled
Aug 12 02:44:04 laver /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C)

Any helpful hints would be most appreicated?

Alec




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?199908130030.RAA53343>