Quote:
Originally Posted by stack
Is it worth trying to format the fat partition in a last ditch attempt to get the original firmware loaded? I was thinking of trying it before but didn't want to stray off-script in case the recovery does more than it says it will.
|
I think it better to be sure we can't "fix" it from the Diags system before trying that.
Both "Main" and "Diags" need what looks like an error free /var/local (partition 3) and /mnt/us (partition 4) to complete the boot process.
Otherwise the start-up code will try to re-format them.
Currently, it is NOT trying to re-format either of them, so they must be 'good enough' to pass the simple tests to continue the boot.
Not necessarily 'good enough' to work, just 'good enough' to pass POST.
When the system re-partitions partition 4 (it is a partition within a partition system) to account for the reduced size (from mapping out more eraseblocks than the device has spare eraseblocks) and then re-formatting the re-sized partition we could very well end up with a partition within partition 4 that does not past POST.
I.E: Inadvertently making both 'Main' and 'Diags' fail to boot.
In which case you can proceed directly to the thread on how to replace the eMMC with a brand-new (bigger) one.
Oops.
Internally the eMMC only supports:
Erase, Re-program, and Read (in eraseblock size, 4Kbyte, chunks).
Meaning that when one is mapped out, you lose 8 "sectors" from the file system.
It is pretty easy to destroy FAT-32 (or any format) taking out 8 adjacent "sectors" at a time.
So let's try booting the other operating system first and make sure there isn't anything there that could help this situation.
Perhaps Lab126 has an eMMC maintenance utility included there.