Wdmycloud Smart test bad request. (400157)

Continuing the discussion from Wdmycloud error:

I am having this same error on my WDmycloud. How did you guys resolve this? My drive is also running very slow from the UI.

When I do a SSH smartctl -A /dev/sda: this is my log:

smartctl 5.41 2011-06-09 r3365 [armv7l-linux-3.2.26] (local build)
Copyright © 2002-11 by Bruce Allen, http://smartmontools.sourceforge.net

=== START OF READ SMART DATA SECTION ===
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 203 177 021 Pre-fail Always - 6825
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 654
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 090 090 000 Old_age Always - 7821
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 - 93
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 84
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 983
194 Temperature_Celsius 0x0022 104 095 000 Old_age Always - 48
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 200 200 000 Old_age Offline - 0

Hi,

Have you tried resetting the unit? if not, please try using the physical reset button on the back of the unit.

I’m not using SSH. Let’s see if any of the users can share some additional information.

Yeah, I reset the unit and it seemed to fix it, I re-ran smartctl and I got a lot of the similar values, however, I"m not sure what the value above even mean?

Anyway, so I guess I can call this resolved.