Network connection lost after firmware update v04.01.00-408

Legacy Products My Cloud OS 3
1

After the firmware v04.01.00-408 update I keep losing my network connection to WDmycloud. It is pingable, so it does exists, yet no connection can be made. Only thing I can do is reboot the WDmycloud by turning it off/on, but after a few minutes connection is lost again… Very frustrating 

Any solution?

2

I am always scared to install a new firmware.

You really don’t know what’s gonna happen there after.

Good advice is when everything goes well keep fingers off the firmware updates.:wink:

3

it’s good advice most of times, but old firmware have Shellshock vulnerability and new one get if fixed, so it’s worth to upgrade, but of course it’s risk that you may face new troubles which wasn’t there before. So far I’m more lucky and MyCloud seems to be visible when I’m using new firmware.

4

Mine 3Tb is running on firmware v03.04.01-230 and i have no problems at all.

Except from this vulnerability thing.

But if i read al this misery here i don’t think i want to update this device anymore.

5

Problem is most likely hidden in the stuff for Mac so if you don’t have it, it’s possible to disable and see how it works, I’ve did it last week and it seems to help with loosing access, here are more positive feedback on this issue:

http://community.wd.com/t5/WD-My-Cloud/MyCloud-4TB-Keep-losing-access-to-the-shares-daily/m-p/807497

6

If it is pingable the network connection is not lost.

what are you trying that won’t connect?

Do you have a static IP set? I would set this and be sure it is outside of the DHCP pool on the router

7

Hi

I’m also facing same problems since I updated the my cloud 1.0.6.13 and the firmware yesterday. Now I cannot access my dashboard plus I can’t connect to my wd my cloud since the upgrade. WD pleases resolve the new update if there is a problem with the updates. Before this everything seems fine and smooth. Thanks

8

try just unplug and then replug the network-cable. It worked for me!

9

sometimes its work…now i find out why this thing happened. once i disconnect my usb hard drive from the mycloud everything seems fine. try plug back my usb its happened again. im using usb hard drive wd my passport and wd my book. 

10

Hi,

I am the guy that wrote the post that " ingsoc" linked too above.

http://community.wd.com/t5/WD-My-Cloud/MyCloud-4TB-Keep-losing-access-to-the-shares-daily/m-p/807497

My WDMyCloud has been running without problems since I made the changes that Alex873 suggested on my post.

Last night I also took the plunge and upgraded to v0.4.01.00-408.

It has been unstable since.

Tonight I rebooted and within 20 minutes of reboot it crashed.

I also have a USB drive connected and I have the media server indexing.

I have re-applied the settings as per my post and it still crashes.

As with you the NAS box is pingable but all the shares are inaccessible and the website is not loading

So I connect via SSH and issue the

cat \var\log\kern.log

I find like last time errors from my “usb 2-1: reset SuperSpeed USB device number 2 using xhci-hcd” entires every 7 seconds.

and then eventually I find this entry

Dec 3 19:51:40 WDMyCloud kernel: [1159.932341] apache2 invoked oom-killer: gfp_mask=0x201da, order=0, oom_adj=0, oom_score_adj=0

Then the system goes through and kills the following processes

Line 655: Dec 3 19:51:41 WDMyCloud kernel: [1160.593324] Out of memory: Kill process 8563 (apache2) score 23 or sacrifice child
	Line 742: Dec 3 19:51:43 WDMyCloud kernel: [1162.456259] Out of memory: Kill process 8576 (apache2) score 23 or sacrifice child
	Line 830: Dec 3 19:51:53 WDMyCloud kernel: [1172.299883] Out of memory: Kill process 8581 (apache2) score 23 or sacrifice child
	Line 916: Dec 3 19:52:10 WDMyCloud kernel: [1189.835949] Out of memory: Kill process 8584 (apache2) score 23 or sacrifice child
	Line 1002: Dec 3 19:52:28 WDMyCloud kernel: [1207.734254] Out of memory: Kill process 9661 (apache2) score 24 or sacrifice child
	Line 1088: Dec 3 19:52:36 WDMyCloud kernel: [1215.874978] Out of memory: Kill process 9677 (apache2) score 23 or sacrifice child
	Line 1174: Dec 3 19:52:43 WDMyCloud kernel: [1222.946526] Out of memory: Kill process 9678 (apache2) score 23 or sacrifice child
	Line 1269: Dec 3 19:53:14 WDMyCloud kernel: [1254.510961] Out of memory: Kill process 9676 (apache2) score 23 or sacrifice child
	Line 1355: Dec 3 19:53:21 WDMyCloud kernel: [1260.196251] Out of memory: Kill process 9697 (apache2) score 23 or sacrifice child
	Line 1439: Dec 3 19:53:40 WDMyCloud kernel: [1278.458992] Out of memory: Kill process 9699 (apache2) score 23 or sacrifice child
	Line 1521: Dec 3 19:53:41 WDMyCloud kernel: [1281.059326] Out of memory: Kill process 9662 (apache2) score 23 or sacrifice child
	Line 1617: Dec 3 19:53:55 WDMyCloud kernel: [1295.031725] Out of memory: Kill process 9686 (apache2) score 22 or sacrifice child
	Line 1703: Dec 3 19:54:12 WDMyCloud kernel: [1312.160992] Out of memory: Kill process 9698 (apache2) score 22 or sacrifice child
	Line 1788: Dec 3 19:54:13 WDMyCloud kernel: [1313.589650] Out of memory: Kill process 9716 (apache2) score 22 or sacrifice child
	Line 1872: Dec 3 19:54:15 WDMyCloud kernel: [1314.823555] Out of memory: Kill process 3844 (rpcbind) score 1 or sacrifice child

 so RPCBind gets killed and then thats it, no more NAS box…

This to me appears to be a bug, yet again…

I will keep testing with:

  1. the media scanning turned off
  2. the usb 3.0 drive disconnected

and see if I still get the same issue.

Note: to reboot, connect via ssh and issue:

shutdown -r now

11

After further testing it appears to be an issue with the USB 3.0 connected drive.

If I run without the external USB 3.0 drive it will remain stable, as soon as I plug in the external drive it will crash after 20 to 40 minutes.

12

I had been running my drive since day one at version 3.x.x.139.
I messed around with it two days ago and broke Apache. Had to de brick using a stock .IMG I found of these forums. That .IMG turns out be version 4.x.x.413.
Ive also started to experience this network connectivity loss now for the time since owning the drive.
In my case its not ping able, so that in turns results in no ssh and no dashboard…

I can manually revert the fw to my preferred version via ssh without formatting the data partitions right?

13

Had that problem before but after disabling all features I’m not using it seems to stop bugging me, I’m on v04.01.02-417 right now but problem gone earlier.

The only thing which still make me think of trying v3 is NFS which freeze if you try to download anything, but I’m not sure if v3 doesn’t have same issue.

Regarding downgrade, take a look here: http://community.wd.com/t5/WD-My-Cloud/Firmware-downgrade/m-p/693892/highlight/true#M9268