Date: Fri, 12 Feb 1999 20:38:20 -0700 (MST) From: "Kenneth D. Merry" <ken@plutotech.com> To: gpalmer@FreeBSD.ORG (Gary Palmer) Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: bad drive? Message-ID: <199902130338.UAA38390@panzer.plutotech.com> In-Reply-To: <61128.918808646@gjp.erols.com> from Gary Palmer at "Feb 12, 1999 3:37:26 am"
next in thread | previous in thread | raw e-mail | index | archive | help
Gary Palmer wrote... > > I found the enclosed messages (appended after my sig) in /var/log/messages on > a machine at work. I'm wondering if these imply a fixable error (e.g. bad > termination) or if one of the drives is slowly dying? > > ahc0: <Adaptec 2940 Ultra SCSI adapter> rev 0x00 int a irq 11 on pci0.10.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > da1: <SEAGATE ST15150W 0023> Fixed Direct Access SCSI-2 device > da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: <SEAGATE ST32550W 0021> Fixed Direct Access SCSI-2 device > da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > > This is from the 19981216 SNAP code. > > Thanks, > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > > Feb 11 12:46:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out while > id > le, LASTPHASE == 0x1, SEQADDR == 0xc > Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message > Sent > Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, > status > = 353 > Feb 11 12:46:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Feb 11 12:46:40 virtual /kernel: SEQADDR == 0x157 > Feb 11 12:47:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x2f - timed out while > id I suppose it is possible that this could be caused by bad termination or something similar. The problem is that we're queueing transactions to the drive, but it isn't responding before the timeout fires. The I/O timeout for da devices is 60 seconds. So, take that however you will. I would first try to make sure that the cable is okay, as well as termination. Make sure there are no bent pins or anything like that. If everything checks out in the cabling/termination department, I would probably start to suspect that the drive is having trouble. Ken -- Kenneth Merry ken@plutotech.com 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?199902130338.UAA38390>