Dave,
Well, there was a discussion a few weeks back with Soren Schmidt and a few
others. I believe the conclusion was made that this occurred with most WD
drives (interesting about the WD == IBM part, I did notice he mentioned
that in -current a few weeks ago as well). I had a WD20 gig that would
just hang, and a number of other people had similar problems. (Theirs
would log "Lost Disk Contact" in the dmesg as their root dev wasn't a
UDMA66 drive)
Unfortunately, the discussions occurred while the mailing list archive was
kaput (WD Drive on UDMA66? =]) so it's not archived where I can find it.
Seems to only happen with the ata driver, IIRC.
--
Marius Strom <[EMAIL PROTECTED]>
Professional Geek/Unix System Administrator
Alpha1 Internet <http://www.alpha1.net>
http://www.marius.org/marius.pgp 0x42C74CBA *UPDATED PGP KEY 2/24/2000*
In theory, there is no difference between theory and practice...
...In practice, there is a big difference.
On Mon, 6 Mar 2000, Dave Boers wrote:
> It is rumoured that Marius Strom had the courage to say:
> > I'm willing to bet a nickel (perhaps more) you people are running non-IBM
> > UDMA66 drives on that BP6. Seems that most UDMA66 drives are not actually
> > UDMA66 compliant, and they only drives that have been reported successful
> > on the BP6 are IBM. Try taking your HD's off the UDMA66 controller and
> > put them on the Standard UDMA33 controllers, and it should clear things
> > up.
>
> I'm interested in the sources of your statement about IBM drivers vs. non
> IBM drives.
>
> In my case, I have a WD 18.2 Gb 7200 rpm disk which has been reported to be
> identical to the IBM 18.2 Gb 7200 rpm disk on more than one occasion. And
> by the way, my system has been running quite stable before January 2000
> with the same disk on the same controller and the same mainboard.
>
> Regards,
>
> Dave Boers.
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
