Discussion:
[smartmontools-support] WDC WD50EFRX Self-tests fail
Andreas Grosse
2016-11-05 01:36:10 UTC
Permalink
Hello,

I have a computer with six WDC WD50EFRX-68MYMN1 (WD Red 5 TB). Three of them
are old (Two years old) and three of them are new (Bought last year). A couple
of days ago, I noticed several I/O errors on the new disks in the kernel log.
So I wanted to check the devices, but all self-tests (I tried Short offline,
Conveyance offline, Extended offline) always fail with "Fatal or unknown
error" on the new disks. I also noticed, that the new disks report a polling
time of 6 minutes for the extended self-test routine, which I find rather
unrealistic for a 5 TB drive. The old disks report 540 minutes, the self-tests
run fine on these devices. They are the same "Device model" and have the same
"Firmware Version".
Could this be some form of incompatibility or is it likely that all the drives
are garbage? Or am I just using the tool wrong?

Here is the output of "smartctl -a" for one of the new disks:
------------------------------------------------------------------------------
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.8.4-gentoo] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD50EFRX-68MYMN1
Serial Number: xxx
LU WWN Device Id: yyy
Firmware Version: 82.00A82
User Capacity: 5.000.981.078.016 bytes [5,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5700 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Nov 5 01:27:06 2016 CET
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: ( 60) 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: ( 6) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control 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 198 196 021 Pre-fail Always
- 9100
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always
- 38
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
- 423
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
- 13
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always
- 8
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always
- 81
194 Temperature_Celsius 0x0022 123 096 000 Old_age Always
- 29
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
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline Fatal or unknown error 90% 409 -
# 2 Conveyance offline Fatal or unknown error 90% 361 -
# 3 Short offline Fatal or unknown error 90% 361 -
# 4 Short offline Fatal or unknown error 90% 361 -
# 5 Short offline Fatal or unknown error 90% 361 -
# 6 Short offline Fatal or unknown error 90% 359 -
# 7 Extended offline Fatal or unknown error 90% 317 -
# 8 Short offline Fatal or unknown error 90% 317 -
# 9 Extended offline Fatal or unknown error 90% 316 -
#10 Conveyance offline Fatal or unknown error 90% 316 -
#11 Short offline Fatal or unknown error 90% 316 -

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.
------------------------------------------------------------------------------

Thank you for your help.

Andi
Christian Franke
2016-11-05 10:53:32 UTC
Permalink
Hello,
Post by Andreas Grosse
I have a computer with six WDC WD50EFRX-68MYMN1 (WD Red 5 TB). Three of them
are old (Two years old) and three of them are new (Bought last year).
Are all six drives connected to same (or same kind of) controller?
Post by Andreas Grosse
A couple
of days ago, I noticed several I/O errors on the new disks in the kernel log.
So I wanted to check the devices, but all self-tests (I tried Short offline,
Conveyance offline, Extended offline) always fail with "Fatal or unknown
error" on the new disks. I also noticed, that the new disks report a polling
time of 6 minutes for the extended self-test routine, which I find rather
unrealistic for a 5 TB drive. The old disks report 540 minutes, the self-tests
run fine on these devices. They are the same "Device model" and have the same
"Firmware Version".
There was at least one case that a vendor released an important firmware
update without changing the reported version number
(https://www.smartmontools.org/wiki/SamsungF4EGBadBlocks).
Post by Andreas Grosse
Could this be some form of incompatibility or is it likely that all the drives
are garbage? Or am I just using the tool wrong?
No, you are using the tool correctly (but try also 'smartctl -x', see
below).
Post by Andreas Grosse
...
Model Family: Western Digital Red
...
Self-test execution status: ( 0) The previous self-test routine completed
without error or no self-test has ever
been run.
This should match the status of the last test from the self-test log,
but doesn't.
Post by Andreas Grosse
SMART Error Log Version: 1
No Errors Logged
Please try "smartctl -l xerror". Errors may only appear in the new error
log. Also check for SATA cable problems: "smartctl -l sataphy". Both are
included in "smartctl -x".
Post by Andreas Grosse
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline Fatal or unknown error 90% 409 -
This self-test status is rather rare. It may suggest "unexpected" problems.

If all three new drives return I/O errors and show this unusual
behavior, I would replace these drives.

Do the serial numbers suggest that all drives are from the same batch?

Thanks,
Christian
Andreas Grosse
2016-11-05 12:27:24 UTC
Permalink
Hello Christian,
Post by Christian Franke
Are all six drives connected to same (or same kind of) controller?
All six devices are attached to an LSI SAS3008. But I have also tried the
failing devices on the Intel PCH C232 SATA-Controller, getting the same
results. (I/O-Errors and identical SMART-Data with failing self-tests)
Post by Christian Franke
There was at least one case that a vendor released an important firmware
update without changing the reported version number
(https://www.smartmontools.org/wiki/SamsungF4EGBadBlocks).
No, you are using the tool correctly (but try also 'smartctl -x', see
below).
This should match the status of the last test from the self-test log,
but doesn't.
Please try "smartctl -l xerror". Errors may only appear in the new error
log. Also check for SATA cable problems: "smartctl -l sataphy". Both are
included in "smartctl -x".
Here is the output of "smartctl -x", as far as I see, the sataphy and xerror
information is included. I have also permuted the cables between the old and
the new drives, resulting in no change. There are several Device Errors
reported on all three new devices and none on the old disks.

------------------------------------------------------------------------------
smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.8.4-gentoo] (local build)
Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Family: Western Digital Red
Device Model: WDC WD50EFRX-68MYMN1
Serial Number: WD-WX11D4431746
LU WWN Device Id: 5 0014ee 20aa7bb61
Firmware Version: 82.00A82
User Capacity: 5.000.981.078.016 bytes [5,00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
Rotation Rate: 5700 rpm
Device is: In smartctl database [for details use: -P show]
ATA Version is: ACS-2, ACS-3 T13/2161-D revision 3b
SATA Version is: SATA 3.1, 6.0 Gb/s (current: 6.0 Gb/s)
Local Time is: Sat Nov 5 12:46:10 2016 CET
SMART support is: Available - device has SMART capability.
SMART support is: Enabled
AAM feature is: Unavailable
APM feature is: Unavailable
Rd look-ahead is: Enabled
Write cache is: Enabled
ATA Security is: Disabled, NOT FROZEN [SEC1]
Wt Cache Reorder: 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: ( 60) 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: ( 6) minutes.
Conveyance self-test routine
recommended polling time: ( 5) minutes.
SCT capabilities: (0x303d) SCT Status supported.
SCT Error Recovery Control 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 FLAGS VALUE WORST THRESH FAIL RAW_VALUE
1 Raw_Read_Error_Rate POSR-K 200 200 051 - 0
3 Spin_Up_Time POS--K 198 196 021 - 9091
4 Start_Stop_Count -O--CK 100 100 000 - 41
5 Reallocated_Sector_Ct PO--CK 200 200 140 - 0
7 Seek_Error_Rate -OSR-K 200 200 000 - 0
9 Power_On_Hours -O--CK 100 100 000 - 434
10 Spin_Retry_Count -O--CK 100 253 000 - 0
11 Calibration_Retry_Count -O--CK 100 253 000 - 0
12 Power_Cycle_Count -O--CK 100 100 000 - 14
192 Power-Off_Retract_Count -O--CK 200 200 000 - 9
193 Load_Cycle_Count -O--CK 200 200 000 - 82
194 Temperature_Celsius -O---K 114 096 000 - 38
196 Reallocated_Event_Count -O--CK 200 200 000 - 0
197 Current_Pending_Sector -O--CK 200 200 000 - 0
198 Offline_Uncorrectable ----CK 100 253 000 - 0
199 UDMA_CRC_Error_Count -O--CK 200 200 000 - 0
200 Multi_Zone_Error_Rate ---R-- 100 253 000 - 0
||||||_ K auto-keep
|||||__ C event count
||||___ R error rate
|||____ S speed/performance
||_____ O updated online
|______ P prefailure warning

General Purpose Log Directory Version 1
SMART Log Directory Version 1 [multi-sector log support]
Address Access R/W Size Description
0x00 GPL,SL R/O 1 Log Directory
0x01 SL R/O 1 Summary SMART error log
0x02 SL R/O 5 Comprehensive SMART error log
0x03 GPL R/O 6 Ext. Comprehensive SMART error log
0x06 SL R/O 1 SMART self-test log
0x07 GPL R/O 1 Extended self-test log
0x09 SL R/W 1 Selective self-test log
0x10 GPL R/O 1 SATA NCQ Queued Error log
0x11 GPL R/O 1 SATA Phy Event Counters log
0x21 GPL R/O 1 Write stream error log
0x22 GPL R/O 1 Read stream error log
0x30 GPL,SL R/O 9 IDENTIFY DEVICE data log
0x80-0x9f GPL,SL R/W 16 Host vendor specific log
0xa0-0xa7 GPL,SL VS 16 Device vendor specific log
0xa8-0xb7 GPL,SL VS 1 Device vendor specific log
0xbd GPL,SL VS 1 Device vendor specific log
0xc0 GPL,SL VS 1 Device vendor specific log
0xc1 GPL VS 93 Device vendor specific log
0xe0 GPL,SL R/W 1 SCT Command/Status
0xe1 GPL,SL R/W 1 SCT Data Transfer

SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 5
CR = Command Register
FEATR = Features Register
COUNT = Count (was: Sector Count) Register
LBA_48 = Upper bytes of LBA High/Mid/Low Registers ] ATA-8
LH = LBA High (was: Cylinder High) Register ] LBA
LM = LBA Mid (was: Cylinder Low) Register ] Register
LL = LBA Low (was: Sector Number) Register ]
DV = Device (was: Device/Head) Register
DC = Device Control Register
ER = Error register
ST = Status register
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 5 [4] occurred at disk power-on lifetime: 410 hours (17 days + 2 hours)
When the command that caused the error occurred, the device was in standby
mode.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 00 00 00 00 00 00 05 50 40 00 Error: IDNF at LBA = 0x00000550 =
1360

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/
Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
61 01 50 00 00 00 00 00 00 04 00 40 00 00:51:15.046 WRITE FPDMA QUEUED
e5 00 00 00 00 00 00 00 00 00 00 00 00 00:19:53.090 CHECK POWER MODE
e5 00 00 00 00 00 00 00 00 00 00 00 00 00:19:53.090 CHECK POWER MODE
60 00 08 00 00 00 00 00 00 10 00 40 00 00:19:53.062 READ FPDMA QUEUED
60 00 98 00 10 00 02 46 30 d7 68 40 00 00:19:53.062 READ FPDMA QUEUED

