View Single Post
Old 09-01-2020, 10:35 PM   #15
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Cdesja5 View Post
No go when I tried to add 1000 books at a time to my Glo HD - I therefore removed the Kobo add-ons and then added them back again. It seems the problem is (according to the job list) getting the list of books on device - that always ends in an error.
IOError: disk I/O error

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 90, in run
File "site-packages\calibre\gui2\device.py", line 513, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1964, in books
File "c:\t\t\apsw-w7591s5i\src\cursor.c", line 236, in resetcursor
IOError: IOError: disk I/O error
That error is usually a sign that the database on the device is corrupt. It can sometime be fixed by restarting the device. But, usually you need to replace the database on the device either with a backup, or by signing out of the Kobo account on the device and back in again. The latter creates a new database and imports the sideloaded books again.
Quote:
I have since (without re-starting Calibre) just tried 399 books and got an error. So for the book transfer, it seems the problem is a corrupted file (which I have removed). I can't figure out what the issue getting the kobo's book list into Calibre is though.
What was the error that said the book was corrupt? Unless you are using the KoboTouchExtended driver, calibre isn't doing anything that should trigger an error like this. Or are you saying the error happened on the device when it tried to import the book/
Quote:
ADDITIONAL INFO: I removed the file that was corrupted according to the error message and got the same message with the next file in the list when I tried again... My Glo is now only good for 300 or so books - so disappointed - it's been used very sporadically and with kid gloves and now seems "broken" because of this update.

[Error 1392] The file or directory is corrupted and unreadable: u'E:\\Holiday, Jenny'

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 90, in run
File "site-packages\calibre\gui2\device.py", line 594, in _upload_books
File "calibre_plugins.kobotouch_extended.device.driver" , line 403, in upload_books
File "site-packages\calibre\devices\kobo\driver.py", line 2132, in upload_books
File "site-packages\calibre\devices\usbms\driver.py", line 324, in upload_books
File "site-packages\calibre\devices\usbms\device.py", line 998, in create_upload_path
File "os.py", line 157, in makedirs
WindowsError: [Error 1392] The file or directory is corrupted and unreadable: u'E:\\Holiday, Jenny'
That to me says the internal SD card is failing. It might be that the filesystem for the book partition on the device is badly corrupted. Either of these could also be the cause of the first error.

The firmware update is probably a coincidence. One of the things that happen is that the device is rebooted. If you don't do that very often, any issues with the database will come up at this point.

You could try a factory reset. This will format the book partition and take you through the setup. If it is just a problem with file system, it will be fixed. If it is a problem with the card, it might temporarily fix it, but will probably happen again.
davidfor is offline   Reply With Quote