I just did the upgrade from 021109-053 to 024105-034
when I try to switch from either dlna package using the deb files
I get a 31101 error message saying invalid firmware package
I just did the upgrade from 021109-053 to 024105-034
when I try to switch from either dlna package using the deb files
I get a 31101 error message saying invalid firmware package
I also tried this
Twonky is missing after upgrading from 021109-053 to 024105-034
http://community.wdc.com/t5/My-Book-Live/Twonky-is-missing-after-upgrading-from-021109-053-to-024105-034/td-p/546090
No problems upgrading from 02.11.09-053 here…
Had you made alot of changes to your twonky install?
Check /CacheVolume/install.log for errors
while yes I have upgraded twonky
but it was done in a way that conformed to the way wd installed 5.1.9
I looked at the upgrade scripts related to the new dlna stuff
didnt help
But I guess the biggest question is this
with all other firmware if one re-applied it, it would usually resolve things
doing that on the current one does not
Im getting the same 31101 error with the updateFile.deb from the guide
Im now going to do a dowgrade by hand, and then go up again
it will be a bit to know the results
So what I have done so far
I used the downgrade.sh back to apnc-021109-053-20120413
I then attempted to upgrade via the wd gui to apnc-024105-034-20130215
It gave me 31106 error upgrade not good
I then used the downgrade.sh up to apnc-024105-034-20130215
which once again gave me no dlna server
I then reapplied via the wd gui to apnc-024105-034-20130215
which now gives me the WD Media Server installed and running
BUT, once again, if I attempt to use either of the dlna switching .deb files
I get the 31101 error message
This is so messed up
Here is the log
updateFirmwareFromFile.sh:02/27/13 19:45:38:upgrade start: /CacheVolume/Twonky5MediaServerPatch.deb
updateFirmwareFromFile.sh:02/27/13 19:45:38:check_size=
updateFirmwareFromFile.sh:02/27/13 19:45:38:version_current=024105034
updateFirmwareFromFile.sh:02/27/13 19:45:38:version_newfile=010001
updateFirmwareFromFile.sh:02/27/13 19:45:38:package_newfile=apnc-twonky
updateFirmwareFromFile.sh:02/27/13 19:45:38:master_package_name=apnc
updateFirmwareFromFile.sh:02/27/13 19:45:38:master_package_new=apnc
updateFirmwareFromFile.sh:02/27/13 19:45:38:update_container=twonky
(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.
19089 files and directories currently installed.)
Unpacking apnc-twonky (from .../Twonky5MediaServerPatch.deb) ...
preinst: currentRootDevice=/dev/md1
preinst: master_package_name=apnc
preinst: update_container=twonky
: Searching for previously installed Twonky binaries...
: not found.
Install not supported
dpkg: error processing /CacheVolume/Twonky5MediaServerPatch.deb (--install):
subprocess new pre-installation script returned error exit status 1
Errors were encountered while processing:
/CacheVolume/Twonky5MediaServerPatch.deb
updateFirmwareFromFile.sh:02/27/13 19:45:40:failed 200 "invalid firmware package"
Error fw_update_status: failed 200 "invalid firmware package"
Here is my log for the WD DLNA server install
updateFirmwareFromFile.sh:02/26/13 23:57:37:upgrade start: /CacheVolume/WDMediaServerPatch.deb
updateFirmwareFromFile.sh:02/26/13 23:57:37:check_size=
updateFirmwareFromFile.sh:02/26/13 23:57:38:version_current=024105034
updateFirmwareFromFile.sh:02/26/13 23:57:38:version_newfile=010001
updateFirmwareFromFile.sh:02/26/13 23:57:38:package_newfile=apnc-access
updateFirmwareFromFile.sh:02/26/13 23:57:38:master_package_name=apnc
updateFirmwareFromFile.sh:02/26/13 23:57:38:master_package_new=apnc
updateFirmwareFromFile.sh:02/26/13 23:57:38:update_container=access
Selecting previously deselected package apnc-access.
(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.
19025 files and directories currently installed.)
Unpacking apnc-access (from .../WDMediaServerPatch.deb) ...
preinst: currentRootDevice=/dev/md1
preinst: master_package_name=apnc
preinst: update_container=access
: Searching for previously installed Twonky binaries...
: found.
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!
PID file /var/run/mediaserver.pid not found, stopping server anyway...
Stopping itunes server: forked-daapd.
Kill Miocrawler Process...
No miocrawler process is found
Tue Feb 26 18:58:55 EST 2013 - %W - Communication Manager - process is not running
preinst: current device=/dev/md1
preinst: upgrade device=
Unpacking..
Setting up apnc-access (01.00.01) ...
postinst: upgradeDevice=
postinst: currentRootDevice=/dev/md1
postinst: upgradePath=/
sourcing new config files
master_package=apnc
update_container=access
pkg_upgrades_dir=/CacheVolume/upgrade
postinst: list of packages to be installed on re-boot:
-rwxrwxr-x 1 root www-data 3600408 Feb 15 13:39 /CacheVolume/upgrade/dlna-server-access_02.00.00-95909_powerpc.deb
-rwxrwxr-x 1 root www-data 8362 Feb 15 13:39 /CacheVolume/upgrade/dlna-server-twonky_05.00.01-95580_powerpc.deb
postinst-patch_apnc_access: apnc-access /
twonky-hollow: /
twonky-hollow: twonky_save()
update_utilities: bom_oldpkg()
logger: dlna-server-access package state:
logger: dlna-server-twonky package state: ii
pkg_state_access=
pkg_state_twonky=ii
postinst-patch_apnc_access: selecting dlna-server-access..
Setting update date to current date: Tue Feb 26 18:58:57 EST 2013
A reboot is required for the upgrade to take effect.
postinst complete.
And here is my Twonky install log for comparison
updateFirmwareFromFile.sh:02/27/13 20:34:54:upgrade start: /CacheVolume/Twonky5MediaServerPatch.deb
updateFirmwareFromFile.sh:02/27/13 20:34:54:check_size=
updateFirmwareFromFile.sh:02/27/13 20:34:55:version_current=024105034
updateFirmwareFromFile.sh:02/27/13 20:34:55:version_newfile=010001
updateFirmwareFromFile.sh:02/27/13 20:34:55:package_newfile=apnc-twonky
updateFirmwareFromFile.sh:02/27/13 20:34:55:master_package_name=apnc
updateFirmwareFromFile.sh:02/27/13 20:34:55:master_package_new=apnc
updateFirmwareFromFile.sh:02/27/13 20:34:55:update_container=twonky
Selecting previously deselected package apnc-twonky.
(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.
19105 files and directories currently installed.)
Unpacking apnc-twonky (from .../Twonky5MediaServerPatch.deb) ...
preinst: currentRootDevice=/dev/md1
preinst: master_package_name=apnc
preinst: update_container=twonky
: Searching for previously installed Twonky binaries...
: found.
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 Access Daemons: dms_smm mpe_server.
Stopping itunes server: forked-daapd.
Kill Miocrawler Process...
No miocrawler process is found
Wed Feb 27 15:35:09 EST 2013 - %W - Communication Manager - process is not running
preinst: current device=/dev/md1
preinst: upgrade device=
Unpacking..
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/dlna_bom-update', which is also in package apnc-access 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/twonky_utilities', which is also in package apnc-access 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-access 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/postinst-patch_apnc', which is also in package apnc-access 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-access 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-access 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-access 01.00.01
dpkg: warning: overriding problem because --force enabled:
trying to overwrite '/CacheVolume/upgrade/upgrade_utilities', which is also in package apnc-access 01.00.01
(Noting disappearance of apnc-access, which has been completely replaced.)
Setting up apnc-twonky (01.00.01) ...
postinst: upgradeDevice=
postinst: currentRootDevice=/dev/md1
postinst: upgradePath=/
sourcing new config files
master_package=apnc
update_container=twonky
pkg_upgrades_dir=/CacheVolume/upgrade
postinst: list of packages to be installed on re-boot:
-rwxrwxr-x 1 root www-data 3600408 Feb 15 13:39 /CacheVolume/upgrade/dlna-server-access_02.00.00-95909_powerpc.deb
-rwxrwxr-x 1 root www-data 8362 Feb 15 13:39 /CacheVolume/upgrade/dlna-server-twonky_05.00.01-95580_powerpc.deb
postinst-patch_apnc_twonky: apnc-twonky /
twonky-hollow: /
twonky-hollow: twonky_save()
update_utilities: bom_oldpkg()
logger: dlna-server-access package state: ii
logger: dlna-server-twonky package state: rc
pkg_state_access=ii
pkg_state_twonky=rc
postinst-patch_apnc_twonky: selecting dlna-server-twonky..
Setting update date to current date: Wed Feb 27 15:35:11 EST 2013
A reboot is required for the upgrade to take effect.
postinst complete.
Much appreciated
Still doing some other test, will pass on results in a bit
It’s bombing out finding pre-existing Twonky
# Check for pre-existing Twonky binaries on the unit
twonky_allow ()
{
logger -s -t "${logtag}" "Searching for previously installed Twonky binaries..."
if [! -f ${upgradePath}${TWONKY_PATH}/twonkymediaserver] && [! -f ${TWONKY_SAVE}/twonkymediaserver]; then
logger -s -t "${logtag}" "not found."
return 1
else
logger -s -t "${logtag}" "found."
fi
return 0
I think this is the script of importance… Seems it’s not finding /usr/local/twonkymedia-5/
So my guess is your MBL does not have Twonky installed to that path
TWONKY_PATH=/usr/local/twonkymedia-5/
TWONKY_SAVE=/CacheVolume/twonkymedia-5/
# Save Twonky binaries on upgrade
twonky_save ()
{
logger -s -t "${logtag}" "twonky_save()"
if [-f ${TWONKY_PATH}twonkymediaserver]; then
if [! -f ${upgradePath}${TWONKY_PATH}twonkymediaserver]; then
logger -s -t "${logtag}" "Copying twonky binaries to upgrade path.."
mkdir -p ${upgradePath}${TWONKY_PATH}
cp -rpv ${TWONKY_PATH}* ${upgradePath}${TWONKY_PATH}
fi
if [! -f ${TWONKY_SAVE}twonkymediaserver]; then
mkdir -p ${TWONKY_SAVE}
(cd ${TWONKY_PATH} && find . -type f -exec md5sum {} \;) >/tmp/twonkymedia.md5sums
cp -rpv ${TWONKY_PATH}* ${TWONKY_SAVE}
##*/
mv -v /tmp/twonkymedia.md5sums ${TWONKY_SAVE}
sync
echo 3 > /proc/sys/vm/drop_caches
cd ${TWONKY_SAVE}
md5sum -c twonkymedia.md5sums
if [$? -ne 0]; then
logger -s -t "${logtag}" "Twonky save to CacheVolume failed."
else
logger -s -t "${logtag}" "Twonky save to CacheVolume was successful."
fi
cd -
fi
fi
}
# Recover Twonky binaries on re-upgrade to Twonky
twonky_recover ()
{
logger -s -t "${logtag}" "Recovering Twonky binaries..."
if [-f ${TWONKY_SAVE}/twonkymediaserver -a ! -f ${TWONKY_PATH}/twonkymediaserver]; then
mkdir -p ${TWONKY_PATH}
cp -rpfv ${TWONKY_SAVE}/* ${TWONKY_PATH}
#*/
sync
echo 3 > /proc/sys/vm/drop_caches
(cd ${TWONKY_PATH} && md5sum -c twonkymedia.md5sums)
if [$? -ne 0]; then
logger -s -t "${logtag}" "Twonky recovery from cache volume failed."
fi
fi
}
# Restore Twonky binaries to CacheVolume after factory-restore
twonky_restore ()
{
logger -s -t "${logtag}" "Restoring saved Twonky binaries..."
if [-f ${TWONKY_PATH}/twonkymediaserver -a ! -f ${TWONKY_SAVE}/twonkymediaserver]; then
mkdir -p ${TWONKY_SAVE}
cp -rpfv ${TWONKY_PATH}/* ${TWONKY_SAVE}
#*/
sync
echo 3 > /proc/sys/vm/drop_caches
(cd ${TWONKY_SAVE} && md5sum -c twonkymedia.md5sums)
if [$? -ne 0]; then
logger -s -t "${logtag}" "Twonky restore to saved cache failed."
else
logger -s -t "${logtag}" "Twonky restore to saved cache succeeded."
fi
fi
}
# Check for pre-existing Twonky binaries on the unit
twonky_allow ()
{
logger -s -t "${logtag}" "Searching for previously installed Twonky binaries..."
if [! -f ${upgradePath}${TWONKY_PATH}/twonkymediaserver] && [! -f ${TWONKY_SAVE}/twonkymediaserver]; then
logger -s -t "${logtag}" "not found."
return 1
else
logger -s -t "${logtag}" "found."
fi
return 0
}
Thanks for looking at that, much appreciated
I can see how its possible that it didnt work on a modified version of twonky
But not why it didnt when I re-applied the previous firmware,
which resets twonky all back to default files and settings
should have taken care of that issue when updateing to the latest
On a postivie note, I finally did get a working setup again
I used your downgrade.sh and the rootfs.img from apnc-021109-053-20120413.deb
Then used the update from file method in the wd gui with apnc-023205-046-20120910.deb
Then used the wd update from the web to go to 02.41.05 – 034
which did have a working twonky installed
I then was able to install WDMediaServerPatch.deb
and then back to Twonky5MediaServerPatch.deb
My best guess is maybe it has something to do with the prior state of 021109-053
and going directly to 024105-034 that there might be an issue
as I tried that combo a few times, without luck
but going from 021109-053 to 023205-046 and then to 024105-034 worked as it should have
Once again, thanks for taking the time to look at the issue
No problem, glad your up and running
some other thoughts about what I saw, and this new firmware
for the most part, the prior firmware updates have usually just consisted of a rootfs.img
This new one is that and some post install packages
which in the case of your downgrade.sh guide
begs an interesting question
Since this new firmware is more than just a rootfs.img
One might actually have to do a two step process to re-apply firmware
if one only does the rootfs.img is, its not the complete install, that I can see?
which begs another question
I wonder why they just didnt have these pre-installed into the img?
All the firmwares have post and pre install scripts, you will only see them if you open the .deb in 7-zip 9.10 or lower. They are stored in control.tar.gz
The scripts for twonky and the wd dlna server were new to this firmware and are extracted from the .deb to /CacheVolume/upgrade
These scripts are in the data.tar.lzma
/CacheVolume/upgrade/ [3.5 M]
|-dlna_bom-update (3.4 k)
|-dlna-server-access_02.00.00-95909_powerpc.deb (3.4 M)
|-dlna-server-twonky_05.00.01-95580_powerpc.deb (8.2 k)
|-postinst-patch_apnc (850 b)
|-postinst-patch_apnc_access (651 b)
|-postinst-patch_apnc_dlna (536 b)
|-postinst-patch_apnc_twonky (651 b)
|-twonky_utilities (2.8 k)
|-upgrade_utilities (724 b)
|-upgrade-patch_twonkymediaserver-hollow (451 b)
|
rootfs.img and rootfs.md5 are also extracted to /CacheVolume/Upgrade but get deleted after a successful upgrade
I havent looked at all the previous firmware deb files
but that least few when viewed with 7zip only show the rootfs.img and rootfs.md5
which is where my assumptions arose from
thanks for the clarification
I’m leaning towards something else being the cause as I went straight from 02.11.09-053 to the new firmware and didn’t run into the issues you did. Everything was pretty much factory except a few changes to samba config, ftp config, and resetButtonAction.sh
I would tend to agree
But its on to other tasks at the moment, will relook at this again another time
thanks again
ps
now I have to mentally prepare myself for the posts from people
who upgraded twonky following my guide on the twonky community
as there were already two others with the same scenario as me
in a different thread
For reference here is that guide:
How to upgrade Twonky Server on WD MyBook Live
http://community.twonky.com/twonky/topics/how_to_upgrade_twonky_server_on_wd_mybook_live?page=1
Hi im suffering the same problem it seems there is no twonky version can someone give me a step by step guide to get it twonky back or upgrade to the wdmedia server.i had previously upgraded to twonky 7.9 so maybe thats my problem
ok seems to be working now so forget my previous post