Error 4 [3] occurred at disk power-on lifetime: 408 hours (17 days + 0 hours)
When the command that caused the error occurred, the device was in standby
mode.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 00 00 00 00 00 00 04 00 40 00 Error: IDNF at LBA = 0x00000400 =
1024

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/
Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
61 04 00 00 00 00 00 00 00 10 00 40 00 1d+22:14:54.270 WRITE FPDMA QUEUED
e5 00 00 00 00 00 00 00 00 00 00 00 00 1d+21:37:22.972 CHECK POWER MODE
60 00 08 00 00 00 00 00 00 10 00 40 00 1d+21:37:22.966 READ FPDMA QUEUED
60 00 98 00 10 00 02 46 30 d7 68 40 00 1d+21:37:22.965 READ FPDMA QUEUED
60 00 50 00 08 00 02 46 30 d7 10 40 00 1d+21:37:22.965 READ FPDMA QUEUED

Error 3 [2] occurred at disk power-on lifetime: 408 hours (17 days + 0 hours)
When the command that caused the error occurred, the device was in standby
mode.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 00 00 00 00 00 00 04 00 40 00 Error: IDNF at LBA = 0x00000400 =
1024

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/
Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
61 04 00 00 00 00 00 00 00 10 00 40 00 1d+21:33:33.146 WRITE FPDMA QUEUED
e5 00 00 00 00 00 00 00 00 00 00 00 00 1d+03:25:23.225 CHECK POWER MODE
60 00 08 00 00 00 00 00 00 10 00 40 00 1d+03:25:23.197 READ FPDMA QUEUED
60 00 98 00 10 00 02 46 30 d7 68 40 00 1d+03:25:23.196 READ FPDMA QUEUED
60 00 50 00 08 00 02 46 30 d7 10 40 00 1d+03:25:23.196 READ FPDMA QUEUED

