MobileRead Forums - View Single Post

Shadowjack · 12-27-2017, 12:20 AM

- I tried different cables (including the one sent with my H2O2). No difference.
- I have been using a USB 3 port (same one I used for my old H2O). I tried a USB 2 port just now and everything worked.
- I was able to use windows to copy files (I side loaded custom fonts).
- I do have a laptop with Windows 10 but Calibre is not loaded on it. However, I did try connecting the device to the laptop and didn't have any issues.
- I didn't always check the error log in calibre, but when it occurred it was always with the same job after connection.
- I did restart the PC and device after the error happened.
- I did not try the sign out/in rather than the reset. Didn't think of that. It seemed like the root problem was with the USB mount, not the database.
- The Kobo utility shows the database as uncorrupted. Result of running 'PRAGMA integrity_check' on database on the Kobo device: ok

After some of the times the calibre error occurred, Windows would automatically remount the drive and then complain that it detected an issue and need to scan the drive and try to repair any errors. I would allow it to scan, but it never found anything to fix. I assumed this was Windows being complaining about how the drive was disconnected and flagging the drive to be scanned the next time it detected it. Whenever this happened, Calibre did not recognize the remounted drive. I would have to restart Calibre to restart the beginning jobs. However, this never worked. A reboot of the PC was always necessary after the error occurred.

Well, I do not understand why moving to the USB 2 port worked this time. I know I loaded my complete library of books via the USB 3 port and Calibre on Saturday. But that was after at least 4 or 5 factory resets. I thought I had traced the problem down to patching the firmware to 4.6.9995 (which is what I was running on my old H2O). It seemed to be stable running at 4.4.9298 until today. I must have done a factory reset 5 or 6 times over several days trying to reach a stable position.

12-27-2017, 12:20 AM	#3
Shadowjack Enthusiast Posts: 44 Karma: 10 Join Date: Apr 2009 Location: Champaign, IL Device: Sony PRS-500, PRS-505, PRS-650, Kobo H2O, H2Ov2, Libra H2O	- I tried different cables (including the one sent with my H2O2). No difference. - I have been using a USB 3 port (same one I used for my old H2O). I tried a USB 2 port just now and everything worked. - I was able to use windows to copy files (I side loaded custom fonts). - I do have a laptop with Windows 10 but Calibre is not loaded on it. However, I did try connecting the device to the laptop and didn't have any issues. - I didn't always check the error log in calibre, but when it occurred it was always with the same job after connection. - I did restart the PC and device after the error happened. - I did not try the sign out/in rather than the reset. Didn't think of that. It seemed like the root problem was with the USB mount, not the database. - The Kobo utility shows the database as uncorrupted. Result of running 'PRAGMA integrity_check' on database on the Kobo device: ok After some of the times the calibre error occurred, Windows would automatically remount the drive and then complain that it detected an issue and need to scan the drive and try to repair any errors. I would allow it to scan, but it never found anything to fix. I assumed this was Windows being complaining about how the drive was disconnected and flagging the drive to be scanned the next time it detected it. Whenever this happened, Calibre did not recognize the remounted drive. I would have to restart Calibre to restart the beginning jobs. However, this never worked. A reboot of the PC was always necessary after the error occurred. Well, I do not understand why moving to the USB 2 port worked this time. I know I loaded my complete library of books via the USB 3 port and Calibre on Saturday. But that was after at least 4 or 5 factory resets. I thought I had traced the problem down to patching the firmware to 4.6.9995 (which is what I was running on my old H2O). It seemed to be stable running at 4.4.9298 until today. I must have done a factory reset 5 or 6 times over several days trying to reach a stable position.