Date: Fri, 8 Sep 2000 10:41:36 +0200 (MET DST) From: =?ISO-8859-1?Q?P=E4r_Thoren?= <t98pth@student.hk-r.se> To: Joel Mc Graw <jpmcgraw@home.com> Cc: freebsd-questions@freebsd.org, FreeBSD-questions@freebsd.org Subject: Re: ATA66 troubles under 4.0R vs 3.4 Message-ID: <Pine.GSO.4.21.0009081038180.13106-100000@orc.rby.hk-r.se> In-Reply-To: <39B84AE0.3A37DB86@home.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 7 Sep 2000, Joel Mc Graw wrote: > Greg Lehey wrote: > >=20 > > On Wednesday, 6 September 2000 at 20:35:08 -0500, graphics wrote: > > > After seeing uncountable sudden "drive deaths" on *brand new* > > > drives, we did a little digging (thank god for the archives!) and > > > have noted the many similar tales of woe... > >=20 > > "similar" doesn't mean "the same". What do you mean by "drive > > deaths"? If the drive has really failed, it's very unlikely to be > > connected to FreeBSD. > >=20 > > > Now, since 3.4 reportedly does not suffer from these troubles, we > > > are going to go back down to 3.4, however, we would like the > > > transition to be as painless as humanly possible, so: Can we simply > > > do an overlay of 3.4 onto a 4.0 system? > >=20 > > No. > >=20 > > > Also, is it known whether 4.1 has fixed the 4.0 ATA66 problems? How > > > about 5-stable? > >=20 > > Nobody knows if you don't know. How do you expect us to know what the > > problem is? > >=20 > I think this is an unhelpful answer. I ran into the same problem > upgrading from 3.1 to 4.1r. I noticed that dmesg claimed that the cable > was not DMA66 compliant (it was). After some research, I DID see a lot > of similar complaints (drive dies) with one common thread: they were > Quantum drives. Mine was a Quantum Fireball. Brand new. I went out > and bought a Maxtor, and reinstalled FreeBSD. No problems.=20 > Interestingly enough, I still have the Quantum in the machine, but it's > now the secondary master. >=20 > > If you're running into a real problem with the new ata driver, you can > > build a kernel with the wd driver instead. That's a lot less work > > than reinstalling the system. But I can't decide whether that's the > > case until I see some evidence. >=20 > Obviously, building the kernel with the wd driver would be cheaper than > buying a new drive... >=20 >=20 Hi! I also got problems with the ATA drives. I posted my problem here a couple of days ago. The wd driver in 3.4 worked fine. So I guess I can use them instead. What would be the kernel entry for using the wd driver instead? /P=E4r To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.21.0009081038180.13106-100000>