All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chr <chunkeey@web.de>
To: Sergey Spiridonov <sena@hurd.homeunix.org>
Cc: Jeff Garzik <jeff@garzik.org>,
	linux-kernel@vger.kernel.org,
	Linux IDE mailing list <linux-ide@vger.kernel.org>
Subject: Re: GA-MA790FX-DS5 SATA ahci NCQ erros on Jmicron 20360/20363  (JMB363) kernel 2.6.25-2 Debian/Lenny
Date: Sun, 24 Aug 2008 01:27:51 +0200	[thread overview]
Message-ID: <200808240127.51972.chunkeey@web.de> (raw)
In-Reply-To: <48B0916C.4080805@garzik.org>

On Sunday 24 August 2008 00:38:36 Jeff Garzik wrote:
> See http://ata.wiki.kernel.org/index.php/Libata_error_messages for an
> introduction.
>
> In general, tons of ATA bus errors and SError register bits means that
> problems are coming from the ATA bus, a.k.a. the SATA cable and its
> related connections.
>
> So...  suspect bad cables, bad port connectors, cable interference,
> motherboard-caused interference or grounding problems, power supply
> problems.
>
hmm, or something totally odd...

what happens if you do: (after you made a backup!)
"dd if=/dev/sdX(where X is your affected hdd?) of=/dev/null bs=1"
Note:
The important bit is the small bs (blocksize) number.
You can throw in a O_DIRECT flag to disable the caches, or 
if you have some "empty" partition space, you can "dd" into
it with a small blocksize too)

my seagate & even a samsung hd103uj doesn't like that and will spew
out the same sort problems you have just posted... (but they work fine,
if I don't do nasty dd things!)

and unfortunatly my md(raid1) seems to do lots of "small" reads & writes
when it starts to check/resync the whole 1TB array :-/.

Regards,
	Chr

  reply	other threads:[~2008-08-23 23:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-23 14:32 GA-MA790FX-DS5 SATA ahci NCQ erros on Jmicron 20360/20363 (JMB363) kernel 2.6.25-2 Debian/Lenny Sergey Spiridonov
2008-08-23 22:38 ` Jeff Garzik
2008-08-23 23:27   ` Chr [this message]
2008-08-24  0:27   ` Sergey Spiridonov
2008-08-24  4:39     ` Jeff Garzik
2008-08-24 23:31       ` Sergey Spiridonov
2008-08-25 14:52         ` xerces8
2008-08-25 14:52           ` xerces8
2008-09-17 12:07         ` Sergey Spiridonov
2008-09-17 12:07           ` Sergey Spiridonov
2008-09-17 15:31           ` Krzysztof Halasa
2008-08-24 16:44     ` xerces8
2008-08-24 16:44       ` xerces8
2008-08-30 11:00       ` Tejun Heo
2008-08-30 18:13         ` xerces8
2008-08-31  9:33           ` Tejun Heo

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=200808240127.51972.chunkeey@web.de \
    --to=chunkeey@web.de \
    --cc=jeff@garzik.org \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sena@hurd.homeunix.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.