The MyBook Live series is based around Linux, so you can fix some of WD’s design decisions and improve performance. You can do just about anything, but there are some simple performance improvements you can do.
Assuming you are blocking port 22 from outside your network, enable SSH by logging in to the web dashboard, then switch to the page UI/SSH, and enable from there. If your NAS had the address 192.168.1.101, you would first go to
log in, then go to
to enable SSH. At that point, you can ssh to your box; ssh is built into Mac and Linux boxes, but you’ll need to use Putty or some other client on Windows.
I got this from What are the steps to enable SSH from the WD Community forums.
WD has a monitor script as a daemon. That in itself is fine, but it periodically does an ls of the entire drive to build up some simple statistics. Once your drive has a large number of files on it, this will cripple performance. Since I don’t ever look at their stats, I prefer to disable this part of monitorio.sh. I want to repeat this: if you do this, then the web front end will no longer show accurate disk space usage (it will show whatever you had up to the point where you nerf the file_tally function).
I suggest the following: ssh to your NAS, edit /usr/local/sbin/monitorio.sh, rename file_tally to file_tally_old, and insert an empty file_tally function. Your file will look like this:
if [ ! -p $TALLY_PIPE]; then
You’ll want to restart the monitorio daemon (or reboot the NAS, which is more dramatic).
You can also use ps and kill to stop any existing ls process if you’re impatient.
I didn’t figure this out, I got it from Solving the MyBook Live insane load.
Change to CFQ scheduler
Some people think that performance is better if you switch to the CFQ scheduler. This will definitely depend on how you use the NAS. WD has defaulted to the Anticipatory scheduler. You can check to see what yours is set at.
and if you see
noop [anticipatory] deadline cfq
then your NAS is currently using the Anticipatory scheduler. You can switch by writing CFQ to the scheduler file like this
echo cfq >scheduler
And, if you have multiple drives in your WD Live box (for example, a Live Duo), you’ll need to do this for sdb as well.
I got this from Performance problems? Read this first.
You can read more about the various scheduling algorithms in this Red Hat page: Choosing an I/O scheduler for Red Hat Enterprise Linux 4 and the 2.6 Kernel. At some point, this will be out of date, but it was valid as of late 2012.