Hello, sorry about the long delay.
Eyal Lebedinsky wrote:
BTW, this is SMART read log for page 09 which is SMART self-test log.
The device aborted it. Dunno who issued it or why it got aborted. As I
wrote in the previous mail, EH discovered that SError has accumulated
link level errors and
Eyal Lebedinsky wrote:
It is in the original thread on linux-raid, but here it is for this list.
This is the full dmesg. There were only MARKs in between.
I run a raid 'check' every Friday (cron). The last one reported some parity
errors.
*** last week check start:
[927080.617744] md:
Eyal Lebedinsky wrote:
I CC'ed linux-ide to see if they think the reported error was really innocent:
Question: does this error report suggest that a disk could be corrupted?
This SATA disk is part of an md raid and no error was reported by md.
[937567.332751] ata3.00: exception Emask
Tejun Heo wrote:
Eyal Lebedinsky wrote:
I CC'ed linux-ide to see if they think the reported error was really innocent:
Question: does this error report suggest that a disk could be corrupted?
This SATA disk is part of an md raid and no error was reported by md.
[937567.332751] ata3.00:
I CC'ed linux-ide to see if they think the reported error was really innocent:
Question: does this error report suggest that a disk could be corrupted?
This SATA disk is part of an md raid and no error was reported by md.
[937567.332751] ata3.00: exception Emask 0x10 SAct 0x0 SErr 0x4190002
