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 22.98% done 29.76% done, 0:38 elapsed 33.88% done, 0:44 e 39.03% done, 0:51 elapsed 45.71% done, 0:57 elaps 53.34% done, 1:04 elapsed 62.14% done, 1: 69.63% done, 1:17 elapsed 75.08% 79.46% done, 1:31 elapsed 88. 93.42% done, 1:50 elapsed 97.61% donedone
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.