…ok
I have found what the problem was!
The share folder of My Book Live is managed by some service that controls who has and who doesn’t have the rights to write into it.
This means that a system account (as in my case the user was “transmission”) cannot write in share, even if it has a folder with proper rights.
What I did was changing the Group ID (GID) in my /etc/passwd file so it was matching the “normal” accounts.
In this way I could manage the rights of the shared folder for my “transmission” account using the official Web application from WD.
Once that my “transmission” account had the proper rights…
everything went fine!
bill_s wrote:
I really need to make it known that WD does not support, nor provide support for, modifying our NAS drives. Doing so may damage the drives and possibly void the warranties.
Perfectly understood, but in my case SSH and root access has allowed me to resurrect the TronkyServer without having to factory restore/wipe the NAS! TronkyServer and/or MySQL corrupted the database TwonkyServer uses. The solution was to rename two files and let TwonkyServer rebuild them. There need to be more maintance options on the Web Dashbord UI to allow more restoration control. For example, an option that will remove and clean the TwonkyService and then re-install it cleanly WITHOUT re-formatting or performing a full or quick factory restore.
This would also assist with people who meddle and don’t know what they are doing. Like… “Oops… I really fecked up TwonkyServer, but it’s ok… I can fix it by clicking one button on the Dashboard UI.”
Still, for me the Tronky media server screwedup itself and I have way less than the theoretical limit of 80,000 files. I only got my MBLive two days ago. Not good for the media server to keel over and die. … BUT … Also understood that Twonky ain’t Western Digital.
At the moment I’m seriously happy that SSH and root access is allowed as it’s saved me wiping 256Gb’s of data to fix te media server.
Lesson learnt. Over the next few days I’m going to make working back-up sets of the NAS’s configuration files and other stuff so if anything messes up it should be a simple thing of copying back a working set of configuration files.
Think it’ll be time to write a useful set of bash back-up scripts. (Something WDC should have done to more ■■■■■ proof the drive!)
@markoalmelo: what is default download path in your case? I believe you need to change to /shares/SOMEFOLDER , otherwise you will run out of space quick.
Edit : Okey , I tested it already ! DONT use it. There is 1 stupid bug in webinterface. Already reported it and will be fixed in 2.31 which coming out soon.
Edit 2: version 2.31 is out, and web bug is fixed. So , safe to use now !
My english is bad, but i want to share some experiances of installing feature pack and bit torrent download client into your My Book Live (MBL).
I just got my My Book Live 1TB, and i don’t have any basic knowledge of Linux language, however i manage to successfully install bit torrent client into MBL. It’s very easy.
A bit of a n00b issue here but since you posted the pack I was hoping you could help me. I am stuck on installing the feature packs. The only option provided is to install them via a URL. Can someone post the URL I am supposed to use?
Thank you Gingermut. I was able to get it installed and running fine yesterday. But today transmission had issues connecting to trackers so I uninstalled it. Now when I go to my feature pack link, it is not showing up as a pack I can install. What gives? Do I need to reinstall the whole thing again ( like the system config?).
The feature pack installs to optware subfolder, I think. When you do a firmware update, I believe that part will be wiped. At worst, its just a re-install of the feature pack. The author of the pack may have better idea of how to restore the package.
I’m sorry you misunderstood me. First of all, I said that it “could” void the warranty. I didn’t say it would. I was speaking to the fact that they were talking about turning the My Book Live into a torrent client, which is not part of its original function or specifications. Moreover, I was really speaking to the fact that if something goes wrong with the drive, we wouldn’t be able to provide support for restoring it to its original function. If you want to take a look at our warranty policy, the link is below. However, I was referring to two distinct points made in our policy:
The product was not used in accordance with Western Digital specifications and instructions.
The product was not used for its intended function (for example, desktop drives used in an Enterprise environment).
a) This policy makes perfect sense. WD is not in the business of debugging Linux when people (qualified or less-than) go in and tweak settings etc. Many / most other companies are like this, too: if you go and attempt to install a supercharger on your Toyota and the car won’t start anymore, well, surprise: your warranty won’t help you. That said …
b) I think we should all acknowledge the awesome in the fact that WD *knows* that some of its customers are going to tweak their devices and are pretty cool about it. I’m sure we could all name a few companies that are extremely rude to anyone who attempts to “extend the product capabilities”. So Big Kudos to WD.
Just MHO, the Usual Disclaimers, and no I’m not getting paid to write this.
(Something WDC should have done to more ■■■■■ proof the drive!)
