Absolutely terrible! Absolutely Unusable!

[Ralphael]

@Bill_S please pass this to your programmers to have them work on it ASAP!! (yeah right…)

The scans are your #1 problem leading to complete customer dissatisfaction and if you don’t fix this, sooner or later, probably sooner, you won’t have any satisfied customers at all…

So I bought a 3rd Cloud today… and I left all the services running as is… managed to set everything up, connected and mapped to my Mac mini. Was running fine since it is an empty system. Copied one video file to it and I was surprise to see that the dashboard reported the 1 video immediately.

The chaos all started when I plugged in a USB drive that contains something like a quarter million files; about a 100GB of ebooks, jpegs, etc. The surprising thing was my Passport drive was recognized and mounted (FW04.04.01-112) without problems, but I knew it was trouble as soon as I felt the sluggishness however since this was my new test drive I would let it weather it out.

I kept myself logged in via SSH and every so often I would issue a ps -ALL to see how things were doing as I could hear the attached USB drive thrashing…

For some reason I decided to see if I could eject my USB drive… and that is when I noticed that

• no dashboard response, exited and attempted to view dashboard but got a total blank page.
• the mounted cloud drive disconnected when I tried to copy some files to it.
• was unable to mount the drive again
• attempted to stop the wdmcserverd, but SSH was barely responsive. Managed to issue one stop command before SSH locked
• Once wdmcserverd was stop, all SSH response returned but still no Dashboard, nor the ability to mount. The drive had disappeared.

This is what your customers will see if they mount a USB drive, full of files, to the Cloud; the system eventually locks.

This is the same/similar problem that occurred two years ago and you never fixed it.

Grab a USB drive and fill it with photos, ebooks approximately a quarter million… seriously that is the amount of files that I have just for epubs, another quarter million for photos.

Yes the workaround is to turn off “Media Serving” but how many of your customer will know how to do that?

I think it is time for your programmers to find another solution to create thumbnails, indexes and databases of the media.

This one problem is causing:

1. slow and unresponsive drive
2. slow or blank dashboard
3. disconnection, drop outs
4. total system lock

and yet we know, without the scans, your cloud still works except we don’t have thumbnails. I think it is fair to have the thumbnails or index built at the time of query?

or have a button that says scan now… under the user control so they can turn on and off the scans. Scans should be by directory not by shares as I do want to have Cloud access, just not everything thumbnails or indexed. I have photo directories that would be nice to have thumbnails but the other photo directories do not.

So figure it out…

Do something… really…

Every time I hit a little brick wall, it all adds up; all those little things.

I don’t know what to do with 3 x 4TB clouds but since they contain a 4TB red drive, it is tempting to pick up a QNap drive and simply raid them creating a single 8TB raid 5 volume. This thought has passed my mind constantly over the last 2 years.

---

Edit: So one of the other thing I was testing was the eventual sleep that you promised that once the scans were done, the device would sleep. I have less then a dozen files on the device, one movie file and my supporting script directory. I left it alone all evening and almost all night till 4am until I couldn’t stand the fact that my new cloud did not sleep. Remember that this Cloud is running on the latest firmware 04.04.01-112 and restsdk is still not patched.

Here is the log file:

