View Single Post
Posts: 842 | Thanked: 1,197 times | Joined on May 2010
#52
Hm... I'd probably better add a way to copy the fsckstatus file to your eMMC in case you want to look at it... I assume it's working -correctly-, but I don't know what the output means from your description.

Also, as I said before, you do have bad blocks. It's inevitable. The -filesystem- marks them as bad; this means that if you re-flash, the new FS has to re-mark them. Also, copying a file to it will - at the FS level - automatically mark all bad blocks as bad and work around them. Thus, you won't see any problems(aside from a momentary "pause" as it re-writes the content to a different block).

However, as I've been trying to tell you, if you use the old 0.3x version BAD BLOCKS ARE INCLUDED IN YOUR BACKUP! They then get written over the current filesystem, IGNORING ANY (new) BAD BLOCKS IT FINDS.

If you want more information, go talk to Stskeeps on the IRC. He knows a lot about the raw nand flash and can explain it to you.

Solution: USE THIS VERSION OF BACKUPMENU. Not the one available in the repositories.
 

The Following User Says Thank You to RobbieThe1st For This Useful Post: