Quote:
Originally Posted by ixtab
Nope, it doesn't (yet? ;-) ).
- - - -
It might be time to implement the feature to completely blast the USB storage into Kubrick, too.
|
We recently had someone try to fix a seriously damaged USB storage area by re-formating it in Windows.
Which really didn't do much of anything good to the Kindle's FAT layout.
Plus - that one layer of the stacked "export" is mounted errors=remount-ro
(or, whatever the correct form of that option is)
Probably one source of the "I can't make lasting changes to USB storage" problem reports.
Hmm...
I guess switching the device to diags mode, stopping the fuse export stack if running, un-mounting both layers of the stack, re-formatting mmcblk0p4 with the Kindle specific layout, then putting everything back together is the only answer.
OR
Just zero the first 16 blocks of mmcblk0p4 and force the Kindle to re-boot and fix it, itself.
BUT - we learned last week that the "custom kernel" for the Kindles does not detect/perform the re-build like a stock kernel does.
(All done by the initramfs, which might be what fixed this one, during the re-boot.)
ADD TO:
Summer of Kode Challenge list.