All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Peter" <sw98234@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: wrt: dma_intr: status=0x51 { DriveReady SeekComplete Error }
Date: Sun, 27 Aug 2006 10:49:19 +0000 (UTC)	[thread overview]
Message-ID: <ecrtbf$ocr$1@sea.gmane.org> (raw)
In-Reply-To: 20060827071131.GC6932@bitwizard.nl

On Sun, 27 Aug 2006 09:11:31 +0200, Rogier Wolff wrote:

> On Sat, Aug 26, 2006 at 04:12:52PM +0000, Peter wrote:
>> Diagnostics on the drives are fine. Removing the b drive removes the
>> messages. System functions fine anyway, and no data is lost as a result
>> of the errors. The persistence of it is frustrating!
> 
> What diagnostics did you try? 
> 
First badblocks, then Manufacturer's (Maxtor) overnight burn in tests.

> (I've got experience with a guy saying: "I have 5 which test perfect
> with my diagnostics, but my embedded machine refuses them. What's
> wrong?" All of them report through SMART that they HAVE reported media
> errors, and they all have bad blocks.)

I tried to be more careful before posting here :). I even ran a second
test on the drives on a second machine.
> 
> Do you have "smartd" running? I vaguely remember that it sometimes
> triggered error messages from the normal driver.
> 
No, but I think there is a driver issue such as VMW or the reiserfs.
Reiser even mentions this error on his faq suggesting it's a bad ide
cable. Of course, I changed mine (now testing #4). Of course, switching to
NO preempt has reduced the volume of errors greatly. Even last night
there were none for the time being.

thx.

-- 
Peter
+++++
Do not reply to this email, it is a spam trap and not monitored.
I can be reached via this list, or via 
jabber: pete4abw at jabber.org
ICQ: 73676357


  reply	other threads:[~2006-08-27 10:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-26 16:12 wrt: dma_intr: status=0x51 { DriveReady SeekComplete Error } Peter
2006-08-26 17:41 ` Peter
2006-08-26 22:46 ` Alan Cox
2006-08-27  7:11 ` Rogier Wolff
2006-08-27 10:49   ` Peter [this message]
2006-08-27 17:44 ` RESOLVED: " Peter

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='ecrtbf$ocr$1@sea.gmane.org' \
    --to=sw98234@hotmail.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.