public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Andrea Conti <alyf@alyf.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Harddisk trouble ... or not yet?
Date: Sat, 29 May 2010 09:25:08 +0200	[thread overview]
Message-ID: <4C00C154.6010208@alyf.net> (raw)
In-Reply-To: <20100528015403.GA5811@solfire>

> ata1.00: failed command: READ DMA
> ata1.00: cmd c8/00:80:00:3f:c1/00:00:00:00:00/e0 tag 0 dma 65536 in
>          res 51/84:4f:00:3f:c1/00:00:00:00:00/e0 Emask 0x10 (ATA bus error)
> ata1.00: status: { DRDY ERR }
> ata1.00: error: { ICRC ABRT }
> ata1: soft resetting link
> ata1.00: configured for UDMA/33
> ata1: EH complete
> ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6

I think you have driver issues. Might also be the cabling, but I doubt
it as faulty SATA cables are in my experience quite rare.

WD drives are known not to get along too well with VIA SATA1 controllers:

http://www.viaarena.com/forums/showthread.php?t=38871
http://forums.gentoo.org/viewtopic-t-794855.html

What kernel version are you using?
What does the kernel say when it first detects the disk?

Do you get the same errors under a recent kernel (try the latest gentoo
install cd) ?

My experience with WD "advanced format" drives has been positive so far,
especially considering how cheap they are... The only gripe I have is
that they report not only having a 512B *logical* sector size in the
response to ATA INFO commands (which is fine, as they have a translation
layer), but also a 512B *physical* sector size, which is wrong and
causes partitioning tools to use the wrong alignment.
All the five 1TB drives I have behave this way, and from what I read
this is not an isolated behavior...

andrea



  parent reply	other threads:[~2010-05-29  8:03 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-26  3:15 [gentoo-user] Harddisk trouble ... or not yet? meino.cramer
2010-05-26  6:38 ` [gentoo-user] howto increase INODE kitti jaisong
2010-05-26  7:09   ` Bert Swart
2010-05-26 11:16   ` Volker Armin Hemmann
2010-05-26 12:55   ` Alex Schuster
2010-05-26 11:17 ` [gentoo-user] Harddisk trouble ... or not yet? Volker Armin Hemmann
2010-05-26 14:22 ` [gentoo-user] " Grant Edwards
2010-05-26 17:09   ` meino.cramer
2010-05-26 17:59     ` Volker Armin Hemmann
2010-05-26 19:05       ` Neil Bothwick
2010-05-26 19:13         ` Volker Armin Hemmann
2010-05-26 20:40           ` Neil Bothwick
2010-05-27  0:19             ` meino.cramer
2010-05-27  1:48               ` walt
2010-05-27  2:43                 ` meino.cramer
2010-05-27  3:52                   ` W.Kenworthy
2010-05-27  4:29                     ` Iain Buchanan
2010-05-27  9:39                   ` Andrea Conti
2010-05-28  1:54                     ` meino.cramer
2010-05-28 23:24                       ` walt
2010-05-29  3:47                         ` meino.cramer
2010-05-29  7:25                       ` Andrea Conti [this message]
2010-05-29  8:16                         ` Volker Armin Hemmann
2010-05-29 19:05                           ` Alan McKinnon
2010-05-29 20:08                             ` Volker Armin Hemmann
2010-05-29  8:56                         ` meino.cramer
2010-05-29 19:13                           ` Andrea Conti
2010-05-27  8:17               ` Stroller

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=4C00C154.6010208@alyf.net \
    --to=alyf@alyf.net \
    --cc=gentoo-user@lists.gentoo.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