2015-11-09T20:54:25.285169-08:00 di=k6NucgsedY notice logger: Restarting services
2015-11-09T22:20:37.244854-08:00 di=k6NucgsedY notice logger: exit standby after 8 (since 2015-11-09 22:20:29.686867002 -0800)
2015-11-09T22:30:56.477530-08:00 di=k6NucgsedY notice logger: exit standby after 7 (since 2015-11-09 22:30:49.266867002 -0800)
2015-11-09T22:41:55.083642-08:00 di=k6NucgsedY notice logger: exit standby after 47 (since 2015-11-09 22:41:08.676867002 -0800)
2015-11-09T22:58:06.502868-08:00 di=k6NucgsedY notice logger: exit standby after 359 (since 2015-11-09 22:52:07.266867002 -0800)
2015-11-09T23:08:26.137226-08:00 di=k6NucgsedY notice logger: exit standby after 8 (since 2015-11-09 23:08:18.646867002 -0800)
2015-11-09T23:34:27.844150-08:00 di=k6NucgsedY notice logger: exit standby after 888 (since 2015-11-09 23:19:39.646867002 -0800)
2015-11-10T00:01:10.444271-08:00 di=k6NucgsedY notice logger: exit standby after 990 (since 2015-11-09 23:44:39.986867002 -0800)
2015-11-10T00:01:42.854078-08:00 di=k6NucgsedY notice logger: Rotated atop, atop_size=14631952 atop_upload_size=903298
2015-11-10T00:13:32.885850-08:00 di=k6NucgsedY notice logger: exit standby after 7 (since 2015-11-10 00:13:25.346867002 -0800)
2015-11-10T00:30:10.492607-08:00 di=k6NucgsedY notice logger: exit standby after 386 (since 2015-11-10 00:23:44.926867002 -0800)
2015-11-10T00:42:33.241600-08:00 di=k6NucgsedY notice logger: exit standby after 8 (since 2015-11-10 00:42:25.726867002 -0800)
2015-11-10T01:01:54.155815-08:00 di=k6NucgsedY notice logger: exit standby after 549 (since 2015-11-10 00:52:45.326867002 -0800)
2015-11-10T01:17:10.413106-08:00 di=k6NucgsedY notice logger: exit standby after 304 (since 2015-11-10 01:12:06.266867002 -0800)
2015-11-10T02:01:20.562516-08:00 di=k6NucgsedY notice logger: exit standby after 2038 (since 2015-11-10 01:27:22.446867002 -0800)
2015-11-10T02:53:13.173649-08:00 di=k6NucgsedY notice logger: exit standby after 2501 (since 2015-11-10 02:11:32.486867002 -0800)
2015-11-10T03:00:03.408793-08:00 di=k6NucgsedY notice getNewFirmwareUpgrade.sh: begin script: immediate send_alert auto
2015-11-10T03:00:03.481344-08:00 di=k6NucgsedY notice getNewFirmwareUpgrade.sh: http://support.wdc.com/nas/list.asp?devtype=sq&devfw=04.04.01-112&devlang=eng&devsn=&auto=0&devid=*****
2015-11-10T03:00:05.933675-08:00 di=k6NucgsedY notice logger: ga_collect: dryrun=0, first=1
2015-11-10T03:00:25.732887-08:00 di=k6NucgsedY notice logger: ga_collect: dryrun=0, first=0
2015-11-10T03:01:01.834127-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/", "capacityK":1968336, "totalK":659264, "partition":"rootfs" }
2015-11-10T03:01:01.880774-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/", "capacityK":1968336, "totalK":659264, "partition":"/dev/root" }
2015-11-10T03:01:01.913407-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/run", "capacityK":40960, "totalK":3904, "partition":"tmpfs" }
2015-11-10T03:01:01.952100-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/run/lock", "capacityK":40960, "totalK":64, "partition":"tmpfs" }
2015-11-10T03:01:01.978658-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/dev", "capacityK":10240, "totalK":0, "partition":"tmpfs" }
2015-11-10T03:01:02.003643-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/run/shm", "capacityK":5120, "totalK":0, "partition":"tmpfs" }
2015-11-10T03:01:02.023366-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/tmp", "capacityK":102400, "totalK":3264, "partition":"tmpfs" }
2015-11-10T03:01:02.051809-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/var/log", "capacityK":40960, "totalK":10048, "partition":"ramlog-tmpfs" }
2015-11-10T03:01:02.071494-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"/DataVolume", "capacityK":3841069352, "totalK":1199592, "partition":"/dev/sda4" }
2015-11-10T03:01:02.211121-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"dataSize", "mountPoint":"93de3f6b1c6f991dd33d2212f3ed9055/var/media/", "capacityK":3906546640, "totalK":1771440, "partition":"/dev/sdb2" }
2015-11-10T03:01:02.259823-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"rootfs", "inode":125184, "iused":25169, "mountPoint":"/" }
2015-11-10T03:01:02.279219-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"/dev/root", "inode":125184, "iused":25169, "mountPoint":"/" }
2015-11-10T03:01:02.298846-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":247, "mountPoint":"/run" }
2015-11-10T03:01:02.318624-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":5, "mountPoint":"/run/lock" }
2015-11-10T03:01:02.338317-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":176, "mountPoint":"/dev" }
2015-11-10T03:01:02.358258-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":1815, "iused":2, "mountPoint":"/run/shm" }
2015-11-10T03:01:02.377697-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"tmpfs", "inode":20480, "iused":77, "mountPoint":"/tmp" }
2015-11-10T03:01:02.404931-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"ramlog-tmpfs", "inode":1815, "iused":110, "mountPoint":"/var/log" }
2015-11-10T03:01:02.424613-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"/dev/sda4", "inode":243900416, "iused":2695, "mountPoint":"/DataVolume" }
2015-11-10T03:01:02.524537-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"inodeUsage", "filesystem":"/dev/sdb2", "inode":0, "iused":0, "mountPoint":"93de3f6b1c6f991dd33d2212f3ed9055/var/media/" }
2015-11-10T03:01:04.268253-08:00 di=k6NucgsedY notice BaseOSlog: { "msgid":"usageSize", "totalB":2027561616, "photos":0, "video":990707537, "music":0, "other":1036854079 }
2015-11-10T03:05:02.299070-08:00 di=k6NucgsedY notice logger: disable lazy init
2015-11-10T03:15:46.356066-08:00 di=k6NucgsedY notice logger: exit standby after 8 (since 2015-11-10 03:15:38.786651001 -0800)
2015-11-10T03:28:52.360260-08:00 di=k6NucgsedY notice logger: exit standby after 174 (since 2015-11-10 03:25:58.406651001 -0800)
2015-11-10T03:39:12.075818-08:00 di=k6NucgsedY notice logger: exit standby after 8 (since 2015-11-10 03:39:04.556651001 -0800)
2015-11-10T03:40:53.697994-08:00 di=k6NucgsedY warning wdmcserver: Received signal 2, stopping listeners.
2015-11-10T03:41:03.322333-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:41:13.324119-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:41:23.325603-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:41:33.327029-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:41:43.328416-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:41:53.329942-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:42:03.331349-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:42:13.332765-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:42:23.334186-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:42:33.335626-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:42:43.337033-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:42:53.341483-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:43:03.345296-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:43:13.346926-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:43:23.348389-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:43:33.349874-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:43:43.351299-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:43:53.352767-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:44:03.354218-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:44:13.355660-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:44:23.357108-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:44:33.358501-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:44:43.360001-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused
2015-11-10T03:44:53.363765-08:00 di=k6NucgsedY notice restsdk[6963]: paths.go:49: Could not dial crawler socket at '/tmp/WDMCRequest.socket', error: dial unix /tmp/WDMCRequest.socket: connect: connection refused

