Very slow transfer

My Cloud OS 3 Personal & Network Attached Storage My Cloud
1

When I bought the mycloud device, I though its speed would be as normal as that of accessing such other cloud applications like dropbox or onedrive.

What is happening with me is terrible. I am trying to copy my data (around 200 gigabytes) into the mycloud device. Normally, when copying those files into another hard drive, it would take me around two hours maximum.

I have been waiting for the copying to finish for almost 13 hours. It still indicates that only less than half the data has so far been copied.

Worse, the copying process is slowing down my internet connection. 

Although I am copying the files by connecting the PC to the modem and the mycloud to the modem (not remote access), the speed is very very slow. The modem’s internet speed is also affected. It was 16 migabit but now it is 3 migabit because of the transfer.

I checked out older posts about slow speed. None of them worked for me.

So, do you think that the mycloud that I purchased is defective?

2

Since the update to firmware 4.0 my drive has become ULTRA SLOW:

Copying a single photo (with a size of about 150 KByte only), that needed with the previous version about a tenth of a second, now needs this time on my windows 8.1 PC:

  • 10 seconds where nothing visible happens (with the exception of an hour glass at the cursor)

  • 10 further seconds, where windows tells me to calculate “the remaining time”

  • 10 seconds where nothing happens

  • 3 seconds for the upload

Unbelievable!

The same unbearable delays happen, when I try to connect to the the web interface of the drive:

  • 60 seconds !: nothing, white screen in browser, while the status bar of the browser, showing the success of loading the page, hangs in the middle

  • the first black screen with the logo apperas - for the next 45 seconds !

  • the additional text “Access to WD My Cloud” appears and for the next minute again nothing happens

  • then the start page appears, but with empty sub-frames

  • after 45 seconds the firmware version appears, after further 60 seconds “Diagnose OK” appears, and so on…

For me this looks like missing RAM. Maybe all of it is “stolen” by a very poor programmed indexing feature.

I guess, that indexing my 300.000 photos makes the drive running out of memory (RAM), because of a very poor programming. Maybe the programmers forgot a command to release RAM after indexing a media file?

If possible I would like to go back to the previos version - doing a hard reset and losing all settings would not be a problem to me

3

When calling the “top” command, it seems that RAM is NOT the problem, as I was guessing before. Maybe it’s the cpu load of twonkyserver together with “convert”, whatever this is (process to build preview pics?)

top - 06:56:22 up 2 days,  2:39,  1 user,  load average: 5.52, 6.50, 8.45
Tasks:  93 total,   2 running,  91 sleeping,   0 stopped,   0 zombie
%Cpu(s): 46.9 us,  4.5 sy, 36.5 ni,  0.0 id, 11.9 wa,  0.0 hi,  0.2 si,  0.0 st
KiB Mem:    232448 total,   182720 used,    49728 free,     2816 buffers
KiB Swap:   500672 total,   137600 used,   363072 free,    18304 cached

  PID USER      PR  NI  VIRT  RES  SHR S  %CPU %MEM    TIME+  COMMAND
22593 root      20   0 73664  42m 2368 S  93.5 18.7  10:24.24 twonkyserver
24707 root      28   8 32448  27m 4672 R  35.0 12.2   0:01.09 convert
23543 www-data  20   0 58560  13m 6592 S   1.0  6.1   0:01.65 apache2
24313 root      20   0  4544 2304 1216 R   0.6  1.0   0:01.28 top
  277 root      20   0     0    0    0 S   0.3  0.0   9:47.07 kswapd0
 2360 root      20   0     0    0    0 D   0.3  0.0  17:50.42 pfe_ctrl_timer
 6429 root      20   0 71232 2176 1088 S   0.3  0.9   4:42.74 upnp_nas_device
 6533 root      20   0 36608 4736 2432 S   0.3  2.0 903:04.40 wdmcserver
