Date: Sun, 17 Aug 1997 19:16:53 -0400 From: Anne Voice <anne@theta.dyn.ml.org> To: freebsd-questions@freebsd.org Subject: Disk problems Message-ID: <33F78665.167EB0E7@theta.dyn.ml.org>
next in thread | raw e-mail | index | archive | help
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? >From /var/log/messages: 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>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?33F78665.167EB0E7>