Hi, All,
I've found a problem which might explain some of the quirkiness going on here. I discovered that after installing the ROM (2.5.1), while still in recovery if I connect with "adb shell", and then run "e2fsck -fv /dev/block/mmcblk0p9" (which is /system) I'd get a number of filesystem errors. I repeatedly tried formating /system and reinstalling the ROM and this would happen every time, which suggests to me that either my phone has some sort of memory error (which I've seen no other indication of), or there's something about how the ROM has been packaged or is being extracted which is giving the inconsistent filesystem. Perhaps the base system it's being packaged from has an inconsistent filesystem?
The problem can be solved by doing a "e2fsck -fyv /dev/block/mmcblk0p9" (which will answer "y" to all the repair questions), and then you can delete the many files in the /system/lost+found directory to reclaim several megabytes of space.
It'd be great if a few others can boot into recovery and try "adb e2fsck -fv /dev/block/mmcblk0p9" to see if your filesystem is also corrupted (and while you're there, try the same command with mmcblk0p10 instead of mmcblk0p9 to check your /data partition); if so, there's definitely something going on with the packaging.
Bill