From owner-freebsd-questions Fri Jan 26 14:29:30 2001 Delivered-To: freebsd-questions@freebsd.org Received: from bacardi.torrentnet.com (bacardi.torrentnet.com [198.78.51.104]) by hub.freebsd.org (Postfix) with ESMTP id 4CAD137B402; Fri, 26 Jan 2001 14:29:07 -0800 (PST) Received: from sambvca.torrentnet.com (sambvca.torrentnet.com [4.21.152.12]) by bacardi.torrentnet.com (8.10.2/8.10.2) with ESMTP id f0QMT2M29765; Fri, 26 Jan 2001 17:29:02 -0500 (EST) Date: Fri, 26 Jan 2001 17:29:52 -0500 From: Matt White To: Matt White Cc: hardware@freebsd.org, questions@freebsd.org Subject: RE: Maxtor 80GB problems Message-ID: <62990000.980548192@sambvca.torrentnet.com> In-Reply-To: X-Mailer: Mulberry/2.0.6b1 (Linux/x86) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Actually, Windows appears happy. The only thing about windows is that I am unsure how much noise Windows would make if it actually were unhappy. For those who asked, the motherboard is an Intel pr440fx ppro motherboard. The other motherboad that I tested with is "some p3 motherboard in a micron case". I really didn't look too closely at what it was. dmesg reports the controller as a PIIX4. I believe the pr440fx uses a PIIX3, but Intel's support site is down, so I can't check. -Matt --On Friday, January 26, 2001 14:06:21 -0800 Hodge Podge wrote: > > Sounds like a bad drive to me. Can any OS read/write to it sucessfully? > If FreeBSD And Windows seem unhappy... I woudl exchange it. > > Nicole > > > On 26-Jan-01 Matt White wrote: >> 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-hardware" in the body of the message > > nicole@unixgirl.com |\ __ /| (`\ http://www.unixgirl.com/ > webmistress@dangermouse.org | o_o |__ ) ) http://www.dangermouse.org/ > nicole@deviantimages.com // \\ > http://www.deviantimages.com/ > > ---------------------------(((---(((------------------------------------- > --- > > -- Powered by Coka-Cola and FreeBSD -- > -- I don't speak for anybody but myself - that's enough trouble -- > -- Back Up My Hard Drive? I Can't Find The Reverse Switch! -- > - One Nation Under Fraud Singing Hail to the Thief - > > ------------------------------------------------------------------------- > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message