From owner-freebsd-questions  Thu Apr 17 09:23:09 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.5/8.8.5) id JAA18447
          for questions-outgoing; Thu, 17 Apr 1997 09:23:09 -0700 (PDT)
Received: from who.cdrom.com (who.cdrom.com [204.216.27.3])
          by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA18431
          for <freebsd-questions@freebsd.org>; Thu, 17 Apr 1997 09:23:04 -0700 (PDT)
Received: from nessie.mcc.ac.uk (pp@nessie.mcc.ac.uk [130.88.200.20])
          by who.cdrom.com (8.8.5/8.6.11) with ESMTP id JAA07639
          for <freebsd-questions@freebsd.org>; Thu, 17 Apr 1997 09:22:52 -0700 (PDT)
Received: from albatross.mcc.ac.uk by nessie.mcc.ac.uk with SMTP (PP);
          Thu, 17 Apr 1997 17:05:15 +0100
Received: (from ip@localhost) by albatross.mcc.ac.uk (8.8.5/8.6.12) id RAA04966 
          for freebsd-questions@freebsd.org;
          Thu, 17 Apr 1997 17:00:30 +0100 (BST)
From: Ian Pallfreeman <ip@mcc.ac.uk>
Message-Id: <199704171600.RAA04966@albatross.mcc.ac.uk>
Subject: Re: hard disk CRASH (using 2.2.1)
To: freebsd-questions@freebsd.org
Date: Thu, 17 Apr 1997 17:00:29 +0100 (BST)
Reply-To: ip@mcc.ac.uk
X-Mailer: ELM [version 2.4 PL24]
Content-Type: text
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Doug White wrote:
> On 14 Apr 1997, MARSO, LARRY wrote:
> > On my notebook, after a "from scratch" reinstall that has worked
> > perfectly for days ... the hard drive suddenly seems dead. 
> > 
> > Upon rebooting, it drops into fsck and locks up as follows (same result
> > when I run fsck from the repair floppy): 
> > 
> > Warning: / was not properly dismounted.
> > wd0: interrupt timeout:
> > wd0: status 58<rdy,seekdone,drq> error 0
> > wd0: interrupt timeout
> > wd0: status 50<rdy,seekdone> error 1<no_dam>
> 
> I'vew seen these for both busted disks and systems that have IDE spindown
> enabled.  Try disabling it and see what you get.

This "interrupt timeout" seems to appear sporadically on machines which have
apparently good disks and no spindown...

Is it possible that the drives are remapping, and this causes the timeout?

Ian.
-- 
   "B" Ship, N&O, Manchester Computing, The University, Manchester, England.
     mail: ip@mcc.ac.uk | phone: +44-161-275-6006 | fax: +44-161-275-6040
       ... and you'll tell me what I want, what I really really want ...