My Cloud Home White Light Blinking and wdcloud is showing device is offline

Hello,

I have purchased wd cloud my home few days ago copied my data on it and from yesterday it suddenly stopped working, MCH is showing in router ip address list but the white lights keeps blinking and i have tried all methods like disconnecting power, changing lan ports, connecting directly to router but still its showing device is offline on the dashboard, i cannot access is locally either , by entering the MCH address or IP , it shows error . Tried pinging the ip and getting the response from it aswell. I have submitted the complain as well, if anybody can help that will be great

Edit: just checked the logs device firmware version is latest 9.4.1-101

Thanks

1 Like

It is never a good sign to see this but it will likely resolve itself after a while. The MCH is not a heavy duty media server and the SMR disk in it is likely to error out after periods of heavy activity. This is why other NAS manufacturers will not recommend using SMR drives in a NAS environment and they call this a “light duty” storage system.

You’ve already have the debug_logs.tar, might as well look at the smartctl log in it to see if there are any obvious disk errors.

I have check the smartdata.log file and its showing this, are you talking about this?

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 209 207 021 Pre-fail Always - 2533
4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 27
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 - 156
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 - 23
192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 21
193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 10
194 Temperature_Celsius 0x0022 092 087 000 Old_age Always - 55
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

Yes, your HDD looks fine right now and you may just have to wait it out until it finishes. You have low life time hours on your hdd but errors can still occur early on in lifetime such as this HDD here. You won’t be able to do the test mentioned unless you take out the HDD or boot up the MCH with a diagnostic USB image (not usually possible and not documented).

Any idea how much time it would take?

also i have also been using same drive in my office for almost three years but i set up that with directly accessing the ip address and mounting the public folder to my finder, and its been working fine and had almost 3 TB Of data, so if it starts working should i move my data to public? will it helps with this issue or it happens anyway?

SMR drives require room to roam in order to be similar in performance to a CMR drive, so the more data you have on the HDD, the slower it gets. Consider moving to a proper NAS with proper compatible CMR HDD if you find yourself running out of space all the time. The My Cloud Home is cheap and easy storage and will usually last more than the 2 years that it is warranted to last as long as it is in a light duty environment. This is what Synology says about the WD SMR HDD:

Due to performance characteristics of SMR drives, this model is only suitable for light workload environments. Performance degradation may occur under continuous write operations. Please refer to this FAQ for more information.

Please read their FAQ for further information.

Thanks, i will wait few days and then update about this, as of this moment its still in breathing mode, i last copied around 200, 300GB of data so i will give it few days

Still light is same

Update:

Still light is slowly breathing . i dont know how much do i wait

This sounded like you have done as much as you can as a home user. You may have received some kind of a reply from filing a support ticket. If possible download another debug_logs.tar and submit another ticket. The new log may show additional information.

  • Try to get warranty service if still applicable.
  • Keep waiting to see if MCH recovers.
  • Move on to something more reliable. Hopefully all your data has been backed up.

I have sent logs to them still waiting for response.
MCH is still On, Can you guide me if you know, is there any way to check logs ourselves in which we can see any kind of progress of what the process is currently going on? any progress of disk initializing etc?

So i got response from wd they looked at the logs file and sent this error and said to replace the unit after backing up my data from local acess and they sent the link to this

https://support-en.wd.com/app/answers/detailweb/a_id/50626/track/AvPzLQrZDv8Q~VoPGn4e~yJfKCcqGC75Mv8d~zj~PP~U

But the thing is i cannot access is through this as if i put ip in browser it says device is not ready and i cannot access through network either. When it was working i turned on local network access but still isnt working. What should i do now about the data thats stored in it?

Here’s the error what they pointed out through logs

debug/private/1686841723_kern.log.1.txt:2023-06-15T14:54:10.681506+00:00 di=7DMoqzEviS warning kernel: [76409.632900] isofs_f
ill_super: bread failed, dev=sdb4, iso_blknum=16, block=32
debug/private/1686841723_kern.log.1.txt:2023-06-15T14:54:10.700144+00:00 di=7DMoqzEviS err kernel: [76409.640781] UDF-fs: err
or (device sdb4): udf_read_tagged: read failed, block=256, location=256
debug/private/1686841723_kern.log.1.txt:2023-06-15T14:54:10.700237+00:00 di=7DMoqzEviS err kernel: [76409.650109] UDF-fs: err
or (device sdb4): udf_read_tagged: read failed, block=512, location=512
debug/private/1686841723_kern.log.1.txt:2023-06-15T14:54:10.718063+00:00 di=7DMoqzEviS err kernel: [76409.659161] UDF-fs: err
or (device sdb4): udf_read_tagged: read failed, block=256, location=256
debug/private/1686841723_kern.log.1.txt:2023-06-15T14:54:10.718129+00:00 di=7DMoqzEviS err kernel: [76409.668040] UDF-fs: err
or (device sdb4): udf_read_tagged: read failed, block=512, location=512
debug/private/1686841723_kern.log.1.txt:2023-06-15T14:54:10.730951+00:00 di=7DMoqzEviS err kernel: [76409.689702] exFAT-fs (s
db4): failed to read boot sector
debug/private/1686841723_kern.log.1.txt:2023-06-15T14:54:10.742023+00:00 di=7DMoqzEviS err kernel: [76409.695093] exFAT-fs (s
db4): failed to recognize exfat type

Thanks for reporting the details. It is not too often home users bothered to follow up with their results after asking the user forum for help.

It would appeared that your MCH is booting up incompletely and ended up in an emergency maintenance mode. This may have resulted in the drive not being mounted in the network.

You have nothing to lose by trying to manually mount the MCH in Windows at this point, it may or may not mount:

Start Windows command line by (Windows key + R then type ‘cmd’ without the quotes), then enter
net use V: \ipaddress\public /user:‘user name’ “password”
So if your MCH ip is 192.168.2.22, local user name is danka and local password is ‘aaabbb’ you would enter

net use V: \\192.168.2.22\public /user:danka aaabbb

if it mounts in Windows, you will see “The command completed successfully”
then go to Windows File Explorer and see if you can browse drive V:

If you can’t mount the MCH, try to get warranty service and data recovery as suggested by WDC.

I have tried the mentioned way but it is giving this error “The network name cannot be found”

1 Like

So, i was unable to take backup and my data is lost, Which is quite sad considering a its a brand new drive and it can fail and their is not way to take backup apart from using data recovery companies which ofcourse takes huge amount of money, so i have decided to claim warranty and send my drive back to them hopefully they replace the device and this time it works properly. Lesson learned to not trust these drives and take multiple backups.

Overall pretty dissapointed with this product and the response from WD