Return to BSD News archive
Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!EU.net!sztaki!news
From: pink@fsz.bme.hu (Szabolcs Szigeti (PinkPanther))
Subject: Re: [NetBSD 0.9] patch to wd.c for IDE cont
Message-ID: <CJ7AsA.CHr@sztaki.hu>
Sender: news@sztaki.hu (News system)
Reply-To: pink@fsz.bme.hu
Organization: Department of Process Control, Technical University of Budapest, HUNGARY
References: <1994Jan05.074411.11109@crash>
Date: Thu, 6 Jan 1994 09:09:46 GMT
Lines: 36
In article 11109@crash, fpm@crash.cts.com (Frank MacLachlan) writes:
>In article <explorer.757753457@tbird.cc.iastate.edu> explorer@iastate.edu (Michael Graff) writes:
>
>[ stuff deleted ]
>
>>My roomate has a Connor 350 as wd0 and a Maxtor as wd1. When booting, fscp -p
>>hangs his box.
>
>I think this is common to all of the BSD wd drivers. I got around the
>problem by adding the following to /etc/rc:
>
> dd if=/dev/rwd1c of=/dev/null bs=1k count=1
>
>The important thing is to open and initialize wd1 before the fsck -p
>is performed.
>
>--
>UUCP: {hplabs!hp-sdd ucsd nosc}!crash!fpm
>INET: fpm@crash.cts.com
I had the same problems with a 125 Meg Seagate and a 340 Meg WD. It seem to me
that when the wd driver tries to read the disklabel on both disks it hangs.
( Any connection to the wdc0: extra interrupt when reading label?)
The temporary solution is not to let fsck check the disks simultaneously, and
wait long :-(.
This can be set by the last parameter in fstab.
---
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
|You're damned if you do, | Szabolcs Szigeti |
|You're damned if you don't -- Bart -- | Internet: pink@fsz.bme.hu |
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=