View Single Post
Old 06-02-2020, 05:55 PM   #13
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
@jackie_w: I suppose the brute-force approach of replacing /bin/dosfsck with an up to date build (careful: not the same filename, fix it) would at least fix it on reboot until the next FW update.

(Fair warning: if I screwed up, this will break the boot horribly. Hopefully leading to an instant factory reset on boot. Emphasis on *hopefully* ^^. I did try a dry-run manually with no ill effects, and the commandline arguments haven't changed, so, it *should* behave. But, here be angry potentially disk-eating dragons).

I'm vaguely hoping Nickel itself runs a fsck before remounting onboard after an USBMS session (which would fix it *always*), but that may be wishful thinking .

EDIT: The udev script run on unplug would seem to concur with that theory, yay.

----

And, yeah, only ever happens on the Forma on my end, too.

Last edited by NiLuJe; 06-02-2020 at 06:01 PM.
NiLuJe is offline   Reply With Quote