Error 2 [1] occurred at disk power-on lifetime: 380 hours (15 days + 20 hours)
When the command that caused the error occurred, the device was in standby
mode.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
10 -- 51 00 00 00 00 00 00 03 a0 40 00 Error: IDNF at LBA = 0x000003a0 =
928

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/
Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
61 02 28 00 00 00 00 00 00 00 00 40 00 17:40:47.529 WRITE FPDMA QUEUED
e5 00 00 00 00 00 00 00 00 00 00 00 00 14:30:16.507 CHECK POWER MODE
60 00 08 00 00 00 00 00 00 10 00 40 00 14:30:16.503 READ FPDMA QUEUED
60 00 98 00 10 00 02 46 30 d7 68 40 00 14:30:16.502 READ FPDMA QUEUED
60 00 50 00 08 00 02 46 30 d7 10 40 00 14:30:16.502 READ FPDMA QUEUED

Error 1 [0] occurred at disk power-on lifetime: 291 hours (12 days + 3 hours)
When the command that caused the error occurred, the device was in standby
mode.

After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 00 1c 30 80 40 00 Error: UNC at LBA = 0x001c3080 =
1847424

Commands leading to the command that caused the error were:
CR FEATR COUNT LBA_48 LH LM LL DV DC Powered_Up_Time Command/
Feature_Name
-- == -- == -- == == == -- -- -- -- -- ---------------
--------------------
60 00 80 00 00 00 00 00 1c 28 00 40 00 4d+04:25:17.056 READ FPDMA QUEUED
ea 00 00 00 00 00 00 00 00 00 00 40 00 4d+02:20:08.848 FLUSH CACHE EXT
61 00 08 00 10 00 00 20 00 00 00 40 00 4d+02:20:08.847 WRITE FPDMA QUEUED
61 00 08 00 08 00 00 00 02 00 00 40 00 4d+02:20:08.847 WRITE FPDMA QUEUED
61 00 08 00 00 00 00 00 00 00 80 40 00 4d+02:20:08.847 WRITE FPDMA QUEUED

