Ok so I was just in the process of installing the features packs for my white light and on a whim clicked "check for firmware update". It found a new update and I had a quick browse online which indicated that it added time machine support. No big deal for me…I dont have the apple device. Anyway I did a bit more searching and they have added some great new features: Twonky has been updated to Version 5.1. New gui and better compatibility with dlna devices. Sweet. Icing on the cake for me is the addition of ctorrent client in download manager. It allows you to throttle the upload/download speed as well as end the torrent when certain conditions are met. Nice. Am looking at trying ctorrent client now. Version number is 1.01.14. Cheers
One problem….could not find any mention of what port is used by ctorrent so port forwarding is an issue….
the WebServer / AccessBook Feature pack is currently not working with this new firmware,
i am working at solving the problem …
Edited 01/11/2009 : The problem looks to be solved now…
i want know if your feature pack support the white light two-drive 2x1T version ?
thx a lot.
the featurepacks work on the 2x1 Tb whitelight.
The only feature that you will not have is the System backup from the MybookClone Feature pack.
but the Data backup will be available…
Does Ctorrent support encryption? I don't see any advantages of using ctorrent over transmission. Except maybe system resources.
No don't see encryption options in menu….Downloaded a couple of torrents using it and it worked fine.
Is there a windows app to work with ctorrent something like transmission-remote for transmission cause working thru the web interface is slow and not very comfortable?
Ctorrent port information taken from this site:
"-p port Listen port (default 2706 -> 2106)
Specify the TCP port number on which to listen for incoming connections. By default, CTorrent starts at 2706 and searches for an available port in decreasing order until it finds one or exhausts all ports down through 2106. The behavior with this option is similar, but starting at the specified port number. "
Thanks for the notification, installed the firmware update a couple of nights ago.
I can report that Twonky 5.1 seems to work really well with the PS3. The older version struggled with fast forward and skipping for some file types, but no more. I can start watching a high definition movie then press 'Square' move to the last 5 minute press play and it instantly plays from that point. Funnily, the first scan that Twonky did picked up 80% of my music, pictures and videos. No rhyme or reason as to the files it skipped. However a second scan got to 100%.
since i upgraded to the last firmware the mybok is very busy and became hot! anyone has this prolem?
Yes, I noticed this too. It's 5'C warmer, and seems like the disk is spinning more then before. Also if I ssh and run top, the app cvm is running ~15 times.
Ok, so I found out cvm is MioNet which I obviously had forgot to turn off. But anyway, it seems hotter, yes.
Mine seems very busy as well….it has not gone into "sleep" mode since the upgrade. How do I check what processes are running…?
Ok…notice that the new firmware has altered the Mionet settings and it was on by default….now turned it off to see what happens. Other question still stands….who do I find out what process are running?
Turn on SSH -> connect to MBWE -> run "top".
Mionet daemon is broken. It seems like mionet starts on it own after a while even though you turn it off in the config site on the nas and disable starting mionet on reboot. When you turn off mionet it stays off for some hours, and then turn on automatically thereby draining resources on the NAS and taking CPU cycles.
Does anybody know if there are any script to alter/delete to keep mionet from starting?
Thanks for the info. After running the top command it sems on my unit it is tonkymedia player that is continually running…I have disabled auto update of files but there is not many more options to fiddle with.
I am having the exact same problem. Mine has not gone into sleep mode once since the update. Also, as posters below point out, Mionet keeps restarting itself, even though I have turned it off both from the web interface and via ssh with
There is clearly some sort of bug in this new firmware that is causing some script or other to keep executing occasionally, one of the side effects of which is that Mionet is constantly restarted.
Can anyone here that is more of a Linux guru figure out what script is causing this? I just sent a message to Western Digital tech support, but they are not necessarily very helpful. I suggest everyone else having this problem send them a message as well, though, so that they will note that this really is a problem.
I found that an option in the twonky settings was ticked regarding accessing media from usb devices. Once I had unticked this and restarted twonky it now enters sleep mode. Hope this helps someone. Cheers
Hi, Ragass. I saw this option on the twonky setup page, but mine is unchecked.
For those interested, I did "solve" the mionet problem, in a sense. I ssh'd into the device and removed execute permissions on the file /usr/mionet/monitorCVM.sh. Since doing this, Mionet is not starting up on its own anymore, and my device has been able to sleep. Strangely, the comments at the beginning of this file state:
## This version of monitorCVM.sh is only for FireFly use!!
## This will be called by Wistron's HW monitoring daemon every 1330 seconds.
So, clearly the script monitorCVM.sh was the culprit in causing Mionet to start, and it seems that Wistron's HW monitoring daemon (launched by init.d) is what is calling monitorCVM.sh in the first place. I don't know why this new firmware is doing this, other than that it must just be a bug that was missed by WD.
Now that I have fixed that problem, the device seems to be sleeping essentially as it ought to. I will post back whenever WD tech support gives me an "answer" to this problem.
A comment about this monitorCVM.sh issue: I bought the mybook (white light, the 2x1TB version) just a few days ago, and it had the problem described above, in that even though I have disabled mionet (through the web interface), the monitorCVM.sh keeps firing cvm. This does not keep the mybook from entering sleep mode, but I still wanted to get rid of these processes. It seems to me that disabling mionet in the web interface simply removes the file /etc/.mionet_on_startup. This is checked for in S9M_mionet (in init.d) like this:
if [ ! -f "/etc/.mionet_on_startup" ]; then exit 1 fi
So instead of removing execute permissions on monitorCVM.sh, I just added these same three lines to the beginning of that script. Whether this is the correct solution (tm) or not, it seems to function well.
BTW: I noticed that this HW monitoring thing (I guess it means /usr/sbin/wixhwmonitor, which is a binary executable) contains the string /usr/mionet/monitorCVM.sh hardcoded…
Hi, magugu - good solution, especially if you think you may want to have Mionet running at some point again later. And, yes, the string /usr/mionet/monitorCVM.sh is indeed present in the wixhwmonitor binary, though I'm not really sure why that is.
Anyway, let's hope that WD brings out a new firmware in the near future that fixes this problem for real. I still feel like my device is not sleeping as well as it should since I updated the firmware for some reason, but it may be in my mind and/or unrelated to the Mionet issue.
Well, I heard back from the useless WD tech support department today regarding this. They just advised me to reset the device to factory settings. I am not going to do this, though, as then I will lose all of the data on the drive (from what I understand). Anyone else having this problem that doesn't mind resetting want to give it a try and report back the results?
In the meantime, the "fix" I mentioned previously is still working and I can wait until another firmware update for a real solution if resetting doesn't work.
I've tried resetting to factory settings, and I can confirm two things.
1) It wipes all the data (it even warns you about this before it does it)
2) It doesn't fix this issue (I didn't think it would)
Thank Christ for this forum, I thought I was going nuts. That darn Mionet service just keeps on restarting no matter how many times I tell it not to via the web interface.
I too have noticed that my NAS has been drinking too much coffee and doesn't like to sleep since the firmware upgrade.
I've fired off an email to WD Support as well about this. Hopefully they'll release another firmware update soon-ish.
I've got this reply from WD:
I am really sorry about the issues you are experiencing with your drive and MioNet.
We are currently working on a new firmware release and this should be taking care of.
Please allow sometime for the firmware to be available.
The new firmware was released 2 days ago - v1.01.16. Has anyone tried this to see if it fixes the sleep issue?
the mionet problem is still there in 1.01.16.
also it tries to contact the following ip address 126.96.36.199. (as it did in the previous release)
no response from WDS re this
I wish WD would understand that some of us just want a NAS to back up files, and to be able to shut down all the other stuff.
Re stopping mionet, will try the permissions (its easier!!), can the same be done for wonkymedia server?
Well no real help from WD, other than disable remote access !!
Tried to point out this doesn't work (well for 13300 seconds it does), so in the relevant scripts down inet.d I have placed an exit 1 at the top of the script.
No more phoning home, no more mionet, and no more wonkymedia!!!
(though I am watching it carefully)
I just want the new twonky, the rest is not usefull to me…
And I did a lot of tweaking in my WD, I don't want to start all over again :(
Does the update delete everything ? Files ? or just a small amount of folders ? do we lose the /opt/ ?
Can anybody pack or send me the new twonky so I can install it myself ? maybe I can create a .deb for it.
Yes, /opt/ is gone after installing this update.
Does anyone know if it's posible to downgrade the FW to a version from before we got forced MioNet and a non-sleeping NAS? :/
see this two threads:
Upgrade Factory Installed Twonky: http://mybookworld.wikidot.com/forum/t-160628/
You can upgrade the new firmware with twonkymedia server v5.1 then copy the twonky folder to /DataVolume/Download
and make a roll back to an older firmware.
rename your folder /twonky
and install the TwonkyMediaServer V5.1 for "Maxtor shared Storage 2" from
now copy your registered file "twonkymediaserver" from /DataVolume/Download to /wonky/
tested and works fine….
going back to sleep problem
did a ps -af and found this one, perhaps it has something to do…
4520 root 404 S /bin/sleep 60
its usual to use sleep with the time u want and it runs with 60. but no idea how to change
(mbwe white light 1tb)
4520 root 404 S /bin/sleep 60
this sleep is part of the script
As a complete idiot, can someone explain how to stop the Mionet script on my WD Mybook white light version please.
I cant seem to even log in as root, I have enabled SSH but still no such luck.
A step by step guide from within a W7 enviroment would be great.
Thanks in anticipation, from an insomniac Mybook.
Can't give you step-by-step b/c I'm not yet running Win7, but since you self-labeled as a novice above, thought maybe you don't know these missing steps for SSH:
- get PuTTY from http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html (should work in W7)
- use PuTTY to connect to your box's IP as root / welc0me (if your SSH box is really checked and was never changed)
Then follow the popular Mionet procedure page here, finding it per pfoomer's advice if not found already. I was very recently a complete noob and all that worked for me.
I created an account for posting here just to thank magugu for his solution 6 years later :)
A few weeks ago I updated the firmware of my old MyBook which caused the problem described in this thread.
His solution didn't quite work for me but he pointed me in the right direction. Instead of adding:
if [ ! -f "/etc/.mionet_on_startup" ]; then
to monitorCVM.sh I simply added
I also commented the call to the two methods and the sleep command at the bottom of that file.
Since I never used Mionet and have no intention of using it now, it's no big loss.
Thank you magugu.