I assume those ATA numbers correspond to your WD drives...?
If so, I often get the same flavour of error messages from a system running WD Greens in RAID despite smart and badblocks not reporting any errors. From reading up on it this seems to be a quirk of some firmwares on WD drives (probably the more desktop-oriented ones, IIRC I've not seen it from any of my WD reds), as I've never seen the error on any of my hitachi or toshiba drives (or any SSDs for that matter) and the only time I've had it in conjunction with an array failure has been with a) a dodgy cable connection and b) a dodgy JMicron SATA controller.
Personally I wouldn't worry too much about it as I've assigned it to the "almost certainly a red herring" bucket as I've never been able to attribute it to a failure - but then I assume you have at least one backup that you've actually tested, and that you know not to trust advice from randoms on the internet...
Edited to add - I assume you've already checked the smart attrs and you're not seeing any corresponding rise in drive error counts? Here's what one of my WD greens look like [and before anyone asks, temp is high because a) it's in the middle of a RAID resync and b) it's 32°C here currently];
All of those values at 0 are, TTBOMK, the ones you always want to stay at 0. Your drives should have similar attrs available for you to check.
If so, I often get the same flavour of error messages from a system running WD Greens in RAID despite smart and badblocks not reporting any errors. From reading up on it this seems to be a quirk of some firmwares on WD drives (probably the more desktop-oriented ones, IIRC I've not seen it from any of my WD reds), as I've never seen the error on any of my hitachi or toshiba drives (or any SSDs for that matter) and the only time I've had it in conjunction with an array failure has been with a) a dodgy cable connection and b) a dodgy JMicron SATA controller.
Personally I wouldn't worry too much about it as I've assigned it to the "almost certainly a red herring" bucket as I've never been able to attribute it to a failure - but then I assume you have at least one backup that you've actually tested, and that you know not to trust advice from randoms on the internet...
Edited to add - I assume you've already checked the smart attrs and you're not seeing any corresponding rise in drive error counts? Here's what one of my WD greens look like [and before anyone asks, temp is high because a) it's in the middle of a RAID resync and b) it's 32°C here currently];
Code:
SMART Attributes Data Structure revision number: 16
Vendor Specific SMART Attributes with Thresholds:
ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 0
3 Spin_Up_Time 0x0027 201 192 021 Pre-fail Always - 8916
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 16
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0
9 Power_On_Hours 0x0032 062 062 000 Old_age Always - 27790
10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0
11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0
12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 16
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 13
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 111
194 Temperature_Celsius 0x0022 107 105 000 Old_age Always - 45
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0
199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0
200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0
Last edited: