Current-Users archive

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

Re: WDCTL_RST failed



On 11 September 2013 19:01, Manuel Bouyer <bouyer%antioche.eu.org@localhost> 
wrote:
> On Wed, Sep 11, 2013 at 06:32:29PM +0100, Patrick Welche wrote:
>> Dying disk or ahcisata quirk?
>>
>> Just odd that the failing reset happens first, then the timeout.
>
> I guess it's because the ahci driver reports a timeout to the upper level
> (which is basically that: we waited for WDCTL_RST to clear and
> it didn't clear).
>
> It's either a dying disk or a cabling issue.

I've got similar messages on my latest NetBSD box:

--
Sep 11 03:22:55 uksup1 /netbsd: pdcsata0:1:0: lost interrupt
Sep 11 03:22:55 uksup1 /netbsd:         type: ata tc_bcount: 16384 tc_skip: 0
Sep 11 03:24:26 uksup1 /netbsd: pdcsata0:0:0: lost interrupt
Sep 11 03:24:26 uksup1 /netbsd:         type: ata tc_bcount: 49152 tc_skip: 0
Sep 11 03:24:26 uksup1 /netbsd: pdcsata0:0:0: device timeout,
c_bcount=49152, c_skip0
Sep 11 03:24:26 uksup1 /netbsd: wd4a: device timeout reading fsbn
55132608 of 55132608-55132703 (wd4 bn 55132671; cn 54695 tn 1 sn 48),
retrying
Sep 11 03:24:36 uksup1 /netbsd: pdcsata0:0:0: lost interrupt
Sep 11 03:24:36 uksup1 /netbsd:         type: ata tc_bcount: 49152 tc_skip: 0
Sep 11 03:24:36 uksup1 /netbsd: wd4: soft error (corrected)
Sep 11 03:25:28 uksup1 /netbsd: pdcsata0:1:0: lost interrupt
Sep 11 03:25:38 uksup1 /netbsd:         type: ata tc_bcount: 49152 tc_skip: 0
Sep 11 03:25:38 uksup1 /netbsd: pdcsata0:1:0: device timeout,
c_bcount=49152, c_skip0
Sep 11 03:25:38 uksup1 /netbsd: wd5a: device timeout reading fsbn
58539232 of 58539232-58539327 (wd5 bn 58539295; cn 58074 tn 11 sn 10),
retrying
Sep 11 03:25:38 uksup1 /netbsd: pdcsata0:1:0: lost interrupt
Sep 11 03:25:38 uksup1 /netbsd:         type: ata tc_bcount: 49152 tc_skip: 0
Sep 11 03:25:38 uksup1 /netbsd: wd5: soft error (corrected)
---

wd4 and wd5 are members of a root RAID1 array, they always appear
together for wd4 and wd5, so it is not very likely to be a dying disk.
Cabling issue is possible, though. It doesn't seem to cause any
problem to the system so far.



>
> --
> Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>      NetBSD: 26 ans d'experience feront toujours la difference
> --

Chavdar



-- 
----


Home | Main Index | Thread Index | Old Index