The process named "convert" in WD My Cloud EX2 causes severe performance and availability problems as well as unnecessary wear of hard drives. After putting many files into the EX2 unit, the convert process begins to consume CPU 100% and cause many unnecessary I/O activities on the hard drives until the owner reboots the unit.
Please implement solution to this also for EX2 My Cloud Device!
please add firewall apps like iptable or ufw in ex2 to control & restrict access to the device from inside the unit,most, firewall apps are available in most of linux distributions and don’t have much load on the cpu
wireless routers don't support firewall access rules inside the local network over IP
for example 192.168.1.1 - 192.168.1.25 access the cloud ,192,168.1.26 - 192.168.1.255 be restricted
Currently on the EX2, we have the ability to create remote backup jobs. Once created, however, there is no way to EDIT the job. In order to change any of the parameters on the job, one must delete the current job, and create a new job with the same job name as the one deleted to prevent a new copy of the source data to get backed up to the destination drive.
Please add the abiltiy to edit any one of or all the parameters of an existing Backup Job:
Add / remove shares
Change backup "TYPE" from Copy to Synchronize (or visa versa)
Change job from Autoupdate OFF to Autoupdate ON (or visa versa)
In the Dashboard (EX 2) it is possible to successfully create user names with capital letters (wich is NOT supported). If you log off, it will change all letters to small ones, without anyone being notified. -> Problem while loging in
This problem is already known to WD support.
Quote: " In fact, when you create the user name with the capital letters, once you save the change, it will revert all capital letters back to small letters. Therefore, it is not possible to login with the user name containing the capital letters.
If you change the user name "admin" to e.g. "AAAdmin", once you save the change, it reverts back to "aaadmin", Therefore, when you want to log in back to Dashboard, you have to log in with the user "aaadmin" and not "AAAdmin"."
- Accept user names with capital letters or
- Display an error message when trying to set an invalid password and reject the change
byjimmyfwalker01-11-201407:38 AM - edited 01-11-201407:43 AM
I would like to have the ability to backup my enitre EX4 to an external USB drive. I know the feature is already in the unit, but you have to schedule one folder at a time, so it would be nice to schedule the whole unit, and then only have it backup the files that have changed, and not the whole unit. It could be kept in one folder on the USB drive, instead of creating individual folders with dates and times. Also would like to see the ability to remove permissions from the USB backup share so that you can restrict who sees all the data from the EX4.
I am using my EX4 as more storage for my backup server. I'm doing disk to disk backups, and then disk to cloud with a 3rd party.
My disk to disk is something I built, which has a few other people using it for fairly large setups. It's simply rsync with hard linking between incrementals. I'm not sure if hard linking is working at all with Samba though. I'm bouncing between projects here like a mad man.
To give SMB access to my previous NFS share, I had to do the following. It would be good to see these as options or changes in future firmwares, so I don't have to do it manually in the shell. I had to grant root access to samba, because I back up almost everything, and they can be owned by any local user. If I back up the entire filesystem, lots of files are owned by root (obviously), so Samba allowing root is essential. It would be a nightmare to restore and guess at ownerships for every file on the system.
I gave this disclaimer on my post, so you guys will (hopefully) not get support requests for changes I mentioned.
"Note to everyone else. Don't do any of this. I had to log in via SSH and manipulate things directly. I'm a professional, and take all liability for my own mistakes."
If I can be of any more help, feel free to email me. I believe admins can see my email address on my profile. If you're at WD and can't get my email, get with me and we'll figure it out. I'm sure this is all clear enough for anyone building the firmware. If you want me to try something in my environment, I'm willing to consider it. I work with this stuff all day every day, so I generally know if a change is dangerous.
There's a bug with my changes. I can read all the root-only files now. I can't write to anything. I'm back in to fix that. I'm sure it's one stupid flag. samba.conf can be annoying.
1) Allow the user root to be accessed via the user panel, and add it to the smbpasswd file.
Obviously the local user root already exists. I added it to the smbpasswd file with: smbpasswd -a root
And I also set the local user password with: passwd root
2) Make root a valid option as a user to be allowed to the share. Allow root to be added to the valid users list.
3) Change /proc/sys/dev/raid/speed_limit_* . 1000 is way too low with 16TB. After the firmware update, it wanted to rebuild the array, and will take 11 days. I changed them to 99999999 (arbitrarily high number) . Now it claims 2.54 days. That could be catastrophic if someone had flaky power. We've been having short power outages here, but the UPSs stayed up the whole time. If we had a long outage and the generator didn't kick on (or if I was an average home user) dropping power during a rebuild could fail the array. I don't think you want to try to explain over the phone to a novice user how to reassemble a failed array.
4) I would have liked it if you had built busybox with chattr. Tell whoever builds it, they'll understand. I wanted to "chattr +i smb.conf", so nothing would accidentally change my settings back. I already tested, and if i make any unrelated changes, it reverts them to your settings. I made a backup, so it won't be a big deal if it changes in the future.
I only got the EX4 because it was cheaper than building out my own machine to do local storage. As far as that goes, it's cute, and seems to work well. All in all, it doesn't look bad from the inside.
And, thank you for having ssh as an option. i'd hate to have to try to root this thing without it.
Repair the software bug in the dashboard webfile viewer so users other than Admin can use it remotely to transfer files.
Curently you can enable dashboard access and forward port 80 or 443 (443 for secure html) to then access the EX2 or 4 directly via your WAN ip. This allows you to use the built in web viewer app to upload and download files when you are away from your home. Other users that you have added to the EX4 can log in via there own username and password and they will be shown a limited version of the dashboard with only the viewing rights to the directories that you have assigned them. However, they can not download, or upload anything which makes this useless for sharing files.
So to summarize, remote dashboard access as the admin works perfectly, remote dashboard access as a sub-user is useless.
I have also noticed that if I login to the admin account, then logout and back in as a subuser on the same PC, the sub-user account works perfectly. However I can't go to my users homes and login then logout so they can have access...
Getting this fixed would solve a lot of file sharing problems for everyone.
I had recently submitted an idea to be able to backup the entire EX4 on a schedule, instead of setting up each individual folder, and then manually kicking off the backup. The idea was rejected by WDC, stating they would not support that feature on the EX series. I hope that was a mistake - really you won't support the function to backup the entire device on a schedule? If that is the case I will have no use for this device, and will need to purchase a different unit. Please WDC, make this happen.
The instruction manual says nothing about any function or menu option about linking AD with cloud. Anywhere.
I'm thereby going to have to conclude that at this time, the function is not available.
However, this should have been implemented in the first revision as it negates the whole point of having a device called "My CLOUD" on an AD with controlled users who have a single sign-on solution on laptops and other mobile devices.
This is the main reason the company I work for picked the My Cloud EX4 device in the first place.
You could argue that not everyone in the AD needs cloud access, you'd be right, I have about 40 users only about 10-12 of them will need cloud access. I could create the users manually and then join the AD, and alott the rest of the users to FTP and UNC file sharing.
What happens though if one of the Cloud users quits his/her job or if we decide to hire a new employee and I have to add him to the cloud users?
I would then need to remove the drive from AD, add/remove the user as required, then rejoin?
What happens to the AD users' files when I do this? Will they be deleted? Will the users lose access to them?
Furthermore, I discovered that when adding/validating your user, the interface presents you with a pull down menu listing all existing users.
I don't mean to sound rude or aggressive but you guys are making it really difficult not to.
Please implement the AD->cloud link as soon as possible and thanks!
I'm using My Cloud drive and I've created a public media share that I'm using to store music, pictures, and videos. I need this to be public so various devices (TV, xbox, etc) can access it but that means that anyone on my network (friends, family) could accidentally delete everything in that share. I'd like to set guest access as read only on that share to prevent that.
It seems like it would be fairly easy to add a guest read only flag to the dashboard GUI since I believe this maps directly to the samba config keyword "read only = yes" (or writeable = no) which is already part of the /etc/samba/overall_share file. I tried setting this option (via ssh) and it does work (it makes it read only), however the valid login list (write list field) is being ignored for some reason so if I set read only to yes, then I can't write to the share even though I connect to it as a user in the writeable list. Not sure why that's the case...