[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AADF4E2.9030407@kernel.org>
Date: Mon, 14 Sep 2009 16:46:42 +0900
From: Tejun Heo <tj@...nel.org>
To: tfjellstrom@...w.ca
CC: Chris Webb <chris@...chsys.com>, linux-scsi@...r.kernel.org,
Ric Wheeler <rwheeler@...hat.com>,
Andrei Tanas <andrei@...as.ca>, NeilBrown <neilb@...e.de>,
linux-kernel@...r.kernel.org,
IDE/ATA development list <linux-ide@...r.kernel.org>,
Jeff Garzik <jgarzik@...hat.com>, Mark Lord <mlord@...ox.com>
Subject: Re: MD/RAID time out writing superblock
Hello,
Thomas Fjellstrom wrote:
> I have the same issue with a single WD 2TB Green drive. Technically two, but
> it always only gets errors from the same drive, so I was assuming it was the
> drive. I only have to setup the raid0 array, and put some light load on it for
> the kernel to start complaining, and eventually it just kicks the drive
> completely with the following messages:
>
> sd 3:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET driverbyte=DRIVER_OK
> end_request: I/O error, dev sdb, sector 202026972
>
> The drive does work fine prior to the frozen timeout errors. And I was using
> it in windows (same raid0 config) just fine with no errors what so ever.
Can you post full dmesg output? The above doesn't tell much about ATA
side of things.
Thanks.
--
tejun
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists