Date: Mon, 28 Jul 2003 10:32:22 -0600 From: "Justin T. Gibbs" <gibbs@scsiguy.com> To: "Marc G. Fournier" <scrappy@hub.org>, freebsd-stable@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: Re: Dump Card State Begins ... Message-ID: <834690000.1059409942@aslan.btc.adaptec.com> In-Reply-To: <20030726115857.M37284@hub.org> References: <20030726115857.M37284@hub.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi ...
>
> Can someone tell me whether or not this is indicative of a hardware, or
> software, problem? It happened a few times today, on two different
> drives, and it seem to "self-recover", since the server is still purring
> along without any noticeable problems:
>
> neptune# grep "timed out" /var/log/messages
> Jul 25 03:52:51 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x40 - timed out
> Jul 25 03:57:22 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x18 - timed out
> Jul 25 03:58:53 neptune /kernel: (da1:ahd1:0:1:0): SCB 0x1e - timed out
> Jul 26 10:55:46 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x39 - timed out
>
> The drives are all U320 Seagate Cheetah 70G ... no RAID involved, its
> just straight drives using the motherboard's onboard SCSI controller ...
> the motherboard is the Intel SE7501, in the SR2300 chassis ...
I need the exact model number and firmware for these drives. There are
at least three different Cheetah 70G U320 drives.
>
> It did it back on the 19th as well:
>
> Jul 19 19:37:16 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x46 - timed out
> Jul 19 19:38:46 neptune /kernel: (da1:ahd1:0:1:0): SCB 0x2d - timed out
>
> But again, appears to have recovered with no ill effects ...
>
>
> Jul 25 03:52:51 neptune /kernel: (da2:ahd1:0:2:0): SCB 0x40 - timed out
> Jul 25 03:53:06 neptune /kernel: >>>>>>>>>>>>>>>>>> Dump Card State Begins <<<<<<<<<<<<<<<<<
The Dump Card state output is much easier to parse if you enable register
pretty printing. From GENERIC:
options AHD_REG_PRETTY_PRINT # Print register bitfields in debug
# output. Adds ~215k to driver.
>From what I can tell here, your drives are sitting on some commands instead
of completing them. This was one of the problems in early revisions of
Seagate's U320 drive firmware. Without knowing more details of the system
though, I can't comment definitively.
--
Justin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?834690000.1059409942>