From: "Johan Schön" <johan.schon@visiarc.com>
To: "Peter L. Ashford" <ashford@sdsc.edu>
Cc: linux-raid@vger.kernel.org
Subject: Re: Disks keep disapearing
Date: Sat, 10 May 2003 18:47:40 +0200 [thread overview]
Message-ID: <3EBD2D2C.1050900@visiarc.com> (raw)
In-Reply-To: <Pine.GSO.4.30.0305091654350.23888-100000@multivac.sdsc.edu>
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?
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:
|hdg: dma_intr: status=0x63 { DriveReady DeviceFault Index Error }
|hdg: dma_intr: error=0x04 { DriveStatusError }
|hdg: DMA disabled
|hdh: DMA disabled
|PDC202XX: Secondary channel reset.
|ide3: reset: success
|hdg: irq timeout: status=0xd2 { Busy }
|
|PDC202XX: Secondary channel reset.
|ide3: reset: success
|hdg: irq timeout: status=0xd2 { Busy }
|
|end_request: I/O error, dev 22:00 (hdg), sector 280277504
|raid5: Disk failure on hdg, disabling device. Operation continuing on 4 devices
|hdg: status timeout: status=0xd2 { Busy }
|
|PDC202XX: Secondary channel reset.
|hdg: drive not ready for command
|md: updating md0 RAID superblock on device
|md: hdh [events: 00000007]<6>(write) hdh's sb offset: 195360896
|md: recovery thread got woken up ...
|md0: no spare disk to reconstruct array! -- continuing in degraded mode
|ide3: reset: success
|md: (skipping faulty hdg )
|md: hdf [events: 00000007]<6>(write) hdf's sb offset: 195360896
|md: hde [events: 00000007]<6>(write) hde's sb offset: 195360896
|md: hdb [events: 00000007]<6>(write) hdb's sb offset: 195360896
|hdg: irq timeout: status=0xd2 { Busy }
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.
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.
Can anyone advise?
// Johan
--
Johan Schön www.visiarc.com
VISIARC AB Cell: +46-708-343002
-
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
next prev parent reply other threads:[~2003-05-10 16:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 18:53 Disks keep disapearing brandon
2003-05-10 0:03 ` Peter L. Ashford
2003-05-10 16:47 ` Johan Schön [this message]
2003-05-10 17:01 ` Mads Peter Bach
2003-05-11 4:09 ` Peter L. Ashford
2003-05-12 17:31 ` Brandon Belshaw
2003-05-12 17:49 ` A.J.Dawson
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=3EBD2D2C.1050900@visiarc.com \
--to=johan.schon@visiarc.com \
--cc=ashford@sdsc.edu \
--cc=linux-raid@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.