SMART Extended Self-test Log Version: 1 (1 sectors)
Num Test_Description Status Remaining LifeTime(hours)
LBA_of_first_error
# 1 Short offline Fatal or unknown error 90% 423 -
# 2 Short offline Fatal or unknown error 90% 409 -
# 3 Conveyance offline Fatal or unknown error 90% 361 -
# 4 Short offline Fatal or unknown error 90% 361 -
# 5 Short offline Fatal or unknown error 90% 361 -
# 6 Short offline Fatal or unknown error 90% 361 -
# 7 Short offline Fatal or unknown error 90% 359 -
# 8 Extended offline Fatal or unknown error 90% 317 -
# 9 Short offline Fatal or unknown error 90% 317 -
#10 Extended offline Fatal or unknown error 90% 316 -
#11 Conveyance offline Fatal or unknown error 90% 316 -
#12 Short offline Fatal or unknown error 90% 316 -

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.

SCT Status Version: 3
SCT Version (vendor specific): 258 (0x0102)
SCT Support Level: 1
Device State: Active (0)
Current Temperature: 38 Celsius
Power Cycle Min/Max Temperature: 25/38 Celsius
Lifetime Min/Max Temperature: 23/56 Celsius
Under/Over Temperature Limit Count: 0/0
Vendor specific:
00 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