13648 root      20   0     0    0    0 S   0.3  0.0   0:38.40 kworker/0:0
17009 root      20   0     0    0    0 S   0.3  0.0   0:13.38 kworker/1:2
    1 root      20   0  2752  640  384 S   0.0  0.3   0:46.74 init
    2 root      20   0     0    0    0 S   0.0  0.0   0:00.02 kthreadd
    3 root      20   0     0    0    0 D   0.0  0.0   0:00.00 cpu1_hotplug_th
    4 root      20   0     0    0    0 S   0.0  0.0   1:27.71 ksoftirqd/0
    7 root      rt   0     0    0    0 S   0.0  0.0   0:00.00 migration/0
    8 root      rt   0     0    0    0 S   0.0  0.0   0:00.00 migration/1
   10 root      20   0     0    0    0 S   0.0  0.0   0:49.41 ksoftirqd/1
   11 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 khelper
   12 root      20   0     0    0    0 S   0.0  0.0   0:00.00 kworker/u:1
  214 root      20   0     0    0    0 S   0.0  0.0   0:02.57 sync_supers
  216 root      20   0     0    0    0 S   0.0  0.0   0:00.03 bdi-default
  218 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 kblockd
  224 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 ata_sff
  235 root      20   0     0    0    0 S   0.0  0.0   0:00.21 khubd
  241 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 md
  264 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 rpciod
  278 root      20   0     0    0    0 S   0.0  0.0   0:00.00 fsnotify_mark
  279 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 nfsiod
  280 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 crypto
  318 root      20   0     0    0    0 S   0.0  0.0   0:00.15 scsi_eh_0
  321 root      20   0     0    0    0 S   0.0  0.0   0:00.00 scsi_eh_1
  324 root      20   0     0    0    0 S   0.0  0.0   0:00.03 kworker/u:2
  335 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 comcerto_spi.1
  337 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 comcerto_spi.0
  370 root      -2   0     0    0    0 D   0.0  0.0   1:24.75 btn_t
  380 root      -2   0     0    0    0 S   0.0  0.0   0:00.00 a3gblink_t
  415 root      20   0     0    0    0 S   0.0  0.0   0:05.12 md1_raid1
  417 root      20   0     0    0    0 S   0.0  0.0   0:01.26 kjournald
 1951 root      20   0  4160   64   64 S   0.0  0.0   0:00.42 udevd
 2415 root      20   0  4096   64   64 S   0.0  0.0   0:00.07 udevd
 2416 root      20   0  4096   64   64 S   0.0  0.0   0:00.01 udevd
 3791 root      20   0  3328  640  256 S   0.0  0.3   0:18.53 rpcbind
 4006 root      20   0 32384 1856  960 S   0.0  0.8   1:15.73 rsyslogd
 4095 root      20   0 56384 1408  768 S   0.0  0.6   1:10.62 apache2
 4159 root      20   0  3200  448  448 S   0.0  0.2   0:01.28 mdadm
 4282 root      20   0     0    0    0 S   0.0  0.0   0:33.92 flush-8:0
 4315 root      20   0     0    0    0 S   0.0  0.0   1:08.81 jbd2/sda4-8
 4318 root       0 -20     0    0    0 S   0.0  0.0   0:00.00 ext4-dio-unwrit
 4934 root      20   0  2112  448  192 S   0.0  0.2   0:39.50 ifplugd
 4978 root      20   0  2112   64   64 S   0.0  0.0   0:00.00 wd-btnd
 5655 root      20   0  3584  640  640 S   0.0  0.3   0:02.84 monitorTemperat
 5714 root      20   0  3520  640  640 S   0.0  0.3   1:50.52 monitorio.sh
 5884 root      20   0     0    0    0 S   0.0  0.0   0:00.00 lockd
 5885 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 5886 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 5887 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 5888 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 5889 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 5890 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 5891 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 5892 root      20   0     0    0    0 S   0.0  0.0   0:00.00 nfsd
 5896 root      20   0  4352   64   64 S   0.0  0.0   0:00.00 rpc.mountd
 5926 root      20   0  7552 1088  704 S   0.0  0.5   1:09.26 nmbd
 5930 root      20   0 35008  704  704 S   0.0  0.3   0:21.25 smbd
 5942 root      20   0 35008  768  768 S   0.0  0.3   0:15.22 smbd
 5965 root      20   0  4864   64   64 S   0.0  0.0   0:00.01 vsftpd
 5977 root      20   0 28352  512  512 S   0.0  0.2   0:07.76 winbindd
 5981 root      20   0 28352  640  640 S   0.0  0.3   0:07.29 winbindd
 6013 root      20   0  6592  576  320 S   0.0  0.2   0:45.58 netatalk
 6015 root      20   0  9920   64   64 S   0.0  0.0   0:09.80 afpd
 6092 root      20   0  2112  576  576 S   0.0  0.2   0:00.40 mDNSResponderPo
 6610 root      20   0 39680  576  576 S   0.0  0.2 579:33.03 wdphotodbmerger
 6641 root      20   0  3520 1024  576 S   0.0  0.4   0:16.25 cron
 6669 root      20   0  2112  512  192 S   0.0  0.2   0:12.80 lld2d
 6852 root      20   0 12800 1856  960 S   0.0  0.8  11:40.03 wdnotifier
 6942 root      20   0  3840   64   64 S   0.0  0.0   0:00.16 wdAutoMounter
 7391 root      20   0  2944   64   64 S   0.0  0.0   0:00.02 getty
 7475 root      20   0 48832   64   64 S   0.0  0.0   0:01.76 winbindd
 8148 root      20   0  6656   64   64 S   0.0  0.0   0:00.05 cnid_metad
16744 root      20   0     0    0    0 S   0.0  0.0   0:17.51 kworker/0:1
19264 root      20   0     0    0    0 S   0.0  0.0   0:00.01 flush-9:1
21657 root      20   0  9024  512  512 S   0.0  0.2   0:00.01 sshd
21751 root      20   0 13440 1920 1216 S   0.0  0.8   0:00.73 sshd

4

I’ll stop this now - because now everything has become SO SLOW again -  and it’s obvious, that it’s NOT the CPU load of twonkyserver or “convert”, nor the amount of used RAM of both processes. The values of those processes are very low at the current time.

So the error must be somehting else… and I give up.

Hope WD will find it!

5

It has nothing to do with the Ram. My ram is 8 GB and only around 2.5 is used out of it during the operation. It seems there is a malfunction in the sameWD cloud. My problem is that I bought it from another country and cannot even replace it.

6

I have the same problem 2tb of data = 60 hours and counying. any ideas anyone

7

I had previously an ordinary cable connecting the computer to the modem. Now I replaced it with CAT6. The connection has become faster though the ethernet connection is still 100mbps.

The shop that made for the me the cable has a Seagate cloud system. It is a three-year old 1.5 TB cloud. But, I noticed that it is incredibly fast even though it is connected through a limited capacity modem-router.

I hope that technical support will give us a solution for this issue. Otherwise, perhaps we need to seek other alternatives instead of wasting time.

There is something that needs to be said. In 1997, when I bought my first computer, every shop here in Jordan was boasting in their offers that they give a computer with Western Digitial caviar hard disk. I very strongly trust WD products and hope the technical support will not let me down with this product.

8

My problem started after I did the update (nothing else changed and the speed was fine immediately before I clicked on the update).

Looked around on the web and found I’m not the only one. I then  turned off DLNA etc - still no difference (not that I should have to start playing around with such things). Rebooted - no difference.

Left it on overnight and it was back to ‘normal’ next morning.

48 hours later, I turn it on and it’s back to snail pace transfer rates :angry:

NOT GOOD ENOUGH.

Note: I have no interest in being a techo to get a COTS product working!

P.S. Does anyone actually test these things!?!  :confounded:

9

After testing and experimenting, I got the following conclusions:

  1. The speed of Mycoud depends on the speed of the whole computer system. This includes:

a. The operating system

b. The random access memory RAM

c. The modem and router models

d. The cable

e. The internet download + upload speeds

  1. In order to make the best use of Mycloud, I believe the following requirements must be met:

a. The RAM should not be less than 8GB.

b. In my casem I use a PC. A PC (from experiment) needs to be a Windows 64 bit. This is faster than 32 and it recognises a RAM bigger than 4GB. If you use WIndows 32bit, it will not recognise more than 2 or 2.5 GB even if you install a big RAM. You can still find a patch in the internet that makes Windows 32 recognise a RAM of 8GB.

In my case to solve the speed issue, my windows 64 plus 8GB RAM are essential requirements.

c. The Ethernet card must be a good one. In my case, I have one built-in Atheros. I was told that it supports a 1GB speed but apparantely it does not as the network speed stands at 100mbps. I have not been able yet to solve this issue. I installed the drivers again and tried several other solutions but none worked. Anyways, for the time being, 100mbps is good.

d. The cable. It never occured to me that whatever advnaced system you have, you will not be able to do anything without a good cable! I used to have the CAT5 cable connecting my computer with the modem. But, when I changed it and put a CAT6 cable, the speed increased significantly.

e. The modem and router. I think this must be an advnaced device that supports high speed. My modem is ZTE ZXHN H108N. I have tried to seek infromation to see what speed it supports but there has been no answer from my internet provider or from the manufacutrer (ZTE).

f. Internet speed. Here is the main problem. My internet connection’s speed is: 16mbps for downloads and 0.7mbps for uploads. This will (at least theoretically) hinder the speed of getting in and out of the Mycloud. If I am using the device remotely, it means that my computer will need to get a high speed and the connection of my cloud at home should also have a high speed. This complicates the matter and makes it difficult to ensure high speed of transfer from/into mycloud.

g. By assuring the above requirments, I found that the use of mycloud in my computer through the local network at home is very very fast. This is not the case when the device is remotely accessed.

This information was not obious for me when I purchased the device. Even the manual does not say that. It was only through experiment that I found out all of this. Anyways, it is still legitimate to ask other users if they are having the same problem or not.

My recommendation for Western Digital is to collect the reported problems and:

  1. Sort them out for the next generations of mycloud (if applicable) and

  2. Introduce the fixes into the manual for the use of the perplexed user.

10

 

KNags

I am curious to know if your problem is the same as mine. May I ask you to share with me the following:

a. Type of modem/router

b. Internet download and upload speed

c. Type of cable connecting your computer to the router/modem.

d. Type of cable connecting the WD cloud drive to the router/modem

11

Netgear MBRN3000 3G Wireless Broadband, Internet speed varies (always did), 

Ethernet cable between MyCloud and router. Wireless connection to HP Laptop 4gb RAM

However, none of that matters in my case. I’ve had this setup for months and run xx GB file transfers and syncs  to/from MyCloud device without any issues.

I was accessing the drive freely until right up until I ran that firmware update v04.00.00-607. Now opening up a 100k word document takes over a minute.

P.S. It seems to be back to normal now - 2 hours after I turned it on. (Until next time?)