[Nexus One Android Development] dvdschnck:
From my recovery.log, during the ROM write process:

What was intended here, I wonder??? ----> chown of 0755 to 0 2000 failed <----

minzip: Extracted file "/system/xbin/showslab"
minzip: Extracted file "/system/xbin/sqlite3"
minzip: Extracted file "/system/xbin/strace"
minzip: Extracted file "/system/xbin/su"
I:read: ui_print =>> Symlink processing.................
=>> Symlink processing.................I:read: ui_print

I:read: ui_print =>> Setting permissions................
=>> Setting permissions................I:read: ui_print

set_perm: chown of /system/etc/init.d/01data2sd to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/init.d/01data2sd to 777 failed: No such file or directory
set_perm: chown of /system/bin/sysro to 0 0 failed: No such file or directory
set_perm: chmod of /system/bin/sysro to 11223 failed: No such file or directory
set_perm: chown of /system/bin/sysrw to 0 0 failed: No such file or directory
set_perm: chmod of /system/bin/sysrw to 11223 failed: No such file or directory
set_perm: chown of /system/bin/nano to 0 0 failed: No such file or directory
set_perm: chmod of /system/bin/nano to 11223 failed: No such file or directory
set_perm: chown of /system/bin/sqlite3 to 0 0 failed: No such file or directory
set_perm: chmod of /system/bin/sqlite3 to 777 failed: No such file or directory
set_perm: chown of 0755 to 0 2000 failed: No such file or directory
set_perm: chmod of 0755 to 755 failed: No such file or directory
set_perm: chown of 0755 to 0 2000 failed: No such file or directory
set_perm: chmod of 0755 to 755 failed: No such file or directory
package_extract_file: no /insert.sh in package
set_perm: chown of /tmp/insert.sh to 0 0 failed: No such file or directory
set_perm: chmod of /tmp/insert.sh to 777 failed: No such file or directory
about to run program [/tmp/insert.sh] with 1 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
I:read: ui_print =>> Savaged Zen EVO Kernel Mod for N1..
=>> Savaged Zen EVO Kernel Mod for N1..minzip: Extracted file "/tmp/dump_image"
minzip: Extracted file "/tmp/mkbootimg"
minzip: Extracted file "/tmp/mkbootimg.sh"
minzip: Extracted file "/tmp/unpackbootimg"
minzip: Extracted file "/tmp/zImage"
about to run program [/tmp/dump_image] with 3 args
I:read: ui_print

I:read: ui_print =>> GCC 4.6.1 ToolChain by ch33kybutt..
=>> GCC 4.6.1 ToolChain by ch33kybutt..I:read: ui_print

# md5sum RoDrIgUeZsTyLe_MIUIMOD_v3.5_MULTI_D2SD_NEXUS_ONE.zip
4c4eba283e6531424d69f3f1dece87bf RoDrIgUeZsTyLe_MIUIMOD_v3.5_MULTI_D2SD_NEXUS_ONE.zip

Also, does anyone know how much bad NAND memory is to be expected? Because I know these devices basically ship with bad blocks on the internal memory. I see about two dozen that I have marked as bad. NAND, not sd card!

Is that an unusually large amount, indicating imminent device failure? My understanding is that it is typically a slow and progressive process of internal memory failure (overheating, etc.), not parallel to the screeching platter syndrome in our laptops/desktops.

Also, could someone tell me what active process, when we are ROMing, marks NAND blocks as BAD?