View Single Post
ndi's Avatar
Posts: 2,050 | Thanked: 1,425 times | Joined on Dec 2009 @ Bucharest
#53
Originally Posted by RobbieThe1st View Post
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.
I'll test.

Originally Posted by RobbieThe1st View Post
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.
So reflashing doesn't do anything for bad blocks? I'm thinking the controller for the NAND should, after all, if the block is under the system image it's bricked. I'll take your advice and bother Stskeeps.

Anyway, after further investigation is seems I may have the cause of the errors. I don't want to throw stones just yet, I want to do several tests before I make a firm affirmation, but it seems it wasn't bad blocks that were the root of my problem, but a file system problem.

Originally Posted by RobbieThe1st View Post
Solution: USE THIS VERSION OF BACKUPMENU. Not the one available in the repositories.
I am. And, I have made a backup and restored it successfully. Additionally, I have again triggered the error in my phone and BackupMenu v43 has successfully repaired the problem.

I am doing almost hourly backups as I diagnose the issue, so I'm giving the script a thorough check.
__________________
N900 dead and Nokia no longer replaces them. Thanks for all the fish.

Keep the forums clean: use "Thanks" button instead of the thank you post.
 

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