From owner-freebsd-hardware Thu Sep 24 08:43:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA18051 for freebsd-hardware-outgoing; Thu, 24 Sep 1998 08:43:23 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vnode.vmunix.com (vnode.vmunix.com [209.112.4.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA18046 for ; Thu, 24 Sep 1998 08:43:22 -0700 (PDT) (envelope-from mark@vnode.vmunix.com) Received: (from mark@localhost) by vnode.vmunix.com (8.8.8/8.8.8) id LAA01938 for freebsd-hardware@freebsd.org; Thu, 24 Sep 1998 11:43:18 -0400 (EDT) (envelope-from mark) Message-ID: <19980924114317.A1903@vmunix.com> Date: Thu, 24 Sep 1998 11:43:17 -0400 From: Mark Mayo To: freebsd-hardware@FreeBSD.ORG Subject: hd error messages.. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i X-Operating-System: FreeBSD 2.2.6-STABLE i386 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org These just showed up in messages: > sd0(ahc0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > sd0(ahc0:0:0): SCB 0x3 timedout while recovery in progress > Ordered Tag sent > sd0(ahc0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd0(ahc0:0:0): Queueing an Abort SCB > sd0(ahc0:0:0): Abort Message Sent > sd0(ahc0:0:0): SCB 0 - Abort Tag Completed. > sd0(ahc0:0:0): no longer in timeout > sd0(ahc0:0:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > sd0(ahc0:0:0): SCB 0x3 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x1 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd0(ahc0:0:0): Queueing an Abort SCB > sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress > sd0(ahc0:0:0): Abort Message Sent > sd0(ahc0:0:0): SCB 2 - Abort Tag Completed. > sd0(ahc0:0:0): no longer in timeout > Ordered Tag sent > sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > Ordered Tag queued > sd0(ahc0:0:0): SCB 0x1 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR = 0x7 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa > sd0(ahc0:0:0): Queueing an Abort SCB > sd0(ahc0:0:0): SCB 0x2 timedout while recovery in progress > sd0(ahc0:0:0): SCB 0x0 timedout while recovery in progress > sd0(ahc0:0:0): Abort Message Sent > sd0(ahc0:0:0): SCB 3 - Abort Tag Completed. > sd0(ahc0:0:0): no longer in timeout > Ordered Tag sent Nothing looks fatal, no panic or anything. I was doing a large untar at the time I believe (didn't notice anything wrong, picked up on this just now) which was likely working the disk a bit. Disk is a 1.2GB Seagate - SEAGATE ST51080N 0943 - the cheap medalist scsi drives they produced a while ago (or was it "hawk"? I dunno..). 5400RPM, SCSI2. Adaptec 2940UW controller. Should I be concerned about this, or was it just a "normal" correctable error. The disk is about 2 years old I think, +/- 6 months. I'd hate to have to replace a disk on that thing now, especially with 3.0 so close (i.e. I'd rather do the downtime all at once - upgrade + new disk!) TIA for any advice as to the fate of my drive! -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark ------------------------------------------------------------------------ "The problem is how do you build tools that understand your programs at a deeper semantic level." - James Gosling To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message