View Single Post
Old 05-27-2019, 05:25 PM   #2
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
My best guess would be Windows's moronic response to a FAT filesystem with the dirty bit set, which for mysterious and probably fairly stupid reasons can happen on the Kobo userstore even when you haven't done anything wrong.

I won't vouch for Windows's fsck not doing anything even stupider with that, so I'd go with "ignore".

The Kobo itself will do a round of checks at boot time, so you can see if a cold reboot "fixes" it.

I'd still check that it's not an actual issue by verifying the integrity of the USB cable/plug being used, and trying on another machine.

Last edited by NiLuJe; 05-27-2019 at 05:30 PM.
NiLuJe is offline   Reply With Quote