linux-admin.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brandon Evans <maillists@hosttuls.com>
To: terry white <twhite@aniota.com>
Cc: linux-admin <linux-admin@vger.kernel.org>
Subject: Re: Drive Ready seek errors
Date: Thu, 03 Jun 2004 14:30:41 -0700	[thread overview]
Message-ID: <40BF9881.7010402@hosttuls.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0406030528250.16000@yossarian.aniota.net>

terry white wrote:
> on "6-2-2004" "Brandon Evans" writ:
> 
> : Lately, a lot of my Linux boxes have had hard drive failures.
> 
> ... ciao:
> 
>     in the not too distant past, word of 'faulty' 20 and 40GB drives
> surfaced.  'maxtor' was one of the names mentioned, but was not alone in
> this issue ...
> 
> 

These are all 120 Gig hardrives, some Seagate, some Maxtor, and some 
western digital,
So I do not think it is any one manufacturer at fault.


-- 
Thanks,
     Brandon E.

  reply	other threads:[~2004-06-03 21:30 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 [this message]
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       ` a Maxtor story Ben Potter
2004-06-05 16:32         ` 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=40BF9881.7010402@hosttuls.com \
    --to=maillists@hosttuls.com \
    --cc=linux-admin@vger.kernel.org \
    --cc=twhite@aniota.com \
    /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).