- WD Community
- :
- Network Devices
- :
- My Book Live
- :
- Upgrade to latest firmware failing
- WD Community
- News & Assistance
- Announcements
- New to Community
- Forum Feedback
- Off-Topic
- Software & Apps
- WD Software
- WD Mobile Apps
- Software & Accessory Ideas
- WD TV Live Streaming
- Live Streaming Discussions
- Live Streaming Firmware
- Live Streaming Ideas
- Live Streaming Issues
- WD TV Live Hub
- Hub Discussions
- Hub Firmware
- Hub Themes
- WD TV Live Hub Ideas
- WD TV Live Hub Issue Reporting
- WD TV Play
- WD TV Play
- Live & Live Plus
- Live Discussions
- Live Firmware
- Elements Play
- Elements Play
- External Drives
- Mac Externals
- PC Externals
- Portable Drives
- External Drive Ideas
- Network Devices
- Networking Devices
- Live Duo
- Sentinel
- My Book Live
- Other Network Drives
- Network Product Ideas
- Internal Drives
- Desktop & Portable
- Internal Drive Ideas
- Anuncios
- Noticias
- Nuevo a La Comunidad
- Los Productos de WD
- Software y Accesorios
- Reproductores Multimedia
- Unidades de Red
- Unidades Externas
- Unidades Internas
- Ankuendigungen
- Neuigkeiten
- Neu in der Community
- WD Produkte
- WD Programme
- WD TV Media Player
- Netzwerk Laufwerke
- Externe Laufwerke
- Interne Laufwerke
- Annunci
- Annunci e Novita'
- Nuovo per La Comunita'
- Prodotti WD
- Programmi & Accessori
- Riproduttori Multimediali
- Dischi di Rete
- Dischi Esterni
- Dischi Interni
- WD TV Legacy
- Hub Network
- Live Networking
- WD TV HD
- WD TV Mini
- Software
- WD Photos
- Other Software & Accessories
- Hard Drives
- WD ShareSpace
- Other Externals
- Other Internal Drives
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic to the Top
- Bookmark
- Subscribe
- Printer Friendly Page
Upgrade to latest firmware failing
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-24-2012 04:55 PM
Hi,
The datatransfer to MBL 2TB model was really slow (<1MB/s over wifi and similar over LAN). Looking at the firmware, I found that it was really old 1.x.
I tried upgrading the firmware from the UI - it kept failing. So I SSH'd in and tried a manual update. It failed giving the following error:
<...>
Compare checksum
-: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match
Going through old forums - I saw that the problem seemed to be with file-sizes and that adding metadata=0.90 to the mdadm.conf file resolved it.
/etc/mdadm was empty. So, I tried to re 'apt-get' it. That didnt work but after removing mdadm, doing 'apt-get update' to get the new packagelist and reinstalling it, there was a mdadm.conf. I made the changes suggested in the forum.
However, the update still failed. Here's the log file:
(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.
17688 files and directories currently installed.)
Preparing to replace apnc 02.11.09-053 (using apnc-021109-053-20120413.deb) ...
stopping duplicate md device /dev/md0
mdadm: stopped /dev/md0
Prepare for upgrade install...
Stopping periodic command scheduler: crond failed!
Stopping standby monitor: monitoriostart-stop-daemon: warning: failed to kill 1460: N
o such process
1 pids were not killed
No process in pidfile '/var/run/standby.pid' found running; none killed.
failed!
PID file /var/run/mediaserver.pid not found, stopping server anyway...
twonkymedia: no process killed
Stopping itunes server: forked-daapd.
/var/lib/dpkg/tmp.ci/preinst: line 96: /etc/init.d/orion: No such file or directory
Prepare for upgrade pkg install...
mdadm: /dev/sda1 appears to contain an ext2fs file system
size=1999808K mtime=Wed Dec 31 16:00:01 1969
mdadm: size set to 1999808K
mdadm: creation continuing despite oddities due to --run
mdadm: array /dev/md0 started.
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=1 blocks, Stripe width=0 blocks
125184 inodes, 499952 blocks
24997 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=515899392
16 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
Superblock backups stored on blocks:
Fragment size=4096 (log=2)
Stride=1 blocks, Stripe width=0 blocks
125184 inodes, 499952 blocks
24997 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=515899392
16 block groups
32768 blocks per group, 32768 fragments per group
7824 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Checking for bad blocks (read-only test): 4.84% done, 0:05 elapsed 14. 18.87% done, 0:24 elapsed
Writing inode tables: done
Creating journal (8192 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 31 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
preinst: current root device=/dev/md1
preinst: upgrade root device=/dev/md0
Unpacking..
Unpacking replacement apnc ...
Unpack timeout occurred
failed 202 "upgrade download failure"
stopping duplicate md device /dev/md0
mdadm: stopped /dev/md0
Setting up apnc (02.11.09-053) ...
/var/lib/dpkg/info/apnc.postinst: line 10: /etc/system.conf: No such file or director
y
blockSize=64k blockCount=31247
cat: /tmp/upgrade_part: No such file or directory
postinst: upgradeDevice= /dev/md0
postinst: currentRootDevice= /dev/md1
Copy image to upgrade device /dev/md0
Compare checksum
-: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match
ok 1
postinst: replaced old version 010507
Upgrade failed
mdadm: /dev/md0 does not appear to be an md device
mdadm: Cannot open /dev/sda1: Device or resource busy
DF shows:
Filesystem Size Used Avail Use% Mounted on
tmpfs 50M 0 50M 0% /lib/init/rw
udev 10M 10M 0 100% /dev
tmpfs 50M 0 50M 0% /dev/shm
rootfs 1.9G 968M 858M 54% /
tmpfs 50M 5.2M 45M 11% /tmp
ramlog-tmpfs 20M 20M 0 100% /var/log
/dev/sda4 1.9T 89G 1.8T 5% /DataVolume
Any ideas?
Thanks,
M.
Re: Upgrade to latest firmware failing
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-24-2012 11:55 PM - edited 04-24-2012 11:59 PM
Just an idea: Maybe you should try a manual install of the very first firmware update from v. 1 to v. 2.
Also, and please excuse me because I'm far from a computer expert, I'm not sure what you mean when you say you "SSH'd in". Couldn't you access the interface anymore to try the manual update from there?
Good luck.
Best regards,
Joe
P.S. The reason I saw your note was that - like so many other people - I just tried the automatic update from the web interface and got stung by the "stuck at 10%" bug, which this version was supposed to fix (ha-ha).
Fortunately, I still had the web interface open, so I opened another tab in Firefox, downloaded the file for the manual update, installed it through the web interface, and it worked, thank God.
Perhaps I should also mention here that my OS is Windows XP sp-3, and I'm using the FF test build "Namoroka", which is based on the good old v. 3.6.
Re: Upgrade to latest firmware failing
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-25-2012 10:24 AM
Hi,
I used the shell to get at the error message (as to why the update was failing). I tried to use the manual update from UI which kept failing.
Is there a link to the 1.x to 2.x upgrade file? Couldnt find it on the WD site.
Thanks.
Re: Upgrade to latest firmware failing
[ Edited ]- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Highlight
- Email to a Friend
- Report Inappropriate Content
04-25-2012 04:33 PM - edited 04-25-2012 04:41 PM
I think this is the firmware file you want?
http://download.wdc.com/nas/apnc-010507-20110714.d
This is my MBL's update history.
01.04.06 Wed Apr 27 16:14:52 BST 2011 01.05.07 Thu Jul 21 00:15:25 BST 2011 02.00.35-423 Sat Jul 30 00:09:31 BST 2011 02.01.06-026 Wed Aug 3 23:22:00 BST 2011 02.02.02-020 Thu Sep 8 11:53:50 BST 2011 02.03.01-024 Wed Oct 26 10:31:45 BST 2011 02.10.09-124 Fri Nov 18 01:33:41 GMT 2011 02.10.12-129 Fri Mar 16 01:44:56 GMT 2012 02.11.09-053 Mon Apr 23 22:13:52 BST 2012
It looks like your MBL already has the last v1 firmware installed.
| Forums | Ideas | News and Announcements | Register | Sign in | Help | Forum Guidelines | |

