> Peter L. Ashford wrote:
> > WD has had problems similar to this with many of their drives. It
> > just decides to 'go away'. There is a fix available on
> their web site
> > for the 180GB and 200GB drives (and a better description of the
> > problem), but the problem is NOT limited to those drives.
>
> How do these problem appear in log files?
-= A server that lost one drive on Sunday, only had this error:
kernel: end_request: I/O error, dev 03:41 (hdb), sector 512
-= Another server that is having this problems, has this in the logs:
May 1 03:01:28 virt10p kernel: end_request: I/O error, dev 16:42 (hdd),
sector 16
May 1 03:01:28 virt10p kernel: hdd: status error: status=0x10 {
SeekComplete }
( repet 10 times)
May 1 03:01:28 virt10p kernel: hdd: status error: status=0x10 {
SeekComplete }
May 1 03:01:28 virt10p kernel: end_request: I/O error, dev 16:42 (hdd),
sector 108736
May 1 04:02:13 virt10p kernel: hdd: status error: status=0x10 {
SeekComplete }
May 1 04:02:13 virt10p kernel: hdd: status error: status=0x10 {
SeekComplete }
>
> I have a machine with two Promise Ultra100 TX2 cards, and
> five WD2000JB 200 GB drives in RAID-5. In a month, i've had a
> few disk "failures" that typically looks like this in the logs:
>
[snip log]
> The disk itself doesn't appear to know about any failures
> (using smartctl), and it works again when hotadded to the
> raidset. I've also had a multiple drive "failure" twice, both
> times with two drives using the same IDE channel.
On the server with the most recent crash, I replaced the drive with a
WD1200JB (it was a WD1200BB), rebuilt the array, then formated the drive
that wasn?t replaced checking it for badblocks, using the slower,
destructive, read-write test (they arnt kidding about the slower part,
took about 24 hours).
Up until Sunday, I could readd the disk to the array, but now the 2nd
hard drive doesn't even show up when doing a fdisk -l
> I'm not sure if these problems are caused by buggy Promise
> ATA drivers in my kernel (RH9, 2.4.20) or the WDC problem
> with 180/200 GB drives. From WDC's description of the
> problem, I got the impression that it only happened when the
> drives were connected to hardware RAID cards like 3Ware IDE
> raid controllers.
I've contacted WD's tech support to see how they can help. When I'm
done with them I'll post the results.
-
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
