From owner-freebsd-scsi Thu Dec 17 20:38:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA15166 for freebsd-scsi-outgoing; Thu, 17 Dec 1998 20:38:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA15159 for ; Thu, 17 Dec 1998 20:38:45 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA78249; Thu, 17 Dec 1998 21:38:22 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812180438.VAA78249@panzer.plutotech.com> Subject: Re: Is this error as important as it looks: HARDWARE FAILURE asc:44,0 In-Reply-To: <006f01be2a3c$bbd056b0$f1effccd@bug.tasam.com> from Joe Gleason at "Dec 17, 98 11:13:12 pm" To: clash@tasam.com (Joe Gleason) Date: Thu, 17 Dec 1998 21:38:22 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joe Gleason wrote... > I recently got this in my security check output log: > > > Direct Access SCSI3 device > > (da0:ahc1:0:5:0): WRITE(06). CDB: a 0 0 7f 10 0 > > (da0:ahc1:0:5:0): HARDWARE FAILURE asc:44,0 > > (da0:ahc1:0:5:0): Internal target failure field replaceable unit: 1 > > Is is something I should worry about? In general, yes, you should worry about it. I would keep a close eye on the drive. Look for any more error messages. If you keep getting error messages, you may want to call IBM and inquire about it. They may be able to tell you what part of the drive "field replaceable unit 1" is. If they would put their manuals on their web site like Quantum and Seagate, you might be able to find out for yourself. > Here is the relavent part of my dmesg: > > ahc0 rev 4 int a irq 12 on pci0:20:0 > ahc0: aic7895 Wide Channel A, SCSI Id=7, 32/255 SCBs > ahc1 rev 4 int b irq 11 on pci0:20:1 > ahc1: aic7895 Wide Channel B, SCSI Id=7, 32/255 SCBs > > Sending WDTR! > (probe20:ahc1:0:5:0): Sending SDTR!! > da0 at ahc1 bus 0 target 5 lun 0 > da0: Fixed Direct Access SCSI3 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) > > I just have the one scsi device. You might want to check and see if it is running too hot. Here's a script that might do that, depending on whether your firmware supports it. (I've tried it on the 18G version of that drive, with firmware version 03B0, and it works fine.) ======================================== #!/bin/ksh TEMPC=`camcontrol cmd -n da -u 1 -c "4D 0 76 0 0 0 0 0 20 0" -i 32 "s9 i1"` TEMPF=`echo " 2 k $TEMPC 9 * 5 / 32 + p" | dc` echo "The temperature is: $TEMPF F" ======================================== I think the default temperature threshold (before it starts spewing errors) is 60C. Ideally, though, you'll want to run a good bit cooler than that. You'll need to change the '-u 1' above to '-u 0' for your drive. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message