[Upgrading, Modifying and Unlocking] Grank:
Ooookay, so...

I tried to do a Nandroid backup, and I got a couple of errors but it seemed like it might have worked okay. I was going to post the errors in here to see whether or not people thought they were critical, but I thought I'd first generate .img files from the .tar files as per the screen output of the script.

That worked fine for the system tar...

Somehow, tar x on the userdata tar in some way corrupted my linux VM's entire file system.

It spat out a bunch of errors about not being able to find files, and then suddenly my linux filesystem was read-only.

Confused, I rebooted, or attempted to, and now VirtualBox says my VHD has an invalid header.

Trying to attach the VHD in windows Disk Management tells me that it's corrupt and unreadable.

The hell??

Here are the errors I experienced while the backup sh was running.

First, one of the blocks refuses to mount:

mounting system and data read-only on device
mount: mounting /dev/block/mtdblock6 on /cache failed: Device or resource busy

And then, I don't know what to make of this part. It ends with a successful hash comparison, which is weird since given all the errors while dumping the img, but it seems like there are silenced errors creating the hash on the device anyway (the blank "mtd:" lines don't happen for any other md5sum get):

Getting md5sum on device for pkg...done (mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
mtd:
06cbcd695972b887001cd8127ba4fa30)
Dumping pkg from device over tcp to /home/grant/Android/Backup20100804//pkg.img...
mtd: ECC errors (0 soft, 1 hard) at 0x002c0000
mtd: ECC errors (0 soft, 1 hard) at 0x002e0000
mtd: ECC errors (0 soft, 1 hard) at 0x00300000
mtd: ECC errors (0 soft, 1 hard) at 0x00320000
mtd: ECC errors (0 soft, 1 hard) at 0x00340000
mtd: ECC errors (0 soft, 1 hard) at 0x00360000
mtd: ECC errors (0 soft, 1 hard) at 0x00380000
mtd: ECC errors (0 soft, 1 hard) at 0x003a0000
mtd: ECC errors (0 soft, 1 hard) at 0x003c0000
mtd: ECC errors (0 soft, 1 hard) at 0x003e0000
mtd: ECC errors (0 soft, 1 hard) at 0x00400000
mtd: ECC errors (0 soft, 1 hard) at 0x00420000
mtd: ECC errors (0 soft, 1 hard) at 0x00440000
mtd: ECC errors (0 soft, 1 hard) at 0x00460000
mtd: ECC errors (0 soft, 1 hard) at 0x00480000
mtd: ECC errors (0 soft, 1 hard) at 0x004a0000
mtd: ECC errors (0 soft, 1 hard) at 0x004c0000
mtd: ECC errors (0 soft, 1 hard) at 0x004e0000
mtd: ECC errors (0 soft, 1 hard) at 0x00500000
mtd: ECC errors (0 soft, 1 hard) at 0x00520000
mtd: ECC errors (0 soft, 1 hard) at 0x00540000
mtd: ECC errors (0 soft, 1 hard) at 0x00560000
done
Comparing md5sum...md5sum verified for pkg.img

I didn't capture the errors that tar spit out when working with userdata.tar, partly because tar blanked the screen area above its working area, but I'm pretty sure the ones at the bottom were something along the lines of no such file or directory.

I will have to go build another VM right away... I'm afraid to even reboot my phone out of Nandroid in case it has corrupted my phone's operating system in some way. I don't have a backup at all since the one I had just generated is on the VHD that just got toasted :(