Use terminal to login to the MBL
cd /CacheVolume/upgrade
md5sum rootfs.img > test.md5
compare test.md5 to rootfs.md5
There is no upgrade folder at /CacheVolume/ (and no rootfs.img)
Th3V3ldt wrote:
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?
That is normal…
Here is my upgrade.log
updateFirmwareFromFile.sh:03/01/13 03:41:01:upgrade start: /CacheVolume/apnc-024105-034-20130215.deb
updateFirmwareFromFile.sh:03/01/13 03:41:01:check_size=
updateFirmwareFromFile.sh:03/01/13 03:41:02:version_current=024105034
updateFirmwareFromFile.sh:03/01/13 03:41:02:version_newfile=024105034
updateFirmwareFromFile.sh:03/01/13 03:41:02:package_newfile=apnc
updateFirmwareFromFile.sh:03/01/13 03:41:02:master_package_name=apnc
updateFirmwareFromFile.sh:03/01/13 03:41:02:master_package_new=apnc
updateFirmwareFromFile.sh:03/01/13 03:41:02:update_container=
dpkg: warning: downgrading apnc from 02.41.05-035 to 02.41.05-034.
(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.
19042 files and directories currently installed.)
Preparing to replace apnc 02.41.05-035 (using .../apnc-024105-034-20130215.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.
Kill Miocrawler Process...
No miocrawler process is found
Thu Feb 28 22:41:15 EST 2013 - %W - Communication Manager - process is not running
Prepare for upgrade pkg install...
mdadm: /dev/sda1 appears to contain an ext2fs file system
size=1999808K mtime=Wed Dec 31 19:00:01 1969
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 ...
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/dlna_bom-update', which is also in package apnc-twonky 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/twonky_utilities', which is also in package apnc-twonky 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/postinst-patch_apnc_dlna', which is also in package apnc-twonky 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/postinst-patch_apnc', which is also in package apnc-twonky 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/postinst-patch_apnc_twonky', which is also in package apnc-twonky 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/postinst-patch_apnc_access', which is also in package apnc-twonky 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/upgrade-patch_twonkymediaserver-hollow', which is also in package apnc-twonky 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/upgrade_utilities', which is also in package apnc-twonky 01.00.01
dpkg: warning: unable to delete old directory '/DataVolume': Device or resource busy
(Noting disappearance of apnc-twonky, which has been completely replaced.)
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
-: OK
ok 0
mounting new root file system
/dev/md1 on / type ext3 (rw,noatime,nodiratime,barrier=1)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755,size=5M)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev,size=5M)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
tmpfs on /tmp type tmpfs (rw,size=100M)
/var/log on /var/log.hdd type none (rw,bind)
ramlog-tmpfs on /var/log type tmpfs (rw,size=20M)
/dev/sda4 on /DataVolume type ext4 (rw,noatime,nodiratime)
/DataVolume/cache on /CacheVolume type none (rw,bind)
/DataVolume/shares on /shares type none (rw,bind)
/DataVolume/shares on /nfs type none (rw,bind)
none on /sys/kernel/security type securityfs (rw)
rpc_pipefs on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
/dev/md0 on /mnt/rootfs type ext3 (rw)
saving upgrade version and date to /var/log/version.log
postinst: new version is 02.41.05-034
sourcing new config files
master_package=apnc
update_container=
pkg_upgrades_dir=/CacheVolume/upgrade
postinst: list of packages to be installed on re-boot:
Th3V3ldt wrote:
There is no upgrade folder at /CacheVolume/ (and no rootfs.img)
It is probably getting deleted as soon as the md5 does not match
I would try using another wireless connection or a wired connection
I used a wired connection now.
Error again 
My log changed:
(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 …/apnc-024105-034-20130215.deb) …
preinst: currentRootDevice=/dev/md1
preinst: master_package_name=apnc
preinst: update_container=
Restore raid device: /dev/sda1
Restore raid device: /dev/sda2
Prepare for upgrade install to /dev/sda1 …
Stopping periodic command scheduler: crond failed!
Stopping standby monitor: monitorio1 pids were not killed
No process in pidfile ‘/var/run/standby.pid’ found running; none killed.
failed!
1 pids were not killed
No process in pidfile ‘/var/run/tally.pid’ found running; none killed.
failed!
PID file /var/run/mediaserver.pid not found, stopping server anyway…
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:05 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
Did the checksum check fail again?
I don’t know… thats all what i have in the log :S
What firmware is on your drive now?
Well, I tested again using auto update and now it went to 100%.
Meanwhile I’ve ssh to wdl and confirmed the md5 in the .img file.
Is now rebooting, let’s see if he wakes up.
Fingers crossed
I was on 02.32.05-144
It’s now ok, in the new version.
I don’t know what I made different but it’s now working… Thanks for your help.
Last question: I use a Mac… I should stick with TwonkyMedia instead of WD Media Server right?
Your welcome… Glad you got it going… Time for me to rest my eyes 
Th3V3ldt wrote:
I was on 02.32.05-144
Last question: I use a Mac… I should stick with TwonkyMedia instead of WD Media Server right?
I would maybe create a seperate thread for that question… Both servers should work ok but one may be better than the other depending on your needs.
Hello everyone,
I updated my Live Book and the WD Media Player patch.
Now de database in de media player-status is empty.
De shares are there and i have 12.000 photo’s en some video’s in de the public share.
Why does de WD Media Player does not collect them in the database?
I did a scan and a rebuild.
Thanks for reaction
(my english is not very good, excuse me…)
I’ll wait I think after the performance I had with the last update which killed my sleep mode, despite doing a complete reset and everything support emailed to do… it seems everytime there is an update things getted screwed or don’t work…
The ‘Alert message’ says "A new version of the firmware has been released. Please update your device." they missed off so you can beta test this update for us… NO THANKS I’ll stick with v02.32.05-046 and leave 02.41.05-034
for the time being thank you very much.
Got two identical emails informing me about the update. I’m hoping that’s a one time thing as unless there’s additional changes not listed in the release notes, I can’t find any compelling reason to update. I’m not experiencing any problems currently and don’t need the WD Media Server, so I’d rather leave well enough alone based on past update experiences.
Oh and requiring a firmware update to switch between Twonky and WD Media server doesn’t make any sense. It should just be an option in the settings GUI.
anybody done a successful update frmo 2.11 to 2.41? I haven’t changed anything from stock or in ssh. Just smartware backups and a few dozen photos for dlna
cman I went from 02.11.09-053 to this firmware no problems
Hi guys. After my first bad experience with WD Media Server decided to give it a second chance. Patched the firmware and WDMS has updated the data base without any prob. Than gave it a while (1 hour, or so) to dig through the content and started testing. It acts quite strange - streaming mpeg files and music without any problem. The issues I have are with avi and mkv files. The avi seem to be playable, but nothing is going on. Regarding mkv my TV (Panasonic G30 series) says it’s unplayable and BD player (Pioneer BDP-140) see no file at all. Also browsing is quite unstable and can freeze my device for a while. Does someone have similar issues? Any ideas how to solve? Thanks for any help!
Hi all, I’m currently using 02.32.05-046
It works for the most part… sometimes the shares can’t be seen but anyway…
I’ve since upgraded to Twonky 7.0.9 and installed two instances using this guide… http://community.twonky.com/twonky/topics/how_to_install_a_second_instance_of_twonky_server_on_wd_mybook_live_for_private_streaming
I’m not a massive fan of Twonky but it works… for the most part. I think I will leave this update for the moment, but if I were to install it would it wipe the Twonky 7 instances I have installed?.. thanks.
