Recent Forum Posts
From categories:
page »

tvmobil free version allows streaming upto 10GB - thats not alot. I've already paid 2 licenses for twonky, one 4 years ago and one just recently as I couldnt find the 1st one.

Please, fresh installation instructions for twonky including removing the current broken version on the MBWE.

You should use tvmobili. It's great. I posted about manually installing it successfully here in the past. It comes with great instructions but be sure to use notepad++ to read them.

Hi Dav-M - Do you know where instructions exist to remove and clean install twonky on MBWE? I'm so frustrated, something has not quite worked and twonky eventually fails.

I want to have the latest version but following the instructions here has not worked for me.

I'm seriously considering another product.

Has anyone got this working for the twonky releases version 8.2 / 8.3 or the latest 8.4 release? I've tried with the upgrade notes but it either become unresponsive the first time or intermittently fails.

MBWE2 works fine for twonky versions up to v8.2.1.

That's a pity as v8.3 onwards has HEVC codec updates as well as samsung tv sub-title updates.

I've tried v8.3 and v8.4 and but it consistently overloads the NAS and eventually crashes.

Anyone who can somehow make it work with 8.4, I and so would many MBWE2 users would be extremely grateful!


Done the following:

/etc/init.d/S97twonkserver stop
rm -r /var/twonky/twonkyserver/*
rm -r /var/twonky/TwonkyServer/*

Followed post (…complete-guide-to-upgrade-to-twonky-7-8-version-my-book-worl) to install 7.0.8 version.
- points to note refers to 'Maxtor Shared Storage 2' software release

Goto IP address:9000 and enter license and its working.

I previously installed glrellm to provide realtime hardware statistics and the NAS is finally stable.

I'm looking at the various upgrade options as 8.4 is the latest release.

Its set to -1 and its been running for more than 5 years with any problems.

I plan to remove the full twonky installation and try again, I'll post the progress update later today

i set twonky to scan twice a day (660 min) and it's been running great! what's the longest amount of time you've had twonky stopped for whereby you didn't have an issue?

I dont believe it - its failed again!!

I've done the following to determine if its the WD NAS, my network or the NAS software (twonky):
As there were disconnection issues, IP conflicts could be an issue, so modem and switch restart. This is following reports of 'Connection to port 22: Broken pipe' and 'ping statistics of NAS with 20% packet loss'
NAS IP works fine but when twonky starts, IP disconnection intermittently occur..and therfore eventual loss of SSH connection. Also twonky DLNA service initially appears and then fails at the same time SSH loses connection.

I can only conclude its twonky…So why did it work for me ok this morning? and then eventually fail after 2 hours of non-use…?

I just reviewed the twonky rescan settings and the -1 (not all 9's i mentioned prior) is what used to crash my server a lot. I hear that you are using 90m so that should be better. If not, just increase it in the future.

So, after twonky 8.0.3 installation upgrade and new license applied.

Its all working, rescan interval default setting is at 90 minutes, I may change later.

Prior to the upgrade, i did clear the current db cache (rm * within the directory). It may that, the upgrade version created a new db cache and it never used the corrupted one.

The new version is much faster in terms of scanning, and its working fine.

Thanks for your help. While my mind is refreshed, I might be in the mood to further upgrade to 8.1.2 and upgrade samba v3.

I may even buy compatible WD disks to upgrade from 1 to 4 TB.

it was set to -1.

Now that I know the problem is twonky, I've decided to go for the upgraded version 8.0.3. I've had version 7 which was a long time ago.

Unfortunately, I've missed placed my OEM license, so I've paid for a new one.

I'll try with the new version and see where that leads.

How often did you have twonky searching for new files? I think i had problems in the past when i set that number to 9's as that like an immediate search option.

Thanks for you message [dz2k] but it seems to be twonky service itself. It happens only when twonky service starts.

I've moved the twonky startup script and its working fine without it. The WD site is working fine and the NAS mirror is good.

Whenever I initiate the twonky service, I think the file rescan causes it to hang and causes an overload CPU/RAM and all other serives eventually fail including pinging its IP address.

I can only conclude twonky's db is corrupt.

How can I reinstall it? I followed this […upgrade-to-twonky-7-8-version-my-book-live..] on the initial twonky installation but I'm not sure how to delete the db and reinstall it without affecting its license (paid for it).


Some personal findings:

  • My wdbctl0030hwt is a WDMyCloud-Gen1 (though the BCTL model is not listed in
  • The 64-k page distro (CleanDebian64k.tar.gz) did not work well with the generally available packages: If you apt-install from the Debian repositories, sometimes the processes bails out and exit.
  • Stick to the CleanDebian-Jessie.tgz release instead
  • The default system cmdline includes some debug clauses in the cmdline: debug initcall_debug. This cause systemd and kernel to throw lots of unneeded messages. The only way to fix it is writing a new configuration partition. This is how I did it.


1. Log in your WD box and fetch the current kernel configuration:

# dd if=/dev/sda7 of=config.img

2. Extract the configuration using the strings command:

strings config.img > config.txt

3. Edit config.txt, remove the clauses debug initcall_debug and save the resulting file in a PC running Linux.

4. In the PC, download bareboxenv32 from the GPL toolchain (I got from from WD at The file is located at packages/barebox-2011.06.0/scripts/

5. Take the file that you got from step 3 and save it in a same directory that has bareboxenv32. Then run:

chmod 755 bareboxenv32
./bareboxenv32 -s config.txt new-config.img

6. Save the resulting file new-config.img to your WD box

7. Blank your WD box partition 7 config data:

dd if=/dev/zero of=/dev/sda7

8. And then, load your new config data:

dd if=new-config.img of=/dev/sda7

9. You may then reboot your system.

Of course you may also use this procedure to add something you want to the linux boot cmdline. Just add/remove it in step 3 and follow the rest of the procedure.

Kudos to fox_exe o/

Hi there list,

A clever guy has published a nice post at WD community, pointing how to install Open Media Vault, Debian Wheezy / Jessie and Synology DiskStationManager v5.2.

For archival sake, I'm republishing it here, from the original post at

WD make a great device with cheap price, but its not so functional for me. So i make few alternatives and here is they:

Primary file archive:
Mirror: Google.Drive folder
For donations - please, go to my site ([]) or write a message in pm on this forum.

Whats done now?

  • Clean OS (Debian Wheezy and Jessie) + Test build with WD/Mindspeed patch (Memory page size changed from default 4kb to 64kb)

> Installation: Read info file inside "Autoinstall" folder.

  • OpenMediaVault - Debian wheezy + OMV. Can be upgraded to latest version. Work almost all stuff.

Ps: Please, dont change network settings or check /etc/network/interfaces before reboot if you changed it)
> Installation: Read info file inside "Autoinstall" folder.

  • Synology DiskStationManager v5.2 - Yes! Its DSM from synology! Great WebGUI and lots of functions (Work almost all, except disk mamagment and Synology cloud services - need valid MAC and Serial number). Stable.

> Installation: Read info inside DSM5 folder.

Recovery and roll back:
If something went wrong, please read "Replace HDD" instruction - its help you reupload firmware to HDD or change internal HDD to another one (Yes, need disasemble device)
Or read instructions from "Recovery" folder - Its almost same, but no need to open device (And void warranty)


  • WOL not supported by Hardware.
  • Be careful with network settings - sometime its erase network settings (/etc/network/interfaces)
  • On first login you can get "Error 404: Not found". Just clear browser cache and check URL (There is no "/UI" string anymore)
  • All your data is safe (DataVolume not changed and not formatted)
  • User / Password for login (WebGui, SSH, etc…) is root/mycloud or admin/mycloud
  • For OMV: After install - go to Storage -> File systems -> Unmount /dev/sda4 and mount it again, then create "Shared folders" and setup other things (Samba, ftp, ssh etc…)
  • For other questions - check this thread. I think all questions already answered.
  • Sometime i can answer in Skype. Check my personal page.

I've managed to stop twonky via root and samba and RAID service reports ok, no errors.

The problem seems to be with twonky or something related.

I've repeatedly pinged the server and its responding now but SSH connection evetually fails with broken pipe.

Hi there,

I have a steady MBWE2 for 4 years + and suddenly it stops working after 5 minutes. I've SSH installed and on reboot I can connect. The twonky service does become available but shortly it fails. thereafter, I'm unable to SSH or even ping the static IP address.

Any advice please?

page »
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License