I recently bought three WD30EZRX drives (before doing enough reading to realise they might not be ideal for a RAID array :-} But this isn’t about that).
At first, although I only have my memory to show for it, they all showed full SMART data. But at some point since I first checked, one of them has stopped showing SMART log data, claiming that logging is not supported. The other two drives are still reporting fine.
The affected drive still appears otherwise to be *working*, but I’m wondering if this is one I ought to be sending back, or if it just needs a poke of some form to enable the SMART logging again.
yes, it does persist through reboots and power-cycles.
This is what I get right now:
rachel@twilight:~$ sudo smartctl -a /dev/sdh
[sudo] password for rachel:
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.0-19-generic] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format)
Device Model: WDC WD30EZRX-00MMMB0
Serial Number: WD-WMAWZ0209664
Firmware Version: 0958
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Size: 512 bytes logical/physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 7
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Nov 30 11:42:26 2012 GMT
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.
Total time to complete Offline
data collection: ( 0) seconds.
Offline data collection
capabilities: (0x00) Offline data collection not supported.
SMART capabilities: (0x0000) Automatic saving of SMART data is not implemented.
Error logging capability: (0x00) Error logging NOT supported.
No General Purpose Logging support.
SMART Error Log not supported
SMART Self-test Log not supported
Device does not support Selective Self Tests/Logging
For comparison, this is what one of the other drives gives me; the third drive is similar to the second:
rachel@twilight:~$ sudo smartctl -a /dev/sdi
smartctl 5.43 2012-06-30 r3573 [x86_64-linux-3.5.0-19-generic] (local build)
Copyright (C) 2002-12 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Model Family: Western Digital Caviar Green (Adv. Format)
Device Model: WDC WD30EZRX-00MMMB0
Serial Number: WD-WMAWZ0213423
LU WWN Device Id: 5 0014ee 0adaf0dbd
Firmware Version: 80.00A80
User Capacity: 3,000,592,982,016 bytes [3.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Device is: In smartctl database [for details use: -P show]
ATA Version is: 8
ATA Standard is: Exact ATA specification draft version not indicated
Local Time is: Fri Nov 30 11:42:29 2012 GMT
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: (0x80) Offline data collection activity
was never started.
Auto Offline Data Collection: Enabled.
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
Total time to complete Offline
data collection: (50700) 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: ( 487) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x3035) 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 - 0
3 Spin_Up_Time 0x0027 141 140 021 Pre-fail Always - 9933
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 23
5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0
7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0
9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 260
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 - 22
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 17
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 68
194 Temperature_Celsius 0x0022 102 094 000 Old_age Always - 50
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 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 100 253 000 Old_age Offline - 0
SMART Error Log Version: 1
No Errors Logged
SMART Self-test log structure revision number 1
No self-tests have been logged. [To run self-tests, use: smartctl -t]
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.
The drives are in bays 1-3 of a hornettek enterprise 4x eSATA enclosure (the affected drive is in bay 1) connected via a Startech port-multiplier eSATA interface, on an ubuntu quantal system. I don’t think these ought to be relevant given only one of the drives is exhibiting this.
What may *possibly* be more relevant, though I feel superstitious for saying so is this:
After initially putting these three drives into the enclosure and using them for a while, I put a drive into bay 4: an older caviar green model: WD10EACS that wasn’t currently in a machine though I couldn’t remember why I had a 1TB drive not in use. After an hour or so of use, the drive in bay 1 (the drive I’m talking about) dropped out of the raid, causing a huge headache as you can imagine, with sense errors logged in syslog.
I removed the old 1TB drive, and since then the drive has been fine, no more sudden errors, disappearances, sense faults etc., even after later populating bay 4 with another even older drive (WD5000AAKS as if that’s relevant). It’s been working fine, except I *think* it no longer having SMART logging dates from then.
For now I’m considering the old 1TB Caviar Green drive to be Poison, although, as I say, I feel a bit superstitious for doing so, not knowing how such a “poison” might work, but I have a suspicion it killed my Sharkoon drive dock as well. Correlation may not be causation, but I don’t fancy putting it back into a system any time soon, and this may after all be why it was taken out of one before.
As an aside, according to those two drives, I don’t seem to be getting the rapidly-escalating LCC figures others are seeing; but it’s only just come off about a fortnight of reshaping and then repopulating the array - but having finished doing that a few hours ago *something* still seems active whenever the RAID is up (even though /proc/mdstat shows nothing going on and the drive activity lights don’t flicker; the only way I can tell is from the sound) so the drives are probably avoiding the LCC problem by virtue of never getting a chance to idle. Suspecting this may bed in later.