[Tolo_Mir]

@Ralphael I completely agree with you! They need to roll up their sleeves and make the device be simply useful!
If no announcement of a new firmware version I’m considering returning!

[Bob_O_Neill]

I don’t know if it is related to the firmware upgrade, but now WD2go does not work anymore (Windows phone), only showing the directories but not allowing access to the files (no network available), and the suggested option of mycloud.com on a browser (any browser - mobile or PC) will not connect at all - it says signing in until it times out. I no longer have any cloud access to the device. It doesn’t do what it used to when I bought it. Any ideas if this is going to be fixed?

[Ralphael]

@Tolo_Mir

If no announcement of a new firmware version I’m considering returning!

If you do have the opportunity to return, do so, but the alternatives are few for a good NAS-Cloud system as you will need to spend another $200-$800 for just a NAS without hard drives, by another company.

They won’t be fixing the media scans anytime soon as this has been part of the OS since the WD live days (4 years ago). To fix it yourself use SSH to log into the Cloud and kill the two services; this will give you a great little Cloud.

@Bob_O_Neill

I don’t know if it is related to the firmware upgrade, but now WD2go does not work anymore (Windows phone), only showing the directories but not allowing access to the files (no network available), and the suggested option of mycloud.com on a browser (any browser - mobile or PC) will not connect at all - it says signing in until it times out. I no longer have any cloud access to the device. It doesn’t do what it used to when I bought it. Any ideas if this is going to be fixed?

I believe WD2go is permanently gone with OS3; Webdav is no longer supported. Create a new post and ask around for other options.

[Bennor]

@Bob_O_Neill

I don’t know if it is related to the firmware upgrade, but now WD2go does not work anymore (Windows phone), only showing the directories but not allowing access to the files (no network available), and the suggested option of mycloud.com on a browser (any browser - mobile or PC) will not connect at all - it says signing in until it times out. I no longer have any cloud access to the device. It doesn’t do what it used to when I bought it. Any ideas if this is going to be fixed?

This is a separate issue from what was being discussed in this thread. Do a search of this My Cloud subforum and you’ll find other several other threads complaining about Windows Phone app no longer working post OS 3 upgrade and many threads on problems with the former WD2Go.com now MyCloud.com site.

One suggestion on the MyCloud.com site issue is to ensure your My Cloud is using the OS3 firmware (ie the latest firmware) as using prior firmware will probably cause issues since MyCloud.com uses Webfiles rather than WebDAV that WD2Go.com used when connecting to one’s My Cloud device.

[rac8006]

Rapheal

Some of my USB observations. On version -112 I can reboot with a 16 GB thumb drive connected. But the dashboard says that there are no USB devices. If you remember previously I had a problem upgrading with the USB mounted. The same problem happened when you try to stop media streaming on the USB device. I found that a process called wdAutoMountAdm.pm hangs. It calls another process. I can’t remember the name of those other processes. But when I did a strace on them. One was waiting on a select. The other two were waiting on flock. I think this means that they are waiting on each other. Which is a classic deadlock condition. I should also point out that if you do a df command the USB is mounted at two different mount points. Yet the dashboard says no USB devices. There is a file called /var/local/autoMount/autoMount.db. This database is supposed to contain information on mounted devices. If you query the database it show a USB device mounted. The vendorID of this device is a microsd reader. I think there should be two devices the reader and the thumb drive. I need to do some more testing.

