View Single Post
Old 08-07-2016, 08:52 AM   #98
frostschutz
Linux User
frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.frostschutz ought to be getting tired of karma fortunes by now.
 
frostschutz's Avatar
 
Posts: 2,282
Karma: 6123806
Join Date: Sep 2010
Location: Heidelberg, Germany
Device: none
Quote:
Originally Posted by Dave R View Post
I followed the instructions to format my H2O on Windows 10 using FAT32. That worked. Windows could see the KOBO drive and I copied back the folders that were there originally.
However on ejecting the Kobo it was stuck showing the "Connected" screen. I gave it several minutes with no change so switched it off. Now it will not boot at all - just a blank screen with the on light flashing.
There are several possibilities why formatting might go wrong...

1) it was formatted incorrectly. It must be FAT32, directly without partition table. I do not know how Windows decides whether to create a partition table or not; most USB Sticks have a partition table (single partition), but Kobo does not have one.

2) Kobo itself didn't manage to umount the FAT32 before exporting the USB device. This happens for example when you are running mods that block the FAT32 from being umounted, or when connecting USB from within a KEPUB [in this case the umount happens only after some delay]. In this case it results in filesystem corruption which might cause the device to crash, or to be stuck for a long time attempting to run a filesystem recovery.

3) Device was not ejected/umounted properly before pulling the USB cable. At best this causes some missing file, worst it will kick the Kobo into factory reset mode.

Some time ago I had posted a small mod that displays a smiley :-) face if the user partition was umounted correctly, and a :-( face if it was not. Kobo itself does not check at all whether umount worked - it does a lazy umount which just doesn't do anything while the device is still in use.
frostschutz is offline   Reply With Quote