From mboxrd@z Thu Jan 1 00:00:00 1970 From: markus reichelt Subject: Re: a Maxtor story (was: Drive Ready seek errors) Date: Sat, 5 Jun 2004 12:15:58 +0200 Sender: linux-admin-owner@vger.kernel.org Message-ID: <20040605101558.GA2638@lists.notified.de> References: <40BEB0E7.306@hosttuls.com> <40BF9881.7010402@hosttuls.com> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <40BF9881.7010402@hosttuls.com> List-Id: Content-Type: text/plain; charset="us-ascii"; x-action="pgp-signed" Content-Transfer-Encoding: 7bit To: linux-admin@vger.kernel.org -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brandon Evans wrote: > These are all 120 Gig hardrives, some Seagate, some Maxtor, and some > western digital, I've had nothing but trouble with Maxtor's Diamond Plus series. A few months ago I bought 3 120Gig drives and set up a linux box which worked like a charm. One day I noticed that a partition located within the 30-40% of cylinders of one drive was giving bad data read results, about 1-2 MB/s[1]. So I ran a full fsck which took a long time but worked out fine. Over time, the other drives showed exactly the same symptoms. Since areas where bad data read results appeared were spreading I first used the smart daemon tools to check if the drives were failing. I haven't got the logs anymore but it was suggested to run a full diagnostic. So I did with Maxtor's PowerMAX utility. I got the diagnostic code de699c79 along with a message that the hard drive is failing. At first the code was not accepted at Maxtor's online warranty site located at http://www.maxtor.com/de/support/service/warranty_ata.htm (it is by now, btw) so I contacted the support. It was suggested to low level format the drive and I did as suggested but running PowerMAX afterwards still gave the same diagnostic code. In the end no data was lost (due to a paranoid backup strategy) and all Maxtor drives were replaced by WD ones. For me, buying Maxtor drives is considered A Bad Thing. [1] I used the same partition layout for all 3 drives (with ext3 fs), no RAID whatsoever, so it was easy to track and locate the problem. FWIW, the server is/was used for several large MySQL databases and raw analytical data of some spectrometers. - -- Bastard Administrator in $hell -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFAwZ1eLMyTO8Kj/uQRAnXHAJ445wNrrzimKcwynyYizKIeAbS8zQCeJvx5 tCznuYNm70bZlD0lu9THRT0= =eyo3 -----END PGP SIGNATURE-----