[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: 2.6.8-12-amd64-k8 raid1 freezes with spurious interrupts



Hello,

> Do you have "RAID edition" or "normal" hard drives?
> Some "normal" hard drives can carry out lenghty test and/or repair
> procedures themselves and be unresposive in that time.
> RAID controller or software may get confused and handle the
> drive as faulty.

just: normal ;-(

> Check the SMART settings, status (error counts, reallocated sector
> count etc.) and error log on the drives.

unfortunaly it does not work properly, any ideas:

# smartctl -i -d ata /dev/sda -T permissive
smartctl version 5.32 Copyright (C) 2002-4 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Smartctl: Device Read Identity Failed (not an ATA/ATAPI device)

=== START OF INFORMATION SECTION ===
Device Model:     [No Information Found]
Serial Number:    [No Information Found]
Firmware Version: [No Information Found]
Device is:        Not in smartctl database [for details use: -P showall]
ATA Version is:   1
ATA Standard is:  Exact ATA specification draft version not indicated
Local Time is:    Wed Aug  9 12:01:18 2006 CEST
SMART is only available in ATA Version 3 Revision 3 or greater.
We will try to proceed in spite of this.
SMART support is: Ambiguous - ATA IDENTIFY DEVICE words 82-83 don't show if 
SMART supported.
A mandatory SMART command failed: exiting. To continue, add one or more '-T 
permissive' options.

> ATA communication errors also produce time-outs.
> Sometimes, it simply seems that distinct controllers do not like
> distinct hard drives.

this might be the problem as I got the following errors on the console:

ata2: command 0x35 timeout, stat 0xd0 host_stat 0x1
scsi1: Error on Channel0, id0, lan0, CDB: Write (10)
Current sdb: sense Key Medium Error
Additional sense: Write Error - auto reallocation failed
end_request: I/O error, dev sdb, sector 19687
ATA: abnormal status 0xD0 on port 0x977

> PS: I assume that the old story of A-Open mainboards trashing
> WD (and apparently only WD) hard drives after 2-3 months of
> usage is well known.

I hope not to have tha constellation, as my components/setup are:

- mobo: Asus A8N-SLI
- 2 harddrives: Samsung 300 GB, S-ATA2 (Mod.Nr.: HD300LJ )
- kernel: 2.6.8-12-amd64-k8
- raid1: sda and sdb
- 3 partitions on each disk: "/", "/home", "swap"

Any further ideas, than changing harddisks and building new raid!
Harm-?



Reply to: