Hmmm… Slipping down the thread order. I notice the pin is at an angle, whereas the firmware release notice has a vertical pin…
I appreciate this post, I want to start there. But there has to be something said about the ’ 1 2 3 easy’ setup advertising. It just isn’t working out that way. I’ve had nothing but issues with this thing since I purchased it and even had it partially working for a minute, but then it has completely hosed up after I decided to upgrade the firmware to resolve the actual cloud services I was still having.
Basically for $200, I have purchased an IT project that does nothing but frustrate me and yet to be resolved.
This post illustrates the same thing. I don’t want to RMA either, I want to use my knowledge to resolve the issues, but when does it not become worth it? Should I have not expected it to be as easy? God forbid my folks or some other person I know obtaining one of these…they’d be completely lost. If not because of being able to resolve one issue only to run into the next.
And even if I do resolve all of my problems, eventually. Will I ever be able to get it to work with our Chromebook…which serves as our entertainment center? That is a whole other project. I’ve been buying WD hard drives for over 15 years now but I’ll turn my back on them if I find a better wireless cloud hard drive back up solution after this experience.
I’m not trolling, I am venting my frustration in actual praise for this post that seems to illustrate what I too am going through.
I wish everyone else good luck on your pursuit to get this product to actually work as advertised.
- Hoblit
If you can accept deleting all your data on it, I’d suggest doing a quick factory restore, then use the ‘Mobile Devices’ setup path shown in the Quick Installation Guide. This uses the Dashboard to setup the device, which I find more logical and gives more control than the automated route. Then use your router’s UI to set an infinite DHCP address timeout for the device.
I’m not saying this cures all ills, but it allowed me to set up a new device within ten minutes of taking it out of the box. I find that much closer to the ‘easy 1-2-3 setup’ on the box. Setting up Twonky is a different matter, so I wrote an FAQ for that…
The manual is worth reading, if you haven’t. Ignore all the stuff in the first chapters about downloading a whole bunch of WD software; NONE of it is needed for configuration and use as a local file and media server. Get it working as a basic file server, stick data on it, wait for it to finish mucking about with indexing and thumbnailing.
Then think about backups (you can use software other than WD’s to do that; it’s just a NAS, after all).
Then think about setting up remote access.
Take things one step at a time, and slowly build up understanding of how the unit works, and what services you have running on it. WD’s setup process is an all at once, automated setup, with no user learning. So what does the user do when something goes wrong…? They’re stumped.
1 Like
Raphael,
Thanks for your continued offering of assistance to the MyCloud community. Speaking for myself at least, I have learned much from reading your many posts.
Raphael and others,
I have been the trainer of a 4TB MyCloud for the past two weeks. I am at my wit’s end in attempting to establish a robust unit with the primary objective of data backup. No DLNA, no family sharing, no remote access; just me, one user, attempting to have my backup data in a separate room from my computer. I send this request as my last attempt before wiping my unit and returning it.
For the record, I have been a computer user for 40 years since doing machine level programming of 8008 and 8080’s in the 1970’s. I consider myself reasonably computer literate but not savvy.
My environment has both the MyCloud and a MacBookPro (MBP) attached to the ethernet ports of my Gigabit router (netgear R6300). The MBP is connected via the super usb 3.0 port to an Anker Ethernet NIC dongle (I understand that this will limit my transfer rate to that of about usb 3.0), then via ethernet to the router. System preferences indicate a gigabit connection for the MBP. For the record, the MyCloud is on firmware 40.40.01-112.
Initial test transfers, MBP to a virgin MyCloud, indicated transfer rates of about 30MB/sec. Cool!, I thought.
Then I started setting up shares, doing some major transfers, Time Machine Backups and some other backups using Data BackUp3. I set up a 300 GB transfer (direct from MBP hard drive to MyCloud using finder) of images, mostly large png files of 100 MB or greater and went to bed. The next morning, the transfer was less than 25% of the 300 GB or somewhere in the neighborhood of an average 0.5 to 1.0 MB/sec. I stopped the transfer and for the next 4 hours listened to the continually processing of the MyCloud as I search forum after forum. Learning and learning.
To make a long story a little shorter… I did all the suggested work arounds:
- Set all Shares to Media Serving OFF.
- Turned OFF cloud access.
- Turned off DLNA and iTunes services.
- Then I performed a reboot of the MyCloud and crossed my fingers. No Change, still the continual background processing chatter and slow transfer rates of 0.5 to 1.0 MB/sec.
I then did the SSH thing…
- Turned on SSH in the dashboard, log out of the dashboard.
- Open the terminal program and successfully logged into the MyCloud via
SSH root@192.168.1.11; entered the password: welc0me;
It worked!
I felt empowered, ready to gain control of my beast! - Entered the 4 magic commands noted in many places in the forums:
/etc/init.d/wdmcserverd stop
/etc/init.d/wdphotodbmerferd stop
update-rc.d wdphotodbmergerd disable
update-rc.d wdmcserverd disable
Exited terminal and logged into the dashboard.
After a couple of minutes, not immediately, the background processing stopped. I performed another transfer test of a 225 GB folder of mostly png image files and the transfer completed in less than 1.5 hours, consistent with about a 40+ MB/sec transfer rate. Jump with joy! Success! Back to transferring files again…
Ah Poo! I hear the background processing again. Try rebooting, no help, still background processing. And the dashboard indicates “IDLE” for content scan status!!!
Current situation: I am experiencing the continued background processing (of something) that drags data transfer to a snail’s pace. The last test I just completed had a mix of pdf, jpg, png files ranging in size of a few to 100’s of MB each for a total transfer of 1.9GB. This transfer went from MBP HD to MyCloud via finder transfer to a mounted share. The results data…
took 1:10 min:sec to “prepare” for transfer
after 5 minutes: 157 MB of the 1.9GB had transferred for about a 0.5 MB/sec rate. Background processing is continuous.
So, sorry for such a long story, but before MyCloud re-becomes BestBuyCloud again, I thought I give some of you folks a chance to help me figure what I might be doing incorrectly or not doing. In advance, thanks for your help.
dave
1 Like
Well, you could use the usual unix tools to find out what is taking the CPU:
ps
top
Cpt,
thanks for your quick response. I would be happy to try some unix commands but do not know what to use? I am not a unix person, the SSH session was the first time I used it. I can follow a recipe but cannot create one. Can you post some commands I can enter?
dave
See the commands in the little grey box… ‘ps’ and ‘top’…
Google for details.
1 Like
cpt,
so I googled as suggested and performed both ‘ps’ and ‘top’
The output / response might as well be martian as far as I can read or interpret it.
top does say 91, 92 or 93 tasks, 2 or 1 running at the beginning of the response. The most active task has a PID of 12922 by root (I have no idea what this means).
‘ps’ responds with:
PID TTY TIME CMD
13303 pts/0 00:00:00 bash
13501 pts/0 00:00:00 ps
Again this is meaning less to me, but maybe someone can make something of it.
This is a consumer device???
dave
1 Like
Try ps -eaf This will display all processes running.
RAC
when I perform a ‘top’ command, the one task that continually shows with the highest usage is ‘du’; with PID 15021. Although, ‘kswapd0’ with PID 293 also has high usage.
In response to rac8006; here is the entire list of 90+ items vis ‘ps -eaf’. Is any of this useful to help understand the continual chatter?
WDMyCloud:~# ps -eaf
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 08:19 ? 00:00:10 init [2]
root 2 0 0 08:19 ? 00:00:00 [kthreadd]
root 3 2 0 08:19 ? 00:00:00 [cpu1_hotplug_th]
root 4 2 0 08:19 ? 00:00:10 [ksoftirqd/0]
root 7 2 0 08:19 ? 00:00:00 [migration/0]
root 8 2 0 08:19 ? 00:00:00 [migration/1]
root 10 2 0 08:19 ? 00:00:02 [ksoftirqd/1]
root 11 2 0 08:19 ? 00:00:00 [khelper]
root 230 2 0 08:19 ? 00:00:00 [sync_supers]
root 232 2 0 08:19 ? 00:00:00 [bdi-default]
root 234 2 0 08:19 ? 00:00:00 [kblockd]
root 240 2 0 08:19 ? 00:00:00 [ata_sff]
root 251 2 0 08:19 ? 00:00:00 [khubd]
root 257 2 0 08:19 ? 00:00:00 [md]
root 280 2 0 08:19 ? 00:00:00 [rpciod]
root 293 2 0 08:19 ? 00:00:49 [kswapd0]
root 294 2 0 08:19 ? 00:00:00 [fsnotify_mark]
root 295 2 0 08:19 ? 00:00:00 [nfsiod]
root 296 2 0 08:19 ? 00:00:00 [crypto]
root 334 2 0 08:19 ? 00:00:00 [scsi_eh_0]
root 337 2 0 08:19 ? 00:00:00 [scsi_eh_1]
root 340 2 0 08:19 ? 00:00:00 [kworker/u:2]
root 341 2 0 08:19 ? 00:00:00 [kworker/u:3]
root 351 2 0 08:19 ? 00:00:00 [comcerto_spi.1]
root 353 2 0 08:19 ? 00:00:00 [comcerto_spi.0]
root 386 2 0 08:19 ? 00:00:03 [btn_t]
root 403 2 0 08:19 ? 00:00:00 [a3gblink_t]
root 433 2 0 08:19 ? 00:00:00 [md1_raid1]
root 435 2 0 08:19 ? 00:00:00 [kjournald]
root 2068 1 0 08:20 ? 00:00:00 udevd --daemon
root 2184 2 0 08:20 ? 00:00:18 [kworker/1:2]
root 2476 2 0 08:20 ? 00:00:41 [pfe_ctrl_timer]
root 2529 2068 0 08:20 ? 00:00:00 udevd --daemon
root 2531 2068 0 08:20 ? 00:00:00 udevd --daemon
root 4096 1 0 08:20 ? 00:00:01 /sbin/rpcbind -w
root 4386 1 0 08:20 ? 00:00:00 dhclient -v -pf /run/dhclient.eth0.pid -lf /var/lib/
root 4614 1 0 08:21 ? 00:00:06 /usr/sbin/rsyslogd -c5
root 4713 1 0 08:21 ? 00:00:03 /usr/sbin/apache2 -k start
root 4740 1 0 08:21 ? 00:00:00 /sbin/mdadm --monitor --pid-file /run/mdadm/monitor.
root 5139 2 0 08:21 ? 00:00:01 [jbd2/sda4-8]
root 5199 1 0 08:21 ? 00:00:06 /usr/local/bin/upnp_nas_device -webdir /var/local/up
root 5211 2 0 08:21 ? 00:00:00 [ext4-dio-unwrit]
root 5888 1 0 08:21 ? 00:00:01 /usr/sbin/ifplugd -i eth0 -q -f -u0 -d5 -w -I
root 5932 1 0 08:21 ? 00:00:00 /usr/local/bin/wd-btnd /dev/input/button system 4 /u
root 6324 1 0 08:21 ? 00:00:00 /usr/sbin/cron
root 6685 2 0 08:21 ? 00:00:00 [knetatop]
root 6693 1 0 08:21 ? 00:00:03 /usr/bin/atopacctd /tmp/atopacct
root 6698 1 0 08:21 ? 00:00:50 /usr/bin/atop -a -w /var/log/atop/atop_current 60
root 6785 1 0 08:21 ? 00:00:00 /bin/sh /usr/local/sbin/monitorTemperature.sh
root 6844 1 0 08:21 ? 00:00:01 /bin/bash /usr/local/sbin/monitorio.sh
root 7003 2 0 08:21 ? 00:00:00 [lockd]
root 7004 2 0 08:21 ? 00:00:00 [nfsd]
root 7005 2 0 08:21 ? 00:00:00 [nfsd]
root 7006 2 0 08:21 ? 00:00:00 [nfsd]
root 7007 2 0 08:21 ? 00:00:00 [nfsd]
root 7008 2 0 08:21 ? 00:00:00 [nfsd]
root 7009 2 0 08:21 ? 00:00:00 [nfsd]
root 7010 2 0 08:21 ? 00:00:00 [nfsd]
root 7011 2 0 08:21 ? 00:00:00 [nfsd]
root 7015 1 0 08:21 ? 00:00:00 /usr/sbin/rpc.mountd --manage-gids
root 7035 1 0 08:21 ? 00:00:00 /bin/sh /etc/rc2.d/S20restsdk-serverd start
root 7036 7035 0 08:21 ? 00:00:21 /usr/local/restsdk/restsdk-server -device-kind sequo
root 7058 1 0 08:21 ? 00:00:03 /usr/sbin/nmbd -D
root 7062 1 0 08:21 ? 00:00:01 /usr/sbin/smbd -D
root 7077 7062 0 08:21 ? 00:00:00 /usr/sbin/smbd -D
root 7106 1 0 08:21 ? 00:00:00 /usr/sbin/winbindd
root 7111 7106 0 08:21 ? 00:00:00 /usr/sbin/winbindd
root 7138 1 0 08:21 ? 00:00:01 /usr/sbin/netatalk -F /etc/netatalk/afp.conf
root 7142 7138 0 08:21 ? 00:00:00 /usr/sbin/afpd -d -F /etc/netatalk/afp.conf
root 7143 7138 0 08:21 ? 00:00:00 /usr/sbin/cnid_metad -d -F /etc/netatalk/afp.conf
root 7222 1 0 08:21 ? 00:00:00 /usr/local/bin/mDNSResponderPosix -b -f //etc/nas/mD
root 7652 1 0 08:21 ? 00:00:00 /usr/local/bin/lld2d eth0
root 7679 1 4 08:21 ? 00:09:24 /usr/local/bin/wdnotifier
root 7759 1 0 08:22 ? 00:00:00 /usr/local/bin/wdAutoMounter
root 7809 1 0 08:22 ? 00:00:02 /usr/local/bin/onbrdnetloccomm -l 5
root 8062 1 0 08:24 ttyS0 00:00:00 /sbin/getty -L ttyS0 115200 vt100
999 8490 7142 6 08:30 ? 00:11:36 /usr/sbin/afpd -d -F /etc/netatalk/afp.conf
root 8535 7143 2 08:30 ? 00:04:53 /usr/sbin/cnid_dbd -F /etc/netatalk/afp.conf -p /Dat
root 8912 2 0 08:43 ? 00:00:15 [kworker/1:0]
root 10836 2 0 10:16 ? 00:00:08 [kworker/0:2]
root 13186 1 0 11:01 ? 00:00:00 /usr/sbin/sshd
root 13300 13186 0 11:02 ? 00:00:01 sshd: root@pts/0
root 13303 13300 0 11:02 pts/0 00:00:00 -bash
root 14078 2 1 11:21 ? 00:00:14 [flush-8:0]
root 14094 6785 0 11:21 ? 00:00:00 sleep 1800
root 14179 2 0 11:23 ? 00:00:01 [kworker/0:0]
www-data 14225 4713 0 11:23 ? 00:00:01 /usr/sbin/apache2 -k start
root 14319 2 0 11:25 ? 00:00:00 [flush-9:1]
www-data 14977 4713 0 11:33 ? 00:00:00 /usr/sbin/apache2 -k start
root 14986 6844 0 11:34 ? 00:00:00 xargs -0 -I {} getShareSize.sh {}
root 15017 14986 0 11:34 ? 00:00:00 /bin/bash /usr/local/sbin/getShareSize.sh /shares/Ba
root 15021 15017 25 11:34 ? 00:00:15 du -sbL /shares/BackUps
www-data 15023 4713 0 11:34 ? 00:00:00 /usr/sbin/apache2 -k start
root 15028 13303 0 11:35 pts/0 00:00:00 ps -eaf
WDMyCloud:~#
OK The process du is called from process 15017. This process is called from 14986 which is called from 6844 which is monitorio.sh. I’m not 100% clear why this is happening. But it appears that monitorio.sh is trying to maintain the proper
disk usage on the system as you are copying files? You could stop monitorio.sh while copying files then start it again. Rapheal might have a better idea why monitorio is calling getShareSize.sh so often. Since you only want to use the device as a backup. YOu have a few processes that don’t need to be running.
S20Restsdk-serverd
Netatalk
atop
Probem with atop is that it gets restarted every 8 hours. Not sure about the following processes:
onbrdnetloccomm
mDNSResponderPosix
winbindd
upnp_nas_device
Also why do you have so many nfsd processes?
What I did in the past was to stop each process and see if I could still access my files.
RAC
1 Like
well, for comparison, here’s my ps -eaf:
UID PID PPID C STIME TTY TIME CMD
root 1 0 0 Oct01 ? 00:01:37 init [2]
root 2 0 0 Oct01 ? 00:00:00 [kthreadd]
root 3 2 0 Oct01 ? 00:00:00 [cpu1_hotplug_th]
root 4 2 0 Oct01 ? 00:05:22 [ksoftirqd/0]
root 7 2 0 Oct01 ? 00:00:00 [migration/0]
root 8 2 0 Oct01 ? 00:00:00 [migration/1]
root 10 2 0 Oct01 ? 00:08:22 [ksoftirqd/1]
root 11 2 0 Oct01 ? 00:00:00 [khelper]
root 12 2 0 Oct01 ? 00:00:00 [kworker/u:1]
root 214 2 0 Oct01 ? 00:00:24 [sync_supers]
root 216 2 0 Oct01 ? 00:00:00 [bdi-default]
root 218 2 0 Oct01 ? 00:00:00 [kblockd]
root 224 2 0 Oct01 ? 00:00:00 [ata_sff]
root 235 2 0 Oct01 ? 00:00:00 [khubd]
root 241 2 0 Oct01 ? 00:00:00 [md]
root 264 2 0 Oct01 ? 00:00:00 [rpciod]
root 277 2 0 Oct01 ? 00:25:32 [kswapd0]
root 278 2 0 Oct01 ? 00:00:00 [fsnotify_mark]
root 279 2 0 Oct01 ? 00:00:00 [nfsiod]
root 280 2 0 Oct01 ? 00:00:00 [crypto]
root 318 2 0 Oct01 ? 00:00:00 [scsi_eh_0]
root 321 2 0 Oct01 ? 00:00:00 [scsi_eh_1]
root 324 2 0 Oct01 ? 00:00:00 [kworker/u:2]
root 335 2 0 Oct01 ? 00:00:00 [comcerto_spi.1]
root 337 2 0 Oct01 ? 00:00:00 [comcerto_spi.0]
root 386 2 0 Oct01 ? 00:09:19 [btn_t]
root 396 2 0 Oct01 ? 00:06:31 [a3gblink_t]
root 415 2 0 Oct01 ? 00:01:49 [md1_raid1]
root 417 2 0 Oct01 ? 00:00:15 [kjournald]
www-data 859 18287 0 17:01 ? 00:00:00 /usr/sbin/apache2 -k start
root 1945 1 0 Oct01 ? 00:00:01 udevd --daemon
root 2353 2 0 Oct01 ? 03:13:12 [pfe_ctrl_timer]
root 2408 1945 0 Oct01 ? 00:00:01 udevd --daemon
root 2409 1945 0 Oct01 ? 00:00:00 udevd --daemon
root 3044 2 0 Nov25 ? 00:00:49 [kworker/1:1]
root 3739 1 0 Oct01 ? 00:00:24 /sbin/rpcbind -w
root 3999 6748 0 Oct04 ? 00:00:00 /usr/sbin/winbindd
root 4051 1 0 Oct01 ? 00:02:59 /usr/sbin/rsyslogd -c5
root 4218 2 0 02:41 ? 00:00:09 [kworker/0:0]
root 4565 1 0 Oct01 ? 00:00:06 /sbin/mdadm --monitor --pid-file
root 4634 1 0 Nov12 ? 00:01:14 /usr/local/orion/communicationma
root 4791 2 0 Oct01 ? 00:00:10 [jbd2/sda4-8]
root 4828 2 0 Oct01 ? 00:00:00 [ext4-dio-unwrit]
root 5205 6794 0 Oct04 ? 00:00:00 /usr/sbin/cnid_metad -d -F /etc/
root 5760 1 0 Oct01 ? 00:05:22 /usr/sbin/ifplugd -i eth0 -q -f
root 5804 1 0 Oct01 ? 00:00:00 /usr/local/bin/wd-btnd /dev/inpu
root 6437 1 0 Oct01 ? 00:00:38 /bin/sh /usr/local/sbin/monitorT
root 6503 1 0 Oct01 ? 01:32:04 /bin/bash /usr/local/sbin/monito
root 6656 2 0 Oct01 ? 00:00:00 [lockd]
root 6657 2 0 Oct01 ? 00:00:00 [nfsd]
root 6658 2 0 Oct01 ? 00:00:00 [nfsd]
root 6659 2 0 Oct01 ? 00:00:00 [nfsd]
root 6660 2 0 Oct01 ? 00:00:00 [nfsd]
root 6661 2 0 Oct01 ? 00:00:00 [nfsd]
root 6662 2 0 Oct01 ? 00:00:00 [nfsd]
root 6663 2 0 Oct01 ? 00:00:00 [nfsd]
root 6664 2 0 Oct01 ? 00:00:00 [nfsd]
root 6668 1 0 Oct01 ? 00:00:00 /usr/sbin/rpc.mountd --manage-gi
root 6698 1 0 Oct01 ? 00:02:03 /usr/sbin/nmbd -D
root 6702 1 0 Oct01 ? 00:03:27 /usr/sbin/smbd -D
root 6712 6702 0 Oct01 ? 00:00:34 /usr/sbin/smbd -D
root 6748 1 0 Oct01 ? 00:00:23 /usr/sbin/winbindd
root 6752 6748 0 Oct01 ? 00:00:39 /usr/sbin/winbindd
root 6794 1 0 Oct01 ? 00:04:30 /usr/sbin/netatalk -F /etc/netat
root 6796 6794 0 Oct01 ? 00:00:09 /usr/sbin/afpd -d -F /etc/netata
root 6873 1 0 Oct01 ? 03:15:27 /usr/local/bin/mDNSResponderPosi
root 7293 1 0 Oct01 ? 00:01:24 /usr/sbin/cron
www-data 7437 18287 0 18:35 ? 00:00:00 /usr/sbin/apache2 -k start
root 7463 1 0 Oct01 ? 00:44:55 /usr/local/bin/wdnotifier
root 7549 1 0 Oct01 ? 00:00:00 /usr/local/bin/wdAutoMounter
root 7895 1 0 Oct01 ttyS0 00:00:00 /sbin/getty -L ttyS0 115200 vt10
root 10236 2 0 04:00 ? 00:00:07 [kworker/0:1]
kevin 10351 6702 2 19:22 ? 00:01:56 /usr/sbin/smbd -D
root 10359 2 0 19:22 ? 00:00:00 [flush-9:1]
www-data 10499 18287 0 19:23 ? 00:00:00 /usr/sbin/apache2 -k start
root 11675 1 0 Nov25 ? 00:00:00 /usr/sbin/sshd
root 14086 6702 0 20:12 ? 00:00:17 /usr/sbin/smbd -D
root 16453 6437 0 20:42 ? 00:00:00 sleep 1800
root 17012 6503 0 20:50 ? 00:00:00 sleep 60
root 17013 11675 3 20:51 ? 00:00:00 sshd: root@pts/0
root 17016 17013 0 20:51 pts/0 00:00:00 -bash
root 17025 17016 0 20:51 pts/0 00:00:00 ps -eaf
root 17600 1 0 Nov23 ? 00:00:00 dhclient -v -pf /run/dhclient.et
root 17799 1 0 Nov23 ? 00:00:04 /usr/local/bin/lld2d eth0
root 18010 1 0 Nov23 ? 00:00:00 /usr/local/twonkymedia-7/twonkys
root 18013 18010 0 Nov23 ? 01:59:44 /usr/local/twonkymedia-7/twonkys
root 18287 1 0 Nov23 ? 00:00:42 /usr/sbin/apache2 -k start
root 19013 1 0 Nov23 ? 00:05:22 /usr/local/bin/upnp_nas_device -
root 19699 1 0 Nov23 ? 00:00:45 openvpn /usr/local/orion/openvpn
root 24900 2 0 Nov22 ? 00:01:31 [kworker/1:0]
RAC,
what is a ‘nfsd’ process?
Cpt.,
where is the ‘little grey box’?
dave
Folks,
I really, really appreciate your attempts at helping me. But most of it is just flying over my head. Perhaps, I have purchased an item that has more features than I require and more futzing around than I want to do to remove those features. Maybe just mirroring my MyBook 5TB with a duplicate unit and leaving it in my office is the way for duplicate backups. I simply wanted to do a mirroring but have it reside in a different room in my house.
I’m still hanging in here for now.
dave
This is a little grey box - it's a page format
use the </> icon on the compose bar to apply
As for your problems with Linux, well, yes, the MyCloud is a consumer device, and you’re not really supposed to have to tinker ‘under the hood’ with the Linux OS. But, for people who have an idea of what they are doing (I only tinker), it’s a useful way of figuring out what is going on when it doesn’t work properly. It really shouldn’t be necessary, if the thing worked properly. But it doesn’t…
Comparing your process (PID: Process ID) with mine, you have these extras:
/bin/bash /usr/local/sbin/getShareSize.sh
/usr/sbin/afpd -d -F /etc/netatalk/afp.conf
/usr/sbin/cnid_dbd -F /etc/netatalk/afp.conf -p /Dat
[flush-8:0]
[flush-9:1]
du -sbL /shares/BackUps
xargs -0 -I {} getShareSize.sh {}
Which backs up what rac8006 said
nfsd?
Google is your friend. Really.
It’s an NFS daemon - a Network File Server task.
Have you tried a System Only Restore…?
Have a look at Mirrorfolder software. It will create an effective and simple mirror using your computer and an external drive. I’ve been using it since 2007.
Paul
cpt,
Performed a system only restore. After the restore did the following.
Reset my admin user (me) and Password. Changed all Shares permission back to public share OFF. Changed all shares back to Media Serving OFF. Turned Media Streaming OFF. iTunes server OFF. Cloud access OFF. BTW: a new TimeMachineBackup share was created by the restore, renaming my old one as TimeMachineBackup2.
Then did the ‘SSH - 4 commands’ thing.
And lastly, did a reboot.
First transfer of 13GB went at about 10MB/sec. Significantly higher than the 0.5 - 1.0 MB/sec of the previous ‘standard’ case. But still under the initial 30 MB/sec I obtained on the virgin box. Then…
Same background chatter starts up again. Do a few more file transfers with rates ranging from 12.5 to 14.6 MB/sec. Maybe I should be happy with this?
Still hanging in there.
Just tried a WIFI transfer, seeing that this will be my normal mode of connection after my initial data is loaded and first backups are performed on MyCloud.
With the same file transfers I am getting 4.3 to 5.6 MB/sec transfer rates. Only a factor of 3 less than the direct gigabit ethernet connection. Again, I ask: Maybe I should be happy (satisfied) with this?
dave
I purchased my product a couple of days ago, and I could not believe the lack of intuition displayed in creating the user’s manual and the quick start guide. I consider myself above average in following directions and instructions. I’ve never had such a hard time setting up an electronic product until I tried the WD my cloud. After spending a couple of days going back and forth with the installation process by going through a manual that does not follow a logical sequence and does not include intuitive instructions, I’m ready to return this product. Although this thread seems to provide most the of the solutions to the problems I encountered, it still feels like I’m taking an online class. If an electronic product does not allow for an easy plug and play experience, the manual should have instructions with an easy-to-follow sequence. The instructions need to allow the customer to have the product up and running without having to go back and forth different pages or sources outside the manual. For example, WD Sync instructions need to be easily integrated in the manual. When I saw the online help instructions to WD Sync, it shows the company did not want to spend the money in creating an easy-to-do guide. As a technical writer, the main advice I can give you is to divide the manual based on tasks that build upon each other and explain key concepts for somebody that just found out about personal cloud storage. I’m purchasing the Lacie Cloudbox as it has been touted for the easy set up process. The company might want to find out what they’re doing if they want new learners and customers of personal iCloud storage to stay with the WD line of products. Otherwise, you will only get buyers with the same knowledge base as the good gentleman who started this thread post.
Ah, someone who talks sense; that’s exactly the approach I’ve suggested a number of times in the past…
I’ve concluded that the manual was cobbled together from at least two parts; one written by the automated setup team, one written by the Dashboard team. The former is very bad. The latter isn’t so bad. But both seem to be written by the development teams, so they ‘know too much’, and forget that their target audience know nothing about the device, and may not know much about computers or networking. Breaking Rule #1 of writing consumer technical manuals.
https://community.wd.com/t/improve-the-user-manual/97202
And finally…
1 Like
