So making sure I'm reading this right. Renaming your Nandroid to take out the space didn't work or wouldn't work because the nandroid wasn't made correctly because part of the backup scripts couldn't handle the space. Correct?
Actually, the OP (Jonathan) did not indicate that he actually tried to restore the Nandroid backup after removing the space from the Nandroid backup's directory name. Rather, he simply re-ran the backup without a space in the backup's filename.
I pulled-up a version of the nandroid-mobile.sh (v2.2.2) script that is used for the Eris and looked again at the MD5 checking code:
Code:
[FONT=Courier New]cd $RESTOREPATH[/FONT] (i.e., the full /sdcard/nandroid/.... backup directory path)
[FONT=Courier New]<snip>[/FONT]
[FONT=Courier New]if [ ! -f $RESTOREPATH/nandroid.md5$DEFAULTEXT ]; then[/FONT]
[FONT=Courier New]$ECHO "[COLOR=blue]error: $RESTOREPATH/nandroid.md5 not found, cannot verify backup data[/COLOR]"[/FONT]
[FONT=Courier New]exit 1[/FONT]
[FONT=Courier New]fi[/FONT]
[FONT=Courier New]<snip>[/FONT]
[FONT=Courier New]$ECHO "Verifying backup images..."[/FONT]
[FONT=Courier New]md5sum -c nandroid.md5[/FONT]
[FONT=Courier New]if [ $? -eq 1 ]; then[/FONT]
[FONT=Courier New]$ECHO "[COLOR=red]Error: md5sum mismatch, aborting[/COLOR]"[/FONT]
[FONT=Courier New]exit 1[/FONT]
[FONT=Courier New]fi[/FONT]
As you can see, there is a test to check to see if the nandroid.md5 file exists. I would image that this test would fail if there is a space in the RESTOREPATH variable name (it certainly returns an error status 2 if you try to cd to a directory with a space in it without first escaping each space character).
So, I'm still a little skeptical as to whether or not a space in the filename will lead to an MD5 mismatch error. From what I can tell, it should not. The only scenario that I can imagine is that if the particular version of nandroid-mobile.sh is coded differently from the above and is possibly interpreting an error status from the cd command as an error in the md5sum utility (which I still find unlikely).
If the OP (Jonathan) still has the original Nandroid backup in question, it would be interesting for him to:
- do an
adb shell
-
cd to the Nandroid backup directory (escaping the space if necessary)
- run
md5sum -c nandroid.md5 (or
busybox md5sum -c nandroid.md5)
and report what he finds. This would actually tell us if there were MD5 checksum errors in his backup. He also did not indicate if he had a full charge on his phone when the Nandroid backup was made (or when the restore was attempted)--I don't for sure that having a low charge will make the reading from the /sdcard faulty or not (I do know that the nandroid-mobile.sh script will warn you if you attempt a backup or restore with less than 30% charge).
It should look similar to the following:
Code:
# [COLOR=blue]cd /sdcard/nandroid/<your phone's serial #>/BDS-20100821-1454-ieo[/COLOR]
# [COLOR=blue]ls[/COLOR]
ls
boot.img
system.img
data.img
nandroid.md5
# [COLOR=blue]md5sum -c nandroid.md5[/COLOR]
md5sum -c nandroid.md5
boot.img: OK
data.img: OK
system.img: OK
# [COLOR=blue]busybox md5sum -c nandroid.md5[/COLOR]
busybox md5sum -c nandroid.md5
boot.img: OK
data.img: OK
system.img: OK
Jonathan, you game?