From owner-freebsd-questions Fri Jan 26 14: 5:15 2001 Delivered-To: freebsd-questions@freebsd.org Received: from c014.sfo.cp.net (c014-h023.c014.sfo.cp.net [209.228.12.87]) by hub.freebsd.org (Postfix) with SMTP id BEA1437B400 for ; Fri, 26 Jan 2001 14:04:52 -0800 (PST) Received: (cpmta 21436 invoked from network); 26 Jan 2001 14:04:51 -0800 Received: from m12hRs4n205.midsouth.rr.com (HELO mike) (24.95.125.205) by smtp.valuedata.net (209.228.12.87) with SMTP; 26 Jan 2001 14:04:51 -0800 X-Sent: 26 Jan 2001 22:04:51 GMT Message-ID: <006f01c087e4$022bebe0$0200000a@mike> From: "Daryl Chance" To: "Matt White" , , References: <51420000.980546256@sambvca.torrentnet.com> Subject: Re: Maxtor 80GB problems Date: Fri, 26 Jan 2001 16:04:50 -0600 Organization: ValueData, LLC 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.50.4522.1200 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG are you by chance running an AMD? Specifically a Fic MB? Theres a bios fix for the Fic SD11 that fixed some problems I was having. It seems the MB has an issue with Maxtor drives and locks up under heavy disk activity. HTH, - Daryl Chance | And which parallel universe did ValueData, LLC | YOU crawl out of? Memphis, TN | - http://www.thinkgeek.com ----- Original Message ----- From: "Matt White" To: ; Sent: Friday, January 26, 2001 3:57 PM Subject: Maxtor 80GB problems > Hello: > > I recently installed a Maxtor 80GB on a freebsd 4.2-stable box to serve as > a sort of dumping ground for random files. This drive is not very happy. > > During newfs, the kernel complains repeatedly of write timeouts. > Occaisionally, the kernel loses contact with the disk entirely (in those > instances I am forced to give up and restart the system). During a fsck > operation, I get repeated HARD READ errors, along with a prompt as to > whether I want to continue. Of course, it does me no good to continue > because fsck still sees the drive as dirty and thus won't mark it clean. > > I've tried this drive on two different 4.2-stable boxes with different > controllers and cabling. Occaisionally the drive makes unhappy noises. > Under windows the drive appears to be fine, but I haven't really stressed > this beyond the initial format and some time spent in scandisk. Windows is > not amazingly forthcoming about errors. > > I know this isn't the best problem description, but I'm hoping that it will > trigger someone's memory such that they may remember a similar problem. If > I don't get a response, I'll file a formal PR with as much information as I > can gather later. > > Please cc an responses to this email address. > > Thanks in advance. > > > -Matt > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message