MobileRead Forums - View Single Post - "Scan and fix the device" after removing a book with Calibre

jackie_w · 01-29-2022, 07:52 PM

I've been getting the Windows "scan & fix" error with some of my Kobos for a few years. For me it has always been device-dependent.

Glo, AuraHD, Aurav1, AuraH2O, GloHD, AuraOne have never had it in all the years I've owned them.

ClaraHD, Forma, Libra2 (i.e. the 3 newest devices) have all had it from day one. It's intermittent and doesn't seem to be related to a particular cable or a particular PC USB port. Nor does it only happen when using calibre, it can happen whether calibre is open or not.

Just FYI ... @NiLuJe did find a fix many firmwares ago. It involved replacing a small system file (bin/dosfsck) with a newer version than Kobo were using. It worked well (for me) at first but, unfortunately, stopped working (for me) a few firmwares later.

I would like it to be fixed permanently but I try not to worry about it anymore. No errors have ever been found during the fix and my Kobo database has never been corrupted when it happens.

01-29-2022, 07:52 PM	#8
jackie_w Grand Sorcerer Posts: 6,252 Karma: 16544692 Join Date: Sep 2009 Location: UK Device: ClaraHD, Forma, Libra2, Clara2E, LibraCol, PBTouchHD3	I've been getting the Windows "scan & fix" error with some of my Kobos for a few years. For me it has always been device-dependent. Glo, AuraHD, Aurav1, AuraH2O, GloHD, AuraOne have never had it in all the years I've owned them. ClaraHD, Forma, Libra2 (i.e. the 3 newest devices) have all had it from day one. It's intermittent and doesn't seem to be related to a particular cable or a particular PC USB port. Nor does it only happen when using calibre, it can happen whether calibre is open or not. Just FYI ... @NiLuJe did find a fix many firmwares ago. It involved replacing a small system file (bin/dosfsck) with a newer version than Kobo were using. It worked well (for me) at first but, unfortunately, stopped working (for me) a few firmwares later. I would like it to be fixed permanently but I try not to worry about it anymore. No errors have ever been found during the fix and my Kobo database has never been corrupted when it happens. Last edited by jackie_w; 01-29-2022 at 07:55 PM.