Quote:
Originally Posted by knc1
Usually, the indexer gets the blame and historically, deserves it.
But the above added descriptive information tells me that you just had (hardware based) file system errors, and the Kindle was trying to recover the failing backing store (eMMC).
The Kindle's start-up (POST ? on a device that never powers off?) process checks for file system errors and will reformat a bad file system (hence the missing content).
When the file system errors are hardware failures, the failing hardware blocks have to be taken out of service (put on an internal, hardware, "bad block list").
Which causes the whole reformat and test sequence to restart (as it should, it must).
And the Kindles use a rather slow eMMC chip, not an SSD - - so depending on the damage, this sequence could take a few days.
34 hours is a short period for such a self recovery.
- - - - -
Hint: Start saving for a new Kindle now -
this one will not be around in usable shape much longer.
|
Thank you for the detailed explanation
.
The only reason I have not yet upgraded is because the latest firmware (and devices) feature features that I do not use, and seem not to support the USE_ALT_FONTS workaround.