linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Potter <bpotter@teamsearchmr.co.uk>
To: linux-admin@vger.kernel.org
Subject: Re: a Maxtor story
Date: Sat, 05 Jun 2004 17:10:30 +0100	[thread overview]
Message-ID: <40C1F076.3090708@teamsearchmr.co.uk> (raw)
In-Reply-To: <20040605101558.GA2638@lists.notified.de>

Unfortunately it is not just the 120Gb Maxtor hard drives - over a 
period of about 12 months I bought 22 Maxtor hard drives, of these 14 
have now failed. Almost exactly the same problem as markus, In my case, 
extreme slowdown - followed by sudden failure.

The majority of these disks were the slimline models (never again!), but 
there was at least one normal(?) sized hard drive. The capacity ranged 
from 30 Gb to 120Gb

Needless to say, after replacing the lot with IBM deskstars, I have not 
had a single disk failure (to date) and will not be buying Maxtor disks 
again.

Thankfully, I also have a highly paranoid backup system - and did not 
lose any data, and am now running the smart daemon tools on all the 
critical machines.

Just my 2 pence
Ben Potter

markus reichelt wrote:

>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.
>
>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.
>  
>



  reply	other threads:[~2004-06-05 16:10 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-03  5:02 Drive Ready seek errors Brandon Evans
2004-06-03  9:54 ` Toby Fisher
2004-06-03  9:59   ` Pau Montero Pares
     [not found]     ` <40BF9824.4090002@hosttuls.com>
2004-06-04 10:09       ` Pau Montero Pares
2004-06-04 13:04         ` Chris DiTrani
2004-06-07 17:45         ` Brandon Evans
2004-06-03 21:24   ` Brandon Evans
2004-06-08 23:29     ` Toby Fisher
2004-06-08 23:30     ` Toby Fisher
2004-06-03 12:30 ` terry white
2004-06-03 21:30   ` Brandon Evans
2004-06-04 10:14     ` Alexander Economou
2004-06-05 10:15     ` a Maxtor story (was: Drive Ready seek errors) markus reichelt
2004-06-05 16:10       ` Ben Potter [this message]
2004-06-05 16:32         ` a Maxtor story DragonK
2004-06-05 16:33           ` Ben Potter
2004-06-07 13:46             ` Yu Chen
2004-06-05 18:26           ` Scott Taylor
2004-06-03 13:04 ` Drive Ready seek errors Miguel González Castaños

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40C1F076.3090708@teamsearchmr.co.uk \
    --to=bpotter@teamsearchmr.co.uk \
    --cc=linux-admin@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).