That's the whole point - there -is- no controller. This is what screwed me up with my previous version - I'm used to SD cards and HDs where you can go ahead and copy the entire partition or disk using dd, and everything works fine. In this case, I learn(way after the fact) that the OneNAND used on the N900(part of the CPU/SoC, btw) has no controller, and as such requires a special filesystem to handle it - This is the reason for Jffs2 and Ubifs.
When you write an image, it has to be a special "ubinized" version of the UbiFS. I'm betting that between that and the flasher utility, it works around bad-blocks, at least on the first write.
This would explain why, for some people, BackupMenu v.3x rootfs images would flash via the flasher, but not work if written back via dd.


Huh - Not sure how that'd work. My system's supposed to copy each file using "tar -cfp destination.tar /inputfolder" - There's only two "active" lines in the entire backup section!
I'd check that you don't have a missing or "corrupt" file in your input - When I used my own old version, I ended up with a couple of corrupt files, which weren't able to be read when backing it up with the new version, so they were missing in all subsequent backups. Fortunately, in my case, they were unused files(other languages).

Ah, good. I was worried about you using the old version because you were talking about checksums, which aren't used in the new version.

Also(just curious), did you restore your rootfs via BackupMenu, or did you make an image and flash it?

And, of course, feel free to edit/fix it - It's GPL after all. I would like to see any changes you think would improve it, however - I'd like some outside additions.