From owner-freebsd-hardware Tue Jan 16 08:24:20 1996 Return-Path: owner-hardware Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23505 for hardware-outgoing; Tue, 16 Jan 1996 08:24:20 -0800 (PST) Received: from who.cdrom.com (who.cdrom.com [192.216.222.3]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA23449 Tue, 16 Jan 1996 08:24:08 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by who.cdrom.com (8.6.12/8.6.11) with SMTP id EAA25637 ; Tue, 16 Jan 1996 04:59:50 -0800 Received: by Sysiphos id AA00719 (5.67b/IDA-1.5); Tue, 16 Jan 1996 13:59:40 +0100 Message-Id: <199601161259.AA00719@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Tue, 16 Jan 1996 13:59:39 +0100 In-Reply-To: Michael Beckmann "Disk or controller or driver failure ?" (Jan 16, 12:58) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Michael Beckmann Subject: Re: Disk or controller or driver failure ? Cc: hardware@FreeBSD.org, scsi@FreeBSD.org Sender: owner-hardware@FreeBSD.org Precedence: bulk On Jan 16, 12:58, Michael Beckmann wrote: } Subject: Disk or controller or driver failure ? } Hi, } } today I found the hard disk in one of my systems spun down. I got lots } of error messages on the console, and after a while the system } rebooted. This is what I read on the console before it rebooted: } } sd0(ncr0:0:0): NOT READY asc:4.2 } } There was a similar problem this morning, which was logged in } /var/log/messages (I wasn't there): } } Jan 16 04:08:55 zit1 /kernel: sd0(ncr0:0:0): Deferred Error: HARDWARE } FAILURE info:50eb0 asc:15,0 Random } positioning error field replaceable unit: 1 sks:80,3 } } Jan 16 04:09:10 zit1 /kernel: sd0(ncr0:0:0): Deferred Error: HARDWARE } FAILURE info:50eb6 asc:15,0 Random } positioning error field replaceable unit: 1 sks:80,3 [ ... ] } Are these signs of a dying disk or is it the controller ? Or might it be } a driver problem ? Has anyone seen this before ? Well, I'd take those messages to mean what they say: HARDWARE FAILURE: Random positioning error. This is an extended error code, returned by the hard disk, and printed by the generic SCSI code. Make backups ! Regards, STefan PS: You may want to check the power supply, too. This could be caused by an out of spec 12V supply ... -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se