Cannot update to latest firmware

Hi all

For the last few months I have been trying to update my MBL to the latest firmware.  When I try to do it via the dashboard I get an 3118 message that the connection has timed out.  When I try to update through SSH I get the following output:

 updateFirmwareFromFile.sh:04/06/15 18:33:33:: ( /CacheVolume/updateFile.deb check_filesize ) updateFirmwareFromFile.sh:04/06/15 18:33:33:upgrade start: /CacheVolume/updateFile.deb check_filesize updateFirmwareFromFile.sh:04/06/15 18:33:33:check_size=check_filesize updateFirmwareFromFile.sh:04/06/15 18:33:36:blocksize_dpkg0=141119518 updateFirmwareFromFile.sh:04/06/15 18:33:36:blocksize_dpkg1= updateFirmwareFromFile.sh:04/06/15 18:33:36:blocksize_ls=141119518 updateFirmwareFromFile.sh:04/06/15 18:34:14:version_current=024303022 updateFirmwareFromFile.sh:04/06/15 18:34:14:version_newfile=024309038 updateFirmwareFromFile.sh:04/06/15 18:34:14:package_newfile=apnc updateFirmwareFromFile.sh:04/06/15 18:34:14:master_package_name=apnc updateFirmwareFromFile.sh:04/06/15 18:34:14:master_package_new=apnc updateFirmwareFromFile.sh:04/06/15 18:34:14:update_container= dsds (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. 18703 files and directories currently installed.) Preparing to replace apnc 02.43.09-038 (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. Kill Miocrawler Process… No miocrawler process is found Killed the mediacrawler process Mon Apr 6 11:40:35 PDT 2015 - %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 16: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 … Setting up apnc (02.43.09-038) … 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 /usr/local/sbin/sendAlert.sh: line 28: awk: command not found

I have tried contacting support but they have not answered.  I am linux savvy so if anyone can give me any hacking ideas I would love to hear them.

Thanks for your help

Spencer

Looks like a file corruption.  Best and most sure solution is to use a debrick process.  Use one of the guides on this forum. You will not lose your data.

Thanks for your reply.

I tried one of the debricking guides - replacing the reset button script but that did not work.  I have been in contact with WD support and they have asked me to replace the unit.

This is the second time that I have had to replace the unit.  :cry:

Spencer