From owner-freebsd-scsi Sun Apr 26 23:45:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28090 for freebsd-scsi-outgoing; Sun, 26 Apr 1998 23:45:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from wcc.wcc.net (wcc.wcc.net [208.6.232.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28085 for ; Sun, 26 Apr 1998 23:45:28 -0700 (PDT) (envelope-from piquan@wcc.wcc.net) Received: from detlev.UUCP (newip5.wcc.net [206.104.247.5]) by wcc.wcc.net (8.8.8/8.8.8) with ESMTP id BAA11241; Mon, 27 Apr 1998 01:40:58 -0500 (CDT) Received: (from joelh@localhost) by detlev.UUCP (8.8.8/8.8.8) id BAA00575; Mon, 27 Apr 1998 01:43:37 -0500 (CDT) (envelope-from joelh) Date: Mon, 27 Apr 1998 01:43:37 -0500 (CDT) Message-Id: <199804270643.BAA00575@detlev.UUCP> To: freebsd-scsi@FreeBSD.ORG Subject: FRU reporting From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know SCSI that well, but wouldn't it make sense to report non-zero FRU's in the event of a hardware failure (sense code 4)? I only ask because I'm having to troubleshoot just such a situation now. Happy hacking, joelh PS: Kindly keep me in CC's; I'm not a -scsi regular. -- Joel Ray Holveck - joelh@gnu.org - http://www.wp.com/piquan Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message