From owner-freebsd-questions  Mon Aug 18 21:39:52 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id VAA09042
          for questions-outgoing; Mon, 18 Aug 1997 21:39:52 -0700 (PDT)
Received: from gdi.uoregon.edu (cisco-ts13-line12.uoregon.edu [128.223.150.161])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA09029
          for <freebsd-questions@FreeBSD.ORG>; Mon, 18 Aug 1997 21:39:45 -0700 (PDT)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id VAA02560;
          Mon, 18 Aug 1997 21:39:40 -0700 (PDT)
Date: Mon, 18 Aug 1997 21:39:40 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
X-Sender: dwhite@localhost
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Anne Voice <anne@theta.dyn.ml.org>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Disk problems
In-Reply-To: <33F78665.167EB0E7@theta.dyn.ml.org>
Message-ID: <Pine.BSF.3.96.970818213758.2488I-100000@localhost>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 17 Aug 1997, Anne Voice wrote:

> I am using FreeBSD 2.2.2 on a Pentium 133 machine with 32 meg ram and 2
> 2.5 gig Western Digital IDE hard drives.  I have Windows NT Workstation
> 4.0 on the first drive (wd0) and FreeBSD on the second (wd1).  
> 
> Occasionally, when I attempt use ls, finger, uptime and other commands I
> get the following in the message log.  I also get, in white text, a
> message similar to the below (I wasn't in X and didn't know a way to
> save it).  The system locks up for about 30 seconds when this happens
> (ie. alt-F2 won't switch terminals, nor will any commands work). 
> 
> Is this a problem with my drive or some kind of misconfiguration?  If a
> misconfiguration, what can I do about it?

It looks like something is wrong with your IDE controller or your second
IDE disk.  You might check that nothing is using IRQ 14 or 15.  Also check
your cabling; your IDE cable may be slightly pulled out, or you have a
dead or dying disk. 

The lockup is a result of the system blocking on the disk read.
Eventually all the requests die and the system can continue to respond.

> Aug 17 15:58:35 theta /kernel: wd1: status 58<rdy,seekdone,drq> error 0
> Aug 17 15:58:35 theta /kernel: wd1: wdunwedge failed: 
> Aug 17 15:58:35 theta /kernel: wd1: status d0<busy,rdy,seekdone> error 
> 1<no_dam>
> Aug 17 15:58:35 theta /kernel: wd1s1f: wdstart: timeout waiting to give
> command$
> Aug 17 15:58:35 theta /kernel: wd1: wdunwedge failed:
> Aug 17 15:58:35 theta /kernel: wd1: status d0<busy,rdy,seekdone> error
> 1<no_dam>
> Aug 17 15:58:35 theta /kernel: wd1s1f: wdstart: timeout waiting to give
> command writing fsbn 3604752 of 3604752-3604767 (wd1s1 bn 3883264; cn
> 3852 tn 7 sn 7)wd1: status d0<busy,rdy,seekdone> error 1<no_dam>
> Aug 17 15:58:36 theta /kernel: wd1: wdunwedge failed:
> Aug 17 15:58:36 theta /kernel: wd1: status d0<busy,rdy,seekdone> error
> 1<no_dam>
> Aug 17 15:58:36 theta /kernel: wd1s1f: wdstart: timeout waiting to give
> command writing fsbn 3604752 of 3604752-3604767 (wd1s1 bn 3883264; cn
> 3852 tn 7 sn 7)wd1: status d0<busy,rdy,seekdone> error 1<no_dam>
> 

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major
Spam routed to /dev/null by Procmail    | Death to Cyberpromo