From owner-freebsd-questions Wed Sep 6 18:42: 6 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cliff.mfn.org (cliff.mfn.org [204.238.179.8]) by hub.freebsd.org (Postfix) with ESMTP id B57CE37B423 for ; Wed, 6 Sep 2000 18:41:59 -0700 (PDT) X-Message1: Missouri FreeNet does not relay. If this email X-Message2: is unsolicited bulk or commercial, please report X-Message3: this abuse promptly to abuse@mfn.org. Thank You. X-ORIGINIP: 128.242.145.201 X-ORIGINDNS: imaging.mfn.org Received: from imaging (imaging.mfn.org [128.242.145.201]) by cliff.mfn.org (8.9.3/8.8.7) with SMTP id VAA22470 for ; Wed, 6 Sep 2000 21:43:49 -0500 (CDT) (envelope-from lart@mfn.org) Posted-Date: Wed, 6 Sep 2000 21:43:49 -0500 (CDT) X-CUTMARK: --------------- Message-ID: <0ad401c0186b$ddaddc20$c991f280@mfn.org> From: "graphics" To: Subject: ATA66 troubles under 4.0R vs 3.4 Date: Wed, 6 Sep 2000 20:35:08 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello, 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... 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? Also, is it known whether 4.1 has fixed the 4.0 ATA66 problems? How about 5-stable? Thanks in advance! (P.S. we are not subscribed, so please include us directly in any replies. Thanks again!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message