|# Needless to say, I (Volkan Ozcelik) take no responsibility, whatsoever,|
|# about what will happen to your NAS when you try these.|
|# When did it to mine, I observed *ENORMOUS* performance gain and a zen-like silence.|
|# | WHAT YOU ARE GOING TO DO CAN LIKELY VOID YOUR WARRANTY ||
|# | SO PROCEED WITH CAUTION ||
|# There I said. That’s not for the faint-hearted.|
|# Though if you are fed up with your WD’s poor performance|
|# and if you feel adventurous, read on…|
|# Where was I?|
|# So if your WD NAS is torturously sloooow, the hard drives spin ever and ever,|
|# your web admin interface does not load in “minutes” and when it does you can brew|
|# a fresh irish cream latte and also drink it while navigating from one page to another,|
|# if your CPU utilization is around 50%-90% ALL THE TIME, then what you’ll read here|
|# might help you.|
|# The root cause of all these issues is that WD Cloud attempts to index all the images|
|# on your hard drive and create thumbnails for them — If you are an average Joe who|
|# uploads a bunch of family photos, that’s no big deal. — But if you are like me,|
|# who have mostly front-end-related projects, digital design, and artwork, that has|
|# been accumulated over the last 15 years; that indexing process can take YEARS to complete.|
|# ** I’m sorry WD, and I am not gonna wait for a year to have a silent and healthy drive!!!!!! **|
|# The good thing is, the indexing process can be disabled.|
|# The not-so-good thing is, you’ll need to ROOT into the device, which can void your warranty.|
|# If you are ready, let’s move on:|
|# Step 1) Enable SSH from the admin console.|
|# Log in to the web admin UI and then go to Settings » Network » SSH, and turn it on.|
|# Step 2) Shell into the device:|
|ssh -oHostKeyAlgorithms=+ssh-dss sshd@your-western-digital-local-ip-address|
|# You HAVE TO use `-oHostKeyAlgorithms=+ssh-dss` because your|
|# WD drive’s OS (the particular flavor of Linux (BusyBox) on the device)|
|# does not support secure SSH access.|
|# When you log in you’ll be prompted with something like this:|
|# root@WDMyCloudMirror root #|
|# Step 3) Stop the bastards:|
|# Step 4) Check and verify that they are indeed stopped:|
|ps aux | grep wd|
|# You are all set!|
|# Enjoy your performant and quiet NAS!|
|# There is probably a script somewhere that enables these services (wdmcserverd, wdphotodbmergerd) on reboot.|
|# If you feel extra adventurous, feel free to hack into the system and disable that script too.|
|# When you do, I’dd appreciate if you comment on this gist as well.|
|# When you restart the hard drive, or when there is a power loss and a reboot, those services will go up.|
|# So you’ll have to shell into the box and kill them again.|
|# Extra Extra Tip|
|# Moving things around is MUCH faster when you SSH into the box instead of managing|
|# them from your remote NAS mount. “The Cloud” is especially a bit foggy when|
|# you are connecting through the wifi. Whenever possible prefer a gigabit ethernet|
|# connection to your private cloud.|
I just use WD only as file storage through sftp/ftp, not as media players Timemachine backups.
Reboot after the following commands:
update-rc.d is no longer found on some models of WD My Cloud. There are workarounds about startup scripts to run the stop command, etc but WD is doing integrity checks on the devices post-firmware update and changes like this can get your device in an unstable state and make it difficult to connect without a re-image.
Hi @Pedrolitor; happy to help.
Unfortuntaley, I removed the hard drives in that unit (after being fed up enough) and switched using a QNAP Direct Attached Storage.
Since I can access a DAS (attached to my PC, and my PC is never down) from the network anyway, it is still doubles as a NAS to a certain extent without all the useless crap.
I think unless you have an organization of 4-5 people with different users, profiles, and needs; a NAS is kinda overrated.
So I don’t know what that command may entail; but since you’ve rooted into the system at least you can
Hope that helps.
The issue is here in the script (this is for /etc/init.d/wdphotodbmerger but same for wdmcserved).
the kill process is complaining about the process id because the pidof wdphotodbmerger command should return a process id for kill to, well, kill but that command returns null. Which means either wdphotodbmerger is not running, or it's at some other level that isn't available to the shell.
running ps -ef | grep wdphotodbmerger returns nothing (just the grep statement itself), so apparently it's no longer running.
Thank you so much for the updates guys. @v0lkan sorry I took so long to respond I didnt see your response, you answered too quickly ^^
Now we use Plex, and let it manage the DLNA (no plex app on this tv...) but only for movies/tvshows. I'm not sure it's better because the DLNA is still really unstable. Sometimes it works just fine, sometimes we dont see the server on the TV but my brother 600km away can stream 1080p movies from the server on his phone using plex. I think the problem come from the NAS that is not powerful enough.
@lonmiller I didn't get all you said (sorry I have poor english and zero SSH skills) but what I understood is that they were both already stopped that's why it couldn't stop them. Since they were and update lately I just stopped them and it worked! But the dashboard and metadata agents in plex are still incredibly slow (and no one is using neither the nas or plex right now...)