Checked my warranty status and I am still under warranty! Put through the RMA. Thanks everyone and for the PM WD_Bill!
I assumed that a year warranty was what I got, but it was more. 
nfodiz wrote:
Here is the direct link for those wishing to update using update from file from the MBL dashboard
I wonder how did you find the link? After going round and round in circles on the support website I finally found a line that said:
Critical: Manual updating is not currently available, if you need assistance please Contact Us.
Barry
I updated the firmware this morning and there is no WD Media server after the update, just Twonky. What went wrong?
Is there a way to configure the media server settings?
No, you can only control which shares it scans by going to the dashboard and enabling media serving on a share by share basis under SHARES
Hi all,
I upgraded my My Book Live 2TB NAS to latest WD firmware version above and I still can’t stream MKV files. Twonky 5.19 says “file format not supported” . Do I have to upgrade Twonky? If so how do I do that? If someone could point me to the steps to do it and get the upgrade for the My Book Live I’d would really really apprciate the help! I spent most the afternoon trying to get this working, surfing the net, trying to find any help. So far I am confused. Twonky or WD don’t make this easy when it should be! And I am an IT professional!
Thanks again for any help!
Thanks nfodiz for your help!
I’m almost there! I followed the instructions as you said but now when I try to run an MKV file (3D) The server keeps coming back to the navigation menu and won’t load the video, Any idea why?
Thanks again for all your help!
I’m not sure on that one… Do you have a regular mkv you can try to play? I have no idea if the WD server can handle 3D mkv’s…
Maybe someone else can chime in here
1 Like
I just had to rebuild the database in the dashboard! Wow works fantastic now! Keep it mind when you are suggesting the great help you gave me! 3D MKV ARE SUPPORTED!
Woohoo!
Thank You!
1 Like
Hey nfodiz,
I can’t mark your message as a solution under options. How can I give you the solution kudos?
To mark a post as a solution, I believe you need to be the starter of the thread
You are very welcome though and thanks for the info on 3D mkv’s working 
1 Like
I’m getting error 31105 when updating.
What can I do?
If you know how to SSH into the drive, go to /CacheVolume and post your update.log text. This may help track down the issue
update.log
(Reading database …
dpkg: warning: files list file for package `ramlog’ missing, assuming package has no files currently installed.
dpkg: warning: files list file for package `libparted0’ missing, assuming package has no files currently installed.
19071 files and directories currently installed.)
Preparing to replace apnc 02.41.05-034 (using /CacheVolume/updateFile.deb) …
preinst: currentRootDevice=/dev/md1
preinst: master_package_name=apnc
preinst: update_container=
stopping duplicate md device /dev/md0
mdadm: stopped /dev/md0
Restore raid device: /dev/sda1
Restore raid device: /dev/sda2
Prepare for upgrade install to /dev/sda1 …
Stopping periodic command scheduler: crond.
Stopping standby monitor: monitorio.
1 pids were not killed
No process in pidfile ‘/var/run/tally.pid’ found running; none killed.
failed!
Stopping Twonky MediaServer …
Stopping itunes server: forked-daapd.
Prepare for upgrade pkg install…
mdadm: /dev/sda1 appears to contain an ext2fs file system
size=1999808K mtime=Thu Jan 1 01:00:01 1970
mdadm: size set to 1999808K
mdadm: creation continuing despite oddities due to --run
mdadm: array /dev/md0 started.
preinst: current device=/dev/md1
preinst: upgrade device=/dev/md0
Unpacking…
Unpacking replacement apnc …
Setting up apnc (02.41.05-034) …
postinst: upgradeDevice=/dev/md0
postinst: currentRootDevice=/dev/md1
postinst: upgradePath=/mnt/rootfs
Copy image to upgrade device /dev/md0:
blockSize=64k blockCount=31247
Compare checksum
-: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match
ok 1
Upgrade failed
mdadm: stopped /dev/md0
mdadm: added /dev/sda1
Hello,
I now get ’ 31101 - Invalid firmware package’ using the file you provided.
Please download Hashtab from http://www.implbits.com/Home.aspx
Install and then right click on the .deb and select properties and then select the file hashes tab and compare to mine
CRC32: C3850B18
MD5: 4BED62F94A43DA6648117DB988600DAA
SHA-1: ECF590C06BD2BAF557DF7B4B54FA1190AA98B341
I am almost positive you have a corrupt file
I’m on a Mac.
My md5 is 4BED62F94A43DA6648117DB988600DAA
I tryed using ckeck for update and update from file.
Same result 
BTW: it stays a lot of time on 70% when upgrading
Are you by chance using a wireless connection?
MD5 matches so it has to be getting corrupted somehow when the dashboard sends the file to the mbl to be extracted
Is there a rootfs.img file at /CacheVolume/upgrade?
If there is we can use terminal to run an md5 check on the extracted file
Yes, I’m using wireless connection.
I can try using another one but aren’t any more errors on the log?
I see some warning and pid not killed… could it be related or is this normal?
