I’m getting these two errors on my phone. Should I just chuck it and get as far away from WD as I can?
This is like somebody taking a photo of an error code on their automobile dashboard and saying should he chuck it, whether he may be driving a Ford or a Ferrari. Hard disks are made to be obsolete in a short lifespan, some are 2 years, some may last 5 years or more. If you paid the cheapest price for your storage, don’t expect the longest use case for the storage, be the hard disks reside in a lowly My Cloud Home or a high end Synology.
Download the debug_logs.tar and look at the smartctl log from your MCH Duo and file a support case, you are the only person who can do that.
WD Technical Support team for best assistance and troubleshooting:https://support-en.wd.com/app/ask
The smartctl log will look something like this, yours will obviously be different:
smartctl 6.6 2017-11-05 r4594 [aarch64-linux-4.9.266] (local build)
Copyright (C) 2002-17, Bruce Allen, Christian Franke, www.smartmontools.org
=== START OF READ SMART DATA SECTION ===
SMART Extended Comprehensive Error Log Version: 1 (6 sectors)
Device Error Count: 479 (device log contains only the most recent 24 errors)
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 479 [22] occurred at disk power-on lifetime: 13492 hours (562 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 16 20 94 e0 40 00 Error: UNC at LBA = 0x162094e0 = 371234016
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 08 00 e0 00 00 16 20 94 e0 40 08 15:44:48.663 READ FPDMA QUEUED
61 00 48 00 c8 00 00 c5 97 4a c0 40 08 15:44:48.626 WRITE FPDMA QUEUED
60 00 08 00 b8 00 00 00 0b ab f8 40 08 15:44:48.626 READ FPDMA QUEUED
60 00 08 00 b0 00 00 00 95 11 18 40 08 15:44:48.626 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 08 15:44:48.583 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
Error 478 [21] occurred at disk power-on lifetime: 13492 hours (562 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 16 20 94 e0 40 00 Error: UNC at LBA = 0x162094e0 = 371234016
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 08 00 00 00 00 16 20 94 e0 40 08 15:44:46.332 READ FPDMA QUEUED
60 00 08 00 e8 00 00 00 95 11 18 40 08 15:44:46.332 READ FPDMA QUEUED
60 00 08 00 e0 00 00 00 0b ab f8 40 08 15:44:46.332 READ FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 08 15:44:46.289 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 15:44:46.288 IDENTIFY DEVICE
Error 477 [20] occurred at disk power-on lifetime: 13492 hours (562 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 16 20 94 e0 40 00 Error: UNC at LBA = 0x162094e0 = 371234016
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 08 00 48 00 00 16 20 94 e0 40 08 15:44:44.072 READ FPDMA QUEUED
61 00 08 00 28 00 00 c5 97 4a 20 40 08 15:44:44.042 WRITE FPDMA QUEUED
61 00 08 00 18 00 00 e9 18 27 88 40 08 15:44:44.042 WRITE FPDMA QUEUED
60 00 08 00 10 00 00 00 95 e7 30 40 08 15:44:44.042 READ FPDMA QUEUED
60 00 08 00 08 00 00 00 95 6a 48 40 08 15:44:44.042 READ FPDMA QUEUED
Error 476 [19] occurred at disk power-on lifetime: 13492 hours (562 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 16 20 94 e0 40 00 Error: UNC at LBA = 0x162094e0 = 371234016
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 08 00 b0 00 00 00 0b ab f8 40 08 15:44:41.827 READ FPDMA QUEUED
60 01 00 00 a8 00 00 00 0a 3d 88 40 08 15:44:41.827 READ FPDMA QUEUED
60 00 08 00 a0 00 00 00 95 6a 48 40 08 15:44:41.827 READ FPDMA QUEUED
60 00 08 00 98 00 00 00 95 e7 30 40 08 15:44:41.827 READ FPDMA QUEUED
60 00 08 00 18 00 00 16 20 94 e0 40 08 15:44:41.806 READ FPDMA QUEUED
Error 475 [18] occurred at disk power-on lifetime: 13492 hours (562 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 16 20 95 80 40 00 Error: UNC at LBA = 0x16209580 = 371234176
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 08 00 38 00 00 16 20 94 88 40 08 15:44:39.556 READ FPDMA QUEUED
60 00 08 00 a8 00 00 16 20 94 80 40 08 15:44:39.507 READ FPDMA QUEUED
60 00 08 00 98 00 00 00 0c a0 18 40 08 15:44:39.507 READ FPDMA QUEUED
60 01 00 00 90 00 00 16 20 95 80 40 08 15:44:39.507 READ FPDMA QUEUED
60 00 08 00 88 00 00 00 95 7c 50 40 08 15:44:39.507 READ FPDMA QUEUED
Error 474 [17] occurred at disk power-on lifetime: 13492 hours (562 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 16 20 94 e0 40 00 Error: UNC at LBA = 0x162094e0 = 371234016
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 01 00 00 30 00 00 16 20 94 80 40 08 15:44:37.242 READ FPDMA QUEUED
60 01 00 00 28 00 00 16 20 93 80 40 08 15:44:37.242 READ FPDMA QUEUED
60 01 00 00 20 00 00 16 20 92 80 40 08 15:44:37.241 READ FPDMA QUEUED
60 01 00 00 18 00 00 16 20 91 80 40 08 15:44:37.240 READ FPDMA QUEUED
60 01 00 00 10 00 00 16 20 90 80 40 08 15:44:37.239 READ FPDMA QUEUED
Error 473 [16] occurred at disk power-on lifetime: 13492 hours (562 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 2c 43 1e 88 40 00 Error: UNC at LBA = 0x2c431e88 = 742596232
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 08 00 88 00 00 2c 43 1e 88 40 08 15:36:07.841 READ FPDMA QUEUED
60 01 00 00 80 00 00 00 0c a2 f0 40 08 15:36:07.811 READ FPDMA QUEUED
60 01 00 00 08 00 00 00 0b 7b 80 40 08 15:36:07.809 READ FPDMA QUEUED
61 03 38 00 00 00 00 00 95 09 68 40 08 15:36:07.799 WRITE FPDMA QUEUED
60 00 80 00 f0 00 00 00 0b ab e8 40 08 15:36:07.790 READ FPDMA QUEUED
Error 472 [15] occurred at disk power-on lifetime: 13492 hours (562 days + 4 hours)
When the command that caused the error occurred, the device was active or idle.
After command completion occurred, registers were:
ER -- ST COUNT LBA_48 LH LM LL DV DC
-- -- -- == -- == == == -- -- -- -- --
40 -- 51 00 00 00 00 2c 43 1e 88 40 00 Error: UNC at LBA = 0x2c431e88 = 742596232
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 08 00 10 00 00 2c 43 1e 88 40 08 15:36:05.566 READ FPDMA QUEUED
61 00 a8 00 00 00 00 e9 17 a4 a0 40 08 15:36:05.566 WRITE FPDMA QUEUED
27 00 00 00 00 00 00 00 00 00 00 e0 08 15:36:05.523 READ NATIVE MAX ADDRESS EXT [OBS-ACS-3]
ec 00 00 00 00 00 00 00 00 00 00 a0 08 15:36:05.522 IDENTIFY DEVICE
ef 00 03 00 46 00 00 00 00 00 00 a0 08 15:36:05.522 SET FEATURES [Set transfer mode]
Well, I sure wish they would have told me the drive was only going to last a few years. That would have made a big difference! As for this last reply, you might as well be talking Chinese! I’m going get a SSD and NOT from WD! Thanks y’all!
The My Cloud Home has a two year warranty. Manufacturers know very well how long their devices are likely to lasts. Even a Toyota only has a 3 year warranty. These are all mechanical devices that required attention.
The reply linked to WD tech support, any owner would just have to make an effort to file which unfortunately is something lacking for many owners.
WD Technical Support team for best assistance and troubleshooting:https://support-en.wd.com/app/ask
I appreciate your advice. Y’all have really helped me understand a few things. I’m just getting away from these mechanical disks. I’m going with SSD and I’m going to give a different brand a try. There seems to be something that WD is lacking.
