The operation of downloading a FID should erase that data; if the bug is still there in 2.0-final, rereport it.

You know, now that you mention it, I never checked that in 2.0 final. I just remember that it was there in some of the 2.0 betas and I didn't see it specifically noted as "fixed" in any of the release notes. On reflection, you're right: just because it wasn't specifically reported as fixed doesn't mean it wasn't fixed. So I should verify that it's even a problem at all before I panic. Maybe I don't have to do anything.

dd if=/dev/zero bs=512 skip=4096 count=28672 /dev/hda3

Cool. I'm going to put that in the FAQ. Is there anything special that needs to precede the command, such as mounting the drives read-write?