SCT Temperature History Version: 2
Temperature Sampling Period: 1 minute
Temperature Logging Interval: 1 minute
Min/Max recommended Temperature: 0/60 Celsius
Min/Max Temperature Limit: -41/85 Celsius
Temperature History Size (Index): 478 (294)

Index Estimated Time Temperature Celsius
295 2016-11-05 04:49 27 ********
... ..(435 skipped). .. ********
253 2016-11-05 12:05 27 ********
254 2016-11-05 12:06 ? -
255 2016-11-05 12:07 27 ********
256 2016-11-05 12:08 ? -
257 2016-11-05 12:09 25 ******
258 2016-11-05 12:10 26 *******
259 2016-11-05 12:11 26 *******
260 2016-11-05 12:12 26 *******
261 2016-11-05 12:13 27 ********
262 2016-11-05 12:14 27 ********
263 2016-11-05 12:15 28 *********
264 2016-11-05 12:16 28 *********
265 2016-11-05 12:17 29 **********
266 2016-11-05 12:18 29 **********
267 2016-11-05 12:19 30 ***********
268 2016-11-05 12:20 30 ***********
269 2016-11-05 12:21 30 ***********
270 2016-11-05 12:22 31 ************
271 2016-11-05 12:23 31 ************
272 2016-11-05 12:24 32 *************
273 2016-11-05 12:25 32 *************
274 2016-11-05 12:26 32 *************
275 2016-11-05 12:27 33 **************
276 2016-11-05 12:28 33 **************
277 2016-11-05 12:29 33 **************
278 2016-11-05 12:30 34 ***************
279 2016-11-05 12:31 34 ***************
280 2016-11-05 12:32 34 ***************
281 2016-11-05 12:33 35 ****************
... ..( 2 skipped). .. ****************
284 2016-11-05 12:36 35 ****************
285 2016-11-05 12:37 36 *****************
... ..( 2 skipped). .. *****************
288 2016-11-05 12:40 36 *****************
289 2016-11-05 12:41 37 ******************
... ..( 2 skipped). .. ******************
292 2016-11-05 12:44 37 ******************
293 2016-11-05 12:45 38 *******************
294 2016-11-05 12:46 38 *******************

SCT Error Recovery Control:
Read: 70 (7,0 seconds)
Write: 70 (7,0 seconds)

Device Statistics (GP/SMART Log 0x04) not supported

SATA Phy Event Counters (GP Log 0x11)
ID Size Value Description
0x0001 2 0 Command failed due to ICRC error
0x0002 2 0 R_ERR response for data FIS
0x0003 2 0 R_ERR response for device-to-host data FIS
0x0004 2 0 R_ERR response for host-to-device data FIS
0x0005 2 0 R_ERR response for non-data FIS
0x0006 2 0 R_ERR response for device-to-host non-data FIS
0x0007 2 0 R_ERR response for host-to-device non-data FIS
0x0008 2 0 Device-to-host non-data FIS retries
0x0009 2 1 Transition from drive PhyRdy to drive PhyNRdy
0x000a 2 15 Device-to-host register FISes sent due to a COMRESET
0x000b 2 0 CRC errors within host-to-device FIS
0x000f 2 0 R_ERR response for host-to-device data FIS, CRC
0x0012 2 0 R_ERR response for host-to-device non-data FIS, CRC
0x8000 4 2288 Vendor specific
------------------------------------------------------------------------------
Post by Christian Franke
Post by Andreas Grosse
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining
LifeTime(hours)
LBA_of_first_error
# 1 Short offline Fatal or unknown error 90% 409
-
This self-test status is rather rare. It may suggest "unexpected" problems.
If all three new drives return I/O errors and show this unusual
behavior, I would replace these drives.
Do the serial numbers suggest that all drives are from the same batch?
These are the serial numbers:
WD-WX11D4404979
WD-WX31D3408280
WD-WX11D4431746
They have some similarities but I can not judge if this suggests they are from
the same batch.
Could this be an issue caused by myself or is it worth to give the dealer's or
WD's warranty a try?
Post by Christian Franke
Thanks,
Christian
Thank you for your quick reply!

Andi

Loading...