Hi list!
I have the following configuration:
4x WD5000YS (Caviar RE2 500 GB) on the SATA ports of an Intel
SE7230NH1-E. The controller is an ICH7R in AHCI mode. Kernel is
2.6.17-1-686 from Debian testing. No jumpers on the drives, which
should be PM2 (whatever that is) off and 300Gb/s mode. The RE series
has special firmware with reduced error correction timeouts --
supposedly the RAID controller (libata and/or Linux Software-RAID in
my case) should take care of errors anyway.
All drives pass the advanced test of WD's diagnostic tool
individually, however when I tried to create an md array I got
something like this:
[...]
ata2: port reset, p_is 8000000 is 2 pis 0 cmd 44017 tf d0 ss 123 se 0
ata2: status=0x50 { DriveReady SeekComplete }
sdc: Current: sense key: No Sense
Additional sense: No additional sense information
ata2: handling error/timeout
ata2: port reset, p_is 0 is 0 pis 0 cmd 44017 tf 150 ss 123 se 0
ata2: status=0x50 { DriveReady SeekComplete }
ata2: error=0x01 { AddrMarkNotFound }
sdc: Current: sense key: No Sense
Additional sense: No additional sense information
[repeat]
Those messages loop until a timeout of some sort (a few minutes) is
reached. During that time all current and new processes accessing the
disk hang, but the md layer does not fail the disk at any time. The
other disks in the array stay accessible.
After a few reboots with cable-wiggling in between it created the
array without complaining. I then tested and benchmarked it for well
over a day, and when I'd finally declared it stable and copied some
data over it threw the same errors again :(
- It's not the disks themselves
- It's might be the cables, even though the diagnostic is fine,
especially if it forces 150 Gb/s. Also the error is (always? not sure)
on ata2. I don't have enough cables to test, unfortunately.
- It might be md, though the md guru (Neil Brown) says it is not.
- It might be the libata driver.
I appreciate any help,
Christian
-
: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
