Wd My Book Live Firmware Restore
Re: Recovery of original firmware on MyBook live ?
Hello, I'k having the verbal same problem as AntoxaVR6. I opened up my shiny new MyBook Live 2TB, found out that it was running Debian and that y'all could hands enable SSH. Seeing as clasp is officially released, I think "Hey, I should add the clasp repos and do an apt-get dist-upgrade", so I look at the sources.list, encounter that the squeeze repo is already there and do an apt-become update. It was missing the squeeze gpg central, which I idea was strange but decided to ignore and only downloaded it from http://ftp-master.debian.org/keys/archive-key-half-dozen.0.asc and installed it. I and then decided to do an apt-get upgrade before going for an all out dist-upgrade, and when information technology was washed the WebUI had stopped working. Using the information on the main page I figured out how to become it back up and running (php ini thing), but I decided I should revert to official firmware using the technique posted hither. When all was said and done though, I got the same bad checksum error so I re-downloaded iv times and compared the md5 to the 1 posted here http://customs.wdc.com/t5/My-Book-Alive/What-did-I-pause-quot-Upgrade-copy-failure-quot-when-updating/td-p/200472 (seems to be the same problem on the official boards), and they all failed (fifty-fifty though the md5 matched the same sum). Based on that give-and-take and my own observations, I would guess it is an incompatible version of dpkg or md5sum (more than probable md5sum since the person in the other thread reverted dpkg to the initial one, md5sum is the program reporting the initial mistake, and coreutils was updated). The versions I have are dpkg 1.15.8.10 and md5sum 8.5 (coreutils 8.v-one). If somebody with a make clean system could check the versions of these it would be much appreciated. Its non super critical at the moment (everything, including the WebUI seems to be working fine), merely I'm afraid to restart the device, or even disconnect my ssh session. Whatsoever aid would be neat, thanks.
OK, I tried downgrading to the latest coreutils from Lenny (six.10-half dozen), and I got the same problem. If I was sure that the everything was actually right I would supplant md5sum with a unproblematic plan to return 0 to the trounce, simply I have a feeling that something may actually be screwing up somewhere. It may still be as unproblematic as having to have exactly the right version of coreutils, merely something like how htye generate md5 sums shouldn't change (if information technology does, that is a serious problem).
I have no idea what is going incorrect. I riped apart the deb file, and the md5 of the rootfs.img matches that institute in the rootfs.md5 file (4d2551e3133bfe3180051d7ef0e58e17). The file size of the rootfs.img exactly matches that found in the postinstall script (2047803392). I have read the script in question like 10 times and the only pertinent role is:
echo "Re-create image to upgrade device ${upgradeDevice}" dd if=${imageFile} of=${upgradeDevice} > /dev/nada 2> /dev/naught echo "Compare checksum" dd if=${upgradeDevice} bs=${blockSize} count=${blockCount} 2> /dev/cipher | md5sum -c ${imageMd5} checksumOk=$? echo "ok ${checksumOk}" then unless the copy actually fails (for example upgradeDevice doesn't have enough space, or the local device doesn't take enough infinite to extract the deb) I don't run across whatever reason this would not piece of work. I may take to add a agglomeration of debug echo statements to their install scripts, repackage the deb and see what is going wrong.
On some other note, I'm non entirely sure how this works at all considering it extracts the img to / (and thus /CacheBolume/upgrade) and the rootfs.img is like 2GB, merely the rootfs is only like 1.9G total, in fact the only mount big enough to hold it is the Data Volume (unless it keeps an actress partition for installing the new rootfs to). (Edit: after some experimenting I adamant that it does store the data on the Information Book.)
Ok, by editing the post install script (which does all the legwork) to add some more debug statements I take adamant that it is infact not copying the unabridged img file, dd is but writing 31231 64k blocks when information technology needs to copy 31247 blocks (yes it is off by like one MB). I have no idea why this worked the kickoff time I installed this update (beginning thing I did out of the box), and not now (except for maybe the fact that the newer packages might be larger and are taking upwardly space needed by other stuff).
Then, for some reason the new rootfs is beingness created simply a little bit too small. Latter today I will try to debug the cosmos process. I tried removing some unnecessary packages to free up space, only that didn't help at all, so the boosted space used by the newer packages is almost certainly not the issue. It is possible that the finish of that epitome is just padding anyway and it wouldn't matter if I just strength the installer past information technology, but I really don't desire to practise that. If anybody else has any ideas they would be greatly appreciated. I repent for the giant wall of text this post has become, simply I hate double posting.
Re: Recovery of original firmware on MyBook live ?
did y'all check the value of ${blockCount} ?
Re: Recovery of original firmware on MyBook live ?
Ya, that is where the 31247 is from, and the 31231 is what is existence reported by dd as being written (it gives an out of infinite error) after removing the "> /dev/null two> /dev/zip" (which should exist "> /dev/cypher 2>&i" btw (it bothers me)). 31247 is as well the correct number of blocks for the size of the rootfs.img to the byte (2047803392).
Re: Recovery of original firmware on MyBook live ?
You said : "it gives an out of space error"
You should increment the infinite somewhere.
I may be wrong but 'count=?' in conjonction with 'bs' parameter in i of 'dd' action could be the point.
I remember having that Pb in a unlike environnement. I simply increased a bit the 'count' value
Re: Recovery of original firmware on MyBook alive ?
but when mke2fs runs it doesn't allocate enough blocks, and if I try to force information technology, information technology says at that place isn't enough space on the volume.
Re: Recovery of original firmware on MyBook live ?
Could you clean a bit the book
Re: Recovery of original firmware on MyBook live ?
Thanks DRayX for your post which helped me track the problem downward.
Turns out that the upgrade we did from lenny to squeeze replaced mdadm with a version that uses a new, larger metadata header by default (it even complains about the old header in the update.log above), so the md0 partition actually is 1MB smaller when dd writes to it.
This can be fixed easily past appending "metadata=0.90" to the CREATE entry in /etc/mdadm/mdadm.conf (which existed after the upgrade, it does not exist in the original Firmware 01.05.07) and using updateFirmwareFromFile.sh one last time.
Source: http://mybookworld.wikidot.com/forum/t-307650
Posted by: sellarsvate1986.blogspot.com
0 Response to "Wd My Book Live Firmware Restore"
Post a Comment