All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Stark <gsstark@mit.edu>
To: Eric Mudama <edmudama@gmail.com>
Cc: Greg Stark <gsstark@mit.edu>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	Brad Campbell <brad@wasp.net.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Jeff Garzik <jgarzik@pobox.com>
Subject: Re: Crashed Drive, libata wedges when trying to recover data
Date: 03 Sep 2004 13:35:08 -0400	[thread overview]
Message-ID: <87pt53s1bn.fsf@stark.xeocode.com> (raw)
In-Reply-To: <311601c904090310083d057c25@mail.gmail.com>


Eric Mudama <edmudama@gmail.com> writes:

> Today's (and tomorrow's) generation of SATA drives will never ever
> generate a 0x59 status... the error and DRQ bits become mutually
> exclusive.  

This is a very recent Maxtor drive, a 7Y250M0. It's not the new drives that
were recently announced but I think it's the most recent you can find in
stores.

-- 
greg


  reply	other threads:[~2004-09-03 17:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-02  8:32 Crashed Drive, libata wedges when trying to recover data Greg Stark
2004-09-02  9:05 ` Brad Campbell
2004-09-03  4:52   ` Greg Stark
2004-09-03  5:13     ` Greg Stark
2004-09-03 11:08     ` Alan Cox
2004-09-03 14:27       ` Greg Stark
2004-09-03 13:53         ` Alan Cox
2004-09-03 15:58           ` Greg Stark
2004-09-03 15:09             ` Alan Cox
2004-09-03 16:47               ` Greg Stark
2004-09-03 17:08                 ` Eric Mudama
2004-09-03 17:35                   ` Greg Stark [this message]
2004-09-03 17:57                   ` Greg Stark
2004-09-03 19:45                     ` Brad Campbell
2004-09-04  0:10                     ` Eric Mudama
2004-09-03 12:51     ` Brad Campbell
2004-09-03 14:09       ` Alan Cox
2004-09-04 21:58         ` Greg Stark
2004-09-05  4:02           ` Brad Campbell

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=87pt53s1bn.fsf@stark.xeocode.com \
    --to=gsstark@mit.edu \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=brad@wasp.net.au \
    --cc=edmudama@gmail.com \
    --cc=jgarzik@pobox.com \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.