Quote:
Originally Posted by NullNix
For more than an hour? What's it *doing* in there? Even resquashing an entire filesystem shouldn't take that long, and fsck is drastically faster even on spinning rust.
|
Correcting the source of the error message you received.
Of course fsck is drastically faster on spinning rust, spinning rust is drastically faster than flash rom.
Keep in mind two things:
*) Flash storage (eeprom) can not be written to.
It can be read, it can be erased and it can be re-programmed, but write? Can't happen, the device's micro-controller is faking it.
*) Each time an error, either in the data recorded (in this case a file system) or in the underlying storage media, is encountered - -
**After** the device corrects itself internally, the whole fsck process has to be started again.
Let me guess your next question:
The reason you don't see this situation with the SSD in your (whatever) other device is because it is hidden by the controller inside of the device.
The micro-controller in an SSD is much more "intelligent" than that of an eMMC device.
Your attempts to re-start it and/or re-set it during the time it was initially dealing with the problem only made things worse, much worse.
But still, it would have recovered if kept on external power and left alone.
And yes, a day or two is reasonable for a 2G or 4G device.
And it **must** be on external power all of that time (the battery run-time of a Kindle is only 2 to 3 hours - not days).
Lose power to the eMMC device during one of its internal read-erase-merge-reprogram cycles and the device is ruined.