Can anyone let me know if the disk drive diagnostic tools are definitive. If I run the Western Digital Data LifeGuard Diagnostics tool on my 4 x 2Tb WD-20EARS CAVIAR GREEN 2TB 64MB 7200 SAT and they all came back as passed, can I yes 100% that the disk are ok ?
Re: Disk drive diagnostic tool are they definitive ?
alan27 wrote:
Hi All
Can anyone let me know if the disk drive diagnostic tools are definitive. If I run the Western Digital Data LifeGuard Diagnostics tool on my 4 x 2Tb WD-20EARS CAVIAR GREEN 2TB 64MB 7200 SAT and they all came back as passed, can I yes 100% that the disk are ok ?
Or is there a possibly they could still be bad ?
Thanks Alan
Vendor thresholds for bad sectors are much higher than the ones I personally use. So I always look at the smart data (which Lifeguard will show you) in addition to their pass/fail. If you see a trend of increasing reallocated sectors, then the drive is almost certainly failing even if it hasn't reached the vendor threshold yet.
I have tested drives I knew were failing, but the vendor tools still passed them. Waited another week, and then they failed. So in my experience, if the vendor tools report a fail, then the drive is certainly bad. However, if they report a pass, it does not guarantee that the drive is good.
Are you having issues with your drives? Maybe you could post the details.
Re: Disk drive diagnostic tool are they definitive ?
Hi mdgm
It's all part of an ongoing issue I have with my NV + not booting which I have a thred running here for : viewtopic.php?f=20&t=58275
Just trying to elimate as much as possible. 3 of the 4 drives have been tested so far and all have passed, just disk 1 to go , but didn't look at the increasing reallocated sectors part. So will have to put them all back in and have a look once disk one has finished. (7 hours to go 😞 ) thanks for the info yes I am on 4.1.7. The disk are only 10 month old just find it hard to believe 4 disk fail at the same time, but looks like there ok ..... Maybe.
Once this disk is done I'll pull the report for each disk and post them here, so you can see if that's ok , if thats ok .If you get a spare min to have a look at my main issue that would also be most appreciated 🙂
Re: Disk drive diagnostic tool are they definitive ?
I'm just a user like you and don't know much about SMART. Feel free to post the drive SMART stats (I wouldn't post drive serial numbers though, so edit those out).
The vendors tests are the best tests available but they're not guaranteed to pick up if a drive has issues.
Re: Disk drive diagnostic tool are they definitive ?
Ok so out of the 4 x 2Tb WD-20EARS CAVIAR GREEN 2TB , Disk 1 failed. Disk 2, 3, 4 passed . But I’m very worried that the remaining disk are on their way out , as they were all purchased at the same time , maybe a bad batch ? any advice you could give me here would be most appreciated.
Here is the SMART logs for each disk
Disk 1 , this is the one that failed
=== START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00J2GB0 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Oct 27 09:48:32 2011 WEST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (40260) 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.
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.
Disk 2 ,
=== START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00J2GB0 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Oct 27 09:48:35 2011 WEST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (39600) 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.
SMART Error Log Version: 1 ATA Error Count: 12 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 12 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 11 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 10 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 9 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 8 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d6 01 e0 4f c2 40 00 12:30:27.726 SMART WRITE LOG b0 d6 01 e0 4f c2 40 00 12:30:27.568 SMART WRITE LOG ec 00 01 01 00 00 a0 00 12:30:27.388 IDENTIFY DEVICE
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.
Disk 3
=== START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00J2GB0 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Oct 27 09:48:38 2011 WEST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (40260) 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.
SMART Error Log Version: 1 ATA Error Count: 12 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 12 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 11 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 10 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 9 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 8 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d6 01 e0 4f c2 40 00 12:30:28.036 SMART WRITE LOG b0 d6 01 e0 4f c2 40 00 12:30:27.878 SMART WRITE LOG ec 00 01 01 00 00 a0 00 12:30:27.698 IDENTIFY DEVICE
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.
Disk 4
=== START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00J2GB0 Firmware Version: 80.00A80 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Thu Oct 27 09:48:43 2011 WEST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. 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: (41880) 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.
SMART Error Log Version: 1 ATA Error Count: 12 (device log contains only the most recent five errors) CR = Command Register [HEX] FR = Features Register [HEX] SC = Sector Count Register [HEX] SN = Sector Number Register [HEX] CL = Cylinder Low Register [HEX] CH = Cylinder High Register [HEX] DH = Device/Head Register [HEX] DC = Device Command Register [HEX] ER = Error register [HEX] ST = Status register [HEX] Powered_Up_Time is measured from power on, and printed as DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes, SS=sec, and sss=millisec. It "wraps" after 49.710 days.
Error 12 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 11 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 10 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 9 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Error 8 occurred at disk power-on lifetime: 12 hours (0 days + 12 hours) When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were: ER ST SC SN CL CH DH -- -- -- -- -- -- -- 04 51 01 00 00 00 40 Error: ABRT
Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- -------------------- b0 d6 01 e0 4f c2 40 00 12:30:29.630 SMART WRITE LOG b0 d6 01 e0 4f c2 40 00 12:30:29.472 SMART WRITE LOG ec 00 01 01 00 00 a0 00 12:30:29.291 IDENTIFY DEVICE
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.
What I find odd ( to my untrained eye ) is Disk 1 looks ok in the logs , no errors like 2,3,4 but yet that’s the one the failed .... also 2,3,4 are almost identical 12 errors ? hmmm? I have also read about ATA Error Counts , Reallocated Sector Counts and Load Cycle Count as ones to look out for as a guide to if you hard drive is on its way out ....
Is 12 ATA errors bad ? is a Load Cycle Count of disk 2: 362613 Disk 3: 421549 Disk 4: 423058 something I should be worrying about ? these hard drives are only 10 month old .
Any help / advice you can give me here would be most appreciated.
Re: Disk drive diagnostic tool are they definitive ?
Did your NAS come with firmware older than 4.1.7? If so that would explain why you have those ATA errors. As for the Load Cycle Count don't worry about it, those numbers are meant to be high.
Re: Disk drive diagnostic tool are they definitive ?
Hi Mdgm
Thanks again, for taking the time to look and help, yes your right , it came with 4.1.6, last Dec then upgrade 2 ish month after that to 4.1.7 . cool so there looking good at the mo 🙂
Here is my Partition.log
Disk /dev/hdi doesn't contain a valid partition table
Disk /dev/hdc: 2000.3 GB, 2000388448256 bytes 255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/hdc1 2 4096001 2048000 83 Linux Partition 1 does not end on cylinder boundary. /dev/hdc2 4096002 4608001 256000 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/hdc3 4608002 3906992305 1951192152 5 Extended /dev/hdc5 4608003 3906992305 1951192151+ 8e Linux LVM
Disk /dev/hde: 2000.3 GB, 2000388448256 bytes 255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/hde1 2 4096001 2048000 83 Linux Partition 1 does not end on cylinder boundary. /dev/hde2 4096002 4608001 256000 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/hde3 4608002 3906992305 1951192152 5 Extended /dev/hde5 4608003 3906992305 1951192151+ 8e Linux LVM
Disk /dev/hdg: 2000.3 GB, 2000388448256 bytes 255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000
Device Boot Start End Blocks Id System /dev/hdg1 2 4096001 2048000 83 Linux Partition 1 does not end on cylinder boundary. /dev/hdg2 4096002 4608001 256000 82 Linux swap / Solaris Partition 2 does not end on cylinder boundary. /dev/hdg3 4608002 3906992305 1951192152 5 Extended /dev/hdg5 4608003 3906992305 1951192151+ 8e Linux LVM
Disk /dev/hdi: 2000.3 GB, 2000388448256 bytes 255 heads, 63 sectors/track, 243200 cylinders, total 3907008688 sectors Units = sectors of 1 * 512 = 512 bytes Disk identifier: 0x00000000
What can you tell from that then ? (hope all is good there also)
Re: Disk drive diagnostic tool are they definitive ?
Now you mention it , it’s not the quickest no , that was something I was planning to look into later, do you know how I can fix this and align the sectors ? I’m guessing it’s a factory reset using 4.1.7 or 4.1.8 ?
Re: Disk drive diagnostic tool are they definitive ?
Yes, upgrading to 4.1.7 or later (you've already done this), verifying update is successful (i.e. new version shown in Frontview and/or RAIDar), a backup and a factory reset is the way to fix it.
Re: Disk drive diagnostic tool are they definitive ?
alan27 - one never really knows when a drive may fail. You may not experience a failure in drives 2-4 for a long time. When I set up my NV+ over 4 1/2 years ago with two 500GB Seagates, one failed in a little over a month. The second one was still going strong when I upgraded the drive size last summer and it had over 25,600 hours on the drive. Hopefully you will not have another drive failure for some time, but one just never knows.
