Date: Tue, 16 Jan 1996 13:59:39 +0100 From: se@zpr.uni-koeln.de (Stefan Esser) To: Michael Beckmann <petzi@zit.th-darmstadt.de> Cc: hardware@FreeBSD.org, scsi@FreeBSD.org Subject: Re: Disk or controller or driver failure ? Message-ID: <199601161259.AA00719@Sysiphos> In-Reply-To: Michael Beckmann <petzi@zit.th-darmstadt.de> "Disk or controller or driver failure ?" (Jan 16, 12:58)
next in thread | previous in thread | raw e-mail | index | archive | help
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 <se@ZPR.Uni-Koeln.DE>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199601161259.AA00719>