RAC

[rac8006]

Rapheal
I wonder if lowering the priority on the wdmcserverd processes would help. That way when you
tried to do other things they would run becasue they have a higher priority.

RAC

[Ralphael]

@rac8006

I think this means that they are waiting on each other. Which is a classic deadlock condition.

yup…

@rac8006

I wonder if lowering the priority on the wdmcserverd processes would help. That way when youtried to do other things they would run becasue they have a higher priority.

I believe that was their solution after firmware 3.04 (to lower the priority on scans) and they (WD) actually believed that it was a good solution. However the problem in media scanning is that it is I/O intensive and there are certain read/write processes that cannot be pre-empted by the system. This is the reason that when I had that DNS problem, everything would hang for about 20 seconds before the connection was dropped and everything resumed.

The solution is to put the scan where people has control of it where after “each file is scanned” it would check if the user has clicked on stop before continuing. This way the user knows that it is a time consuming process and has full control over it.

second solution is to scan, create thumbnails, index only at the time of reference. i.e. when the cloud app is browsing a particular directory, it checks a db for thumbnail, index entries and if not available, proceeds to create a thumbnail. When the Cloud app refreshes, the thumbnail is then sent.

Last solution is like the first solution except only specific directories are added for scanning. Not everything on the hard drive should be scanned as this is not “Google”.

[Bob_O_Neill]

My problem is not specifically WD2go, but almost any method of accessing remotely. The only way that works is the (windows 10) desktop app “WD My Cloud” which works fine, but is not much use, not being remote. Mycloud.com does not connect - it times out in Firefox and Windows phone, does not work at all in Edge, and can’t see any devices in IE. I suppose if I revert the firmware I might get WD2go to work and kill off WD My Cloud. Is this possible? The dashboard reports that the latest version is installed.

[rac8006]

Another option would be to only do the thumbnail,indexing when the file is first added to the system.

minidlna uses a notify feature that adds the file to its database when the file is created.
I would like to know what wdmcserverd actually does as it is scanning.

RAC

[Bill_S]

@Ralphael, I did forward this to our product people.

[SBrown]

Hello,

My Cloud OS 3 introduces the “USB Content Availability” switch.
The default if OFF.

Does setting this to the OFF position resolve your issue?

[cpt_paranoia]

My Cloud OS 3 introduces the “USB Content Availability” switch.

Maybe you could explain what that switch is supposed to do, as it seems unclear, and, in the absence of a revised user manual, we all have to guess or feel our way blindly:

OS 3 USB Content Availability Option

With the addition of the “USB Content Availability” option in the OS 3 firmware versions, does this feature, when set to Off, actually work for other people when they connect remotely and have a external USB device connected to their My Cloud? When set to Off the external USB drive (a 32GB Sandisk Flash Drive) is accessible and contents can be downloaded when I use the MyCloud.com site for remote access. Screen capture indicating the USB Content Availability option set to Off: [image] Scree…

[SBrown]

Hello,

When “USB Content Availability” is set to OFF (default=off), thumbnails are not created for the content on the USB drive.

In the case of MyCloud.com, this setting does not apply.

When the USB drive is attached to the My Cloud unit, a share is created by default.
The share and it’s content are available using MyCloud.com

Regards,
Samuel Brown

[Ralphael]

@SBrown

When “USB Content Availability” is set to OFF (default=off), thumbnails are not created for the content on the USB drive.

In the case of MyCloud.com, this setting does not apply.

That is good and bad… because you are delaying the inevitable. Stopping the scans for normal local usage is great but as soon as you access via MyCloud.com, all hell breaks lose.

I’ve media stream turned off…and the wdmcserverd service stopped, but I notice as soon as I add my device to my cloud app, wdmcserver starts up and my cloud is rumbling with scans. Now I’m fighting with my device on the startup of the scans.

You cannot turn on the scans after the user has turned them off.

just like USB content Availability OFF means off… and not until I access MyCloud.com then it turns on. No … no … no…

and yes I do want accessibility to my USB content, just not the media scans…

[cpt_paranoia]

Yes, turning cloud access off then back on pops up a warning about starting scanning. WD obviously don’t like us turning off their scans. And, rather than listen to user requests to have a dashboard switch to disable them, they’ve added a dashboard feature to force them back on… I guess the only way to stop them is to rename the daemon… Then it will probably write error messages to the log like it does for their restsdk thing…