Drive failed, Volume degraded MCmirror 6tb

Sorry…I think I pasted wrong…
This should be the correct version:

smartctl version 5.38 [arm-marvell-linux-gnueabi] Copyright (C) 2002-8 Bruce Allen

=== START OF INFORMATION SECTION ===
Device Model: WDC WD30EFRX-68EUZN0
Serial Number: WD-WCC4N3DXUEFJ
Firmware Version: 82.00A82
User Capacity: 3,000,592,982,016 bytes
Device is: Not in smartctl database [for details use: -P showall]
ATA Version is: 9
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Mon Sep 11 23:29:39 2017 CEST
SMART support is: Available - device has SMART capability.
SMART support is: Enabled

=== START OF READ SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

General SMART Values:
Offline data collection status: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 243) Self-test routine in progress…
30% of test remaining.
Total time to complete Offline
data collection: (40080) seconds.
Offline data collection
capabilities: (0x7b) SMART execute Offline immediate.
Auto Offline data collection on/off support.
Suspend Offline collection upon new
command.
Offline surface scan supported.
Self-test supported.
Conveyance Self-test supported.
Selective Self-test supported.
SMART capabilities: (0x0003) Saves SMART data before entering
power-saving mode.
Supports SMART auto save timer.
Error logging capability: (0x01) Error logging supported.
General Purpose Logging supported.
Short self-test routine
recommended polling time: ( 2) minutes.
Extended self-test routine
recommended polling time: ( 255) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x703d) SCT Status supported.
SCT Feature Control supported.
SCT Data Table supported.

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 - 2481
3 Spin_Up_Time 0x0027 182 179 021 Pre-fail Always - 5883
4 Start_Stop_Count 0x0032 096 096 000 Old_age Always - 4803
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 6
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 3780
10 Spin_Retry_Count 0x0032 100 100 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 - 10
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 8
193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 4807
194 Temperature_Celsius 0x0022 101 094 000 Old_age Always - 49
196 Reallocated_Event_Count 0x0032 194 194 000 Old_age Always - 6
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0
198 Offline_Uncorrectable 0x0030 100 253 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

SMART Error Log Version: 1
No Errors Logged

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error

1 Short offline Completed without error 00% 3775 -

2 Short offline Completed without error 00% 3770 -

3 Short offline Completed without error 00% 3769 -

4 Short offline Completed without error 00% 3769 -

5 Extended offline Aborted by host 40% 3768 -

6 Extended offline Aborted by host 90% 3764 -

7 Extended offline Aborted by host 90% 3764 -

8 Short offline Aborted by host 10% 3764 -

9 Extended offline Completed without error 00% 3734 -

#10 Extended offline Aborted by host 90% 3727 -
#11 Extended offline Aborted by host 10% 3727 -
#12 Short offline Completed without error 00% 3716 -
#13 Short offline Completed without error 00% 0 -
#14 Short offline Completed without error 00% 0 -

SMART Selective self-test log data structure revision number 1
SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
1 0 0 Not_testing
2 0 0 Not_testing
3 0 0 Not_testing
4 0 0 Not_testing
5 0 0 Not_testing
Selective self-test flags (0x0):
After scanning selected spans, do NOT read-scan remainder of disk.
If Selective self-test is pending on power-up, resume after 0 minute delay.

Tony

SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
1 Short offline Completed without error 00% 3775 -
2 Short offline Completed without error 00% 3770 -
3 Short offline Completed without error 00% 3769 -
4 Short offline Completed without error 00% 3769 -
5 Extended offline Aborted by host 40% 3768 -
6 Extended offline Aborted by host 90% 3764 -
7 Extended offline Aborted by host 90% 3764 -
8 Short offline Aborted by host 10% 3764 -
9 Extended offline Completed without error 00% 3734 -
10 Extended offline Aborted by host 90% 3727 -
11 Extended offline Aborted by host 10% 3727 -
12 Short offline Completed without error 00% 3716 -
13 Short offline Completed without error 00% 0 -
14 Short offline Completed without error 00% 0 -

The last long test was actually done circa 2 days ago on this drive. Short tests are perfectly fine and they can happen as regularly as every hour if desired. To be honest, if after the rebuild there was a fault (which a long test would detect) then the drive would have flagged it up already as part of the rebuild process. So I would be confident to say that you are all fixed. As a final follow-up (and to build confidence in the drives), why not make a note to do long tests on a fortnightly basis whereby if all then checks out you can be reassured that the drives will be fine.

Certainly from what was the case before compared to now, you shouldn’t have any problems going forward. Congrats.

Pops

Hi Pops,

Ah ok, so I didn’t do a long test?
Because it was doing it last night…
But everything seems to be fine right now, I hope it will stay this way and not go faulty again :slight_smile:

I will run some tests on a regular bases yes, that can never do any harm I guess.

Thank you very very much for all your support in this and hope to see you in London one day!

Cheers

Tony

The last long test was done at 3768 hrs (of the drive’s powered-on life) and the last test (short in this case) was done at 3775 hours. So it’s possible that being only 7 hrs between tests, you were right that the long test did take place last night but it was aborted (at 40% completion). Check to see if the standby/energy saver mode was turned back on since this does cancel the tests.

IMHO, you can safely wait to do a long test in say a fortnight’s time and just monitor the WD dashboard for any warnings of the raid array fails again. The fact that redundancy is restored and the drive has not flagged any SMART errors is good enough I believe.

All the best!
Pops