Hi there
I have discovred that my device slow down dramatically. it is practically not resposive. I used ssh access to see the problem. And finally I run top on ssh and saw the io wait time is close to 99 % !!!
With hdparm -tT /dev/sda I received 40 KB/s read !!!
So the disk speed is the problem.
Does any one know if I can do about it or it is indication of disk failure?
what does smartctl say? If it has lots of reallocated sectors, and is having sense errors, yes— drive is definitely on the way out-- Should have a nasty indicator in the dashboard if that is the case though.
Some time ago I had the same problem with a very slow disk speed / access to the NAS. My Cloud v.04 found bad sectors when I tried: Dashboard > Settings > Utilities > System Diagnostics > Full Test
I was finally able to solve the problem after I contacted WD support. As mentioned, media indexing processes may be responsible. Other problems can be:
- Fragmented or corrupted files (spesially files like *.jpg *gif and *.mp3 files)
- Huge amount of small sized files and many sub-directories
- Home network with old router, switches and network cards. All devices should ideally be gigabit, and Ethernet cables Cat. 6 should be used
In my case I solved the problem this way:
- Home network was updated to gigabit (a new Asus Router)
- Many directories with small files I do not need very often was compressed in zip files
- Made a proper backup (2 complete backups) of My Cloud content
- A System Full Factory Restore from Dashboard
- Restoring content from backup
The downside with this method is that it takes days to accomplish. After the System Full Factory Restore, the Full Test returned: Self Test Passed, and the access to NAS was normal.
This is the smartctl result
Do you think that disk is totally out of control and is to Finnish?
WDMyCloud:~# smartctl -a /dev/sda
smartctl 5.41 2011-06-09 r3365 [armv7l-linux-3.2.26] (local build)
Copyright (C) 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net
=== START OF INFORMATION SECTION ===
Device Model: WDC WD20EFRX-68EUZN0
Serial Number: WD-WMC4M1211173
LU WWN Device Id: 5 0014ee 003a90d8e
Firmware Version: 80.00A80
User Capacity: 2,000,398,934,016 bytes [2.00 TB]
Sector Sizes: 512 bytes logical, 4096 bytes physical
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: Tue Dec 5 20:15:26 2017 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: (0x00) Offline data collection activity
was never started.
Auto Offline Data Collection: Disabled.
Self-test execution status: ( 121) The previous self-test completed having
the read element of the test failed.
Total time to complete Offline
data collection: (27840) 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 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 194 194 051 Pre-fail Always - 55840
3 Spin_Up_Time 0x0027 178 178 021 Pre-fail Always - 4066
4 Start_Stop_Count 0x0032 036 036 000 Old_age Always - 64817
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 062 062 000 Old_age Always - 28212
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 - 72
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 53
193 Load_Cycle_Count 0x0032 179 179 000 Old_age Always - 64763
194 Temperature_Celsius 0x0022 110 094 000 Old_age Always - 37
196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0
197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 7
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
ATA Error Count: 54536 (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 54536 occurred at disk power-on lifetime: 28212 hours (1175 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
-- -- -- -- -- -- --
40 51 80 30 c5 d9 e4 Error: UNC 128 sectors at LBA = 0x04d9c530 = 81380656
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 00 c5 d9 e4 08 06:53:25.775 READ DMA
ec 00 00 00 00 00 a0 08 06:53:25.767 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 06:53:25.767 SET FEATURES [Set transfer mode]
Error 54535 occurred at disk power-on lifetime: 28212 hours (1175 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
-- -- -- -- -- -- --
40 51 80 30 c5 d9 e4 Error: UNC 128 sectors at LBA = 0x04d9c530 = 81380656
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 00 c5 d9 e4 08 06:53:16.804 READ DMA
ec 00 00 00 00 00 a0 08 06:53:16.796 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 06:53:16.796 SET FEATURES [Set transfer mode]
Error 54534 occurred at disk power-on lifetime: 28212 hours (1175 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
-- -- -- -- -- -- --
40 51 80 30 c5 d9 e4 Error: UNC 128 sectors at LBA = 0x04d9c530 = 81380656
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 00 c5 d9 e4 08 06:53:07.833 READ DMA
ec 00 00 00 00 00 a0 08 06:53:07.825 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 06:53:07.825 SET FEATURES [Set transfer mode]
Error 54533 occurred at disk power-on lifetime: 28212 hours (1175 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
-- -- -- -- -- -- --
40 51 80 30 c5 d9 e4 Error: UNC 128 sectors at LBA = 0x04d9c530 = 81380656
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 00 c5 d9 e4 08 06:52:58.862 READ DMA
ec 00 00 00 00 00 a0 08 06:52:58.854 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 06:52:58.854 SET FEATURES [Set transfer mode]
Error 54532 occurred at disk power-on lifetime: 28212 hours (1175 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
-- -- -- -- -- -- --
40 51 80 30 c5 d9 e4 Error: UNC 128 sectors at LBA = 0x04d9c530 = 81380656
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
c8 00 80 00 c5 d9 e4 08 06:52:49.891 READ DMA
ec 00 00 00 00 00 a0 08 06:52:49.883 IDENTIFY DEVICE
ef 03 46 00 00 00 a0 08 06:52:49.883 SET FEATURES [Set transfer mode]
SMART Self-test log structure revision number 1
Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
# 1 Selective offline Completed: read failure 90% 28207 75950704
# 2 Extended offline Interrupted (host reset) 90% 28206 -
# 3 Short offline Completed: read failure 90% 28206 75950704
# 4 Extended offline Completed: read failure 90% 28206 75950704
# 5 Extended offline Interrupted (host reset) 90% 28157 -
# 6 Extended offline Completed: read failure 90% 28147 75950704
# 7 Extended offline Interrupted (host reset) 90% 28147 -
# 8 Short offline Interrupted (host reset) 90% 28147 -
# 9 Short offline Completed: read failure 90% 28145 75950704
#10 Short offline Interrupted (host reset) 90% 28144 -
#11 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 75950704 75950800 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.
vmstat shows still io waits… does any of you believe that this is like 90% disk failure to slow down the system? I wonder what is your swap size on idle system - i have 130 k usage at lowest. Is it ok?
WDMyCloud:~# vmstat 10 20
procs -----------memory---------- ---swap-- -----io---- -system-- ----cpu----
r b swpd free buff cache si so bi bo in cs us sy id wa
0 11 137280 48256 1792 20480 130 51 232 52 190 289 1 2 1 96
1 10 160256 46336 4800 31040 8160 4154 11810 4164 1858 2446 1 5 0 94
1 23 144192 49792 2752 17536 5690 1350 7621 1362 1524 1902 1 3 0 95
2 26 146688 48256 1920 14464 4794 3430 7238 3432 1917 2594 1 2 0 98
2 9 167488 74496 2944 20480 6874 5350 11049 5352 606 901 12 13 0 75
1 11 136448 52224 4928 26496 5984 493 8072 506 1677 2102 2 5 0 93
1 7 136512 51456 2752 30080 1267 147 2066 152 310 410 1 3 0 96
1 11 136512 48640 2752 30144 102 0 109 0 222 254 0 0 0 99
1 12 136512 47360 2752 30144 0 0 0 0 229 256 0 0 0 99
2 14 136384 47104 2880 30272 0 0 1 0 228 250 0 0 0 100
0 15 136000 48192 2880 30208 38 0 38 0 225 254 0 0 0 100
0 11 167616 64576 3008 14848 2656 4243 3835 4244 417 610 4 12 0 84
0 11 165440 57984 3328 20736 1139 70 1691 71 290 363 1 3 0 95
0 14 165376 56896 3392 20800 102 0 103 0 297 428 0 0 0 100
0 14 165312 56768 3392 20800 0 0 0 0 282 445 0 1 0 99
0 14 165312 56896 3392 20800 0 0 0 0 280 437 0 1 0 99
0 14 165312 56832 3392 20800 0 0 0 0 280 441 0 0 0 100
3 6 150208 48320 4032 22208 3590 262 4812 262 408 668 6 13 0 81
0 22 160128 47424 3904 27008 2522 1690 3551 1690 1434 1796 2 5 0 93
2 17 165760 50816 2112 22464 3725 1267 4818 1268 1782 2726 1 2 0 98
After your suggestion to
-
turn off DLNA server and iTunes server
-
thumbnail scanning off
-
!!! turning off the cloud access
server got back to be responsive after some hours.
For me it is a big question mark to WD how the process of building the database (run in the background) can kill the system?
I started to setup cloud access again and it worked fine. After system has been rebooted it started indexing and situation is back and system is not responsive
The other questions are:
- How to stop indexing process? Is it automatically turn on when cloud access enabled?
Normally My Cloud don’t kill the system under the process of building the database. As you desribe, something is wrong with your device.
What response do you get form: Dashboard > Settings > Utilities > System Diagnostics > Full Test
Your device reports a high reallocated sector count, and a high read error rate.
This suggests imminent drive failure very soon. (impossible to predict when.) I suggest backing up the contents of your MyCloud, and contacting WD customer support.
In the meantime, reducing disk activity is a good stopgap, and disabling the scanner is a good idea.
If you dont mind voiding any chance of warranty coverage, and dont feel squeamish about opening the unit or using disk imaging software, it might be possible to replace the drive pre-failure with a same size or larger disk, and doing a full disk image before placing the new drive into the system. It might be necessary to use something like DDRescue to do the disk image if there are still unreadable sectors.
