Aura H2O error in calibre

Shadowjack · 12-26-2017, 05:59 PM

Not sure if this belongs here or in the calibre forum. I am having problems with calibre generating an error when connecting to my H2O edition 2. This doesn't happen all of the time, but once it starts happening it seems to keep happening until I do a factory reset on my device. I finally was able to get my entire library loaded on the H2O but the error started again today. Before I go back to zero, I thought I would see if there is another solution. I also worry that I may need to work with Kobo to return/replace it.

The error I am getting is during the job "Get list of books on device".
ERROR: Error: Error communicating with device

IOError: disk I/O error

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 87, in run
File "site-packages\calibre\gui2\device.py", line 510, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1859, in books
File "c:\t\t\apsw-9hooel\apsw-3.13.0-r1\src\cursor.c", line 236, in resetcursor
IOError: IOError: disk I/O error

There is also a corresponding USB error that causes the USB drive to disappear. However, this action doesn't happen until after the error above.

Cablibre version: 3.14 and using the latest Kobo utilities.
Kobo firmware version: 4.4.9298 (factory default). I have tried upgrading the firmware to 4.6.9995 (side-loaded) with the same results. I have not upgraded to the latest firmware 4.7.10413, due to the reported problem with statistics. My PC is running Windows 7.

Would appreciate any advice.

davidfor · 12-26-2017, 08:23 PM

That error usually means that the database on the device is corrupt. But, if there is a USB error at the same time, it probably means something else is going on. At the point where the error is happening, calibre is trying to read the database. It sounds like there is a problem with the connection to the device and when the calibre starts accessing the database, the connection fails.

There are a few things to try:
- Different USB cables - a faulty cable can cause weird problems.
- Different USB port - If this is a USB 3 port, try a USB2 port.
- Can you successfully use Windows to copy files to and from the device?
- Is there another PC you can try with?
- Is it always the same error? Or do you get that error and a different one later? I'm wondering if the last line has a different description or the line number in "driver.py" is different.
- Are you restarting the PC and device after the error happens?
- Have you tried signing out of the Kobo account rather than a factory reset? This will rebuild the database on the device without needing to resend the books.

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.

davidfor · 12-27-2017, 03:00 AM

Changing to the USB2 port is probably the solution. Using USB3 seems to be a problem with the newer Kobo devices. It isn't everyone, and it isn't all the time. But, changing to the USB2 port seems to fix it every time. Or changing to a hub.

How much is the Kobo devices, and how much is the PC or drivers, I don't know. My laptop only has USB3 ports, and I've never had this problem with my Aura ONE.

I do have problem, but it is caused by having loose USB ports on the laptop and the position of the ports. They are in a place where I can bump them partly out. If calibre is processing the device, I'll get an error, but, I don't think it was the one you are seeing. And when this happens, the device is ejected without closing the file system, and it also seems to put the port into strange state. Afterwards, the Kobo devices won't work with the port, and some other devices won't as well. A simple USB memory stick will, but I don't trust it. Other ports are OK. I have to reboot the laptop to get the port working properly again. That sounds like one of the things you are seeing.

J_K · 12-27-2017, 04:08 AM

This happened to me yesterday on my new H2o Edition 2 using Calibre on Windows 10. H2o 2 is on the latest firmware.

I normally don't use Calibre so it was the first time I had ever tried using it with the H2o 2 (I was trying to fix this). I tried a couple of times and Calibre hung, and when I checked the jobs it was unable to get the list of books. It was also not possible to cancel this. It would give an error if you left it long enough, though I did force close Calibre when it first happened.

I had loads of trouble with explorer.exe afterwards when trying to eject the H2o 2. It was hanging and eventually I had to use Task Manager to try and close explorer.exe and start a new process.

Windows showed the 'problem with drive' error when the H2o 2 was next connected so I did a factory reset and thought I'd try Calibre again. Same thing happened. It was unable to read the list of books and Windows started giving the 'problem with drive' error.

When I next got the 'problem with drive' error, I let Windows scan and it said it found an error, but I thought safer to do a second factory reset than let Windows fix.

So I will not be attempting to use Calibre again with the H2o 2 (my old Touch works fine with Calibre). I am able to use Windows to edit the files on the H2o 2 (have done the full screen reading fix) so it seems to me that Calibre is the problem.

Shadowjack · 01-02-2018, 12:42 PM

Switching to the USB2 has solved my issues. However, transfers within Calibre take much longer. I have a library of about 800 books, but it took 6.5 minutes run the job, "Get list of books on device" and 29 minutes to "Backing up Kobo device database". Is it safe to assume this is solely due to use of USB2?

thanks.

Shadowjack · 01-02-2018, 12:48 PM

Huh. A subsequent connection (to update series info on books I uploaded in the previous connection) only took about 1 minute for each of those jobs.

PeterT · 01-02-2018, 12:51 PM

Quote:

Originally Posted by Shadowjack

Switching to the USB2 has solved my issues. However, transfers within Calibre take much longer. I have a library of about 800 books, but it took 6.5 minutes run the job, "Get list of books on device" and 29 minutes to "Backing up Kobo device database". Is it safe to assume this is solely due to use of USB2?

thanks.

Seeing the Kobo only implements USB 2 I'm not sure why you think using a USB 3 port would offer any advantage.

I know that at times I've seen very slow connections / transfers but then the next time all is back to normal

Sent from my Nexus 7 using Tapatalk

DNSB · 01-02-2018, 12:53 PM

Quote:

Originally Posted by Shadowjack

Switching to the USB2 has solved my issues. However, transfers within Calibre take much longer. I have a library of about 800 books, but it took 6.5 minutes run the job, "Get list of books on device" and 29 minutes to "Backing up Kobo device database". Is it safe to assume this is solely due to use of USB2?

thanks.

You shouldn't see any speed difference. The USB port on your Kobo is USB2 so no speed advantage to connecting to a USB3 port. Personally, I've been using a USB2 powered hub connected to my laptop's USB3 port and haven't seen the weird disconnects with that configuration.

kingzaphod · 03-27-2018, 04:40 PM

Similar messages to those that have gone before: my last IOError message
Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 87, in run
File "site-packages\calibre\gui2\device.py", line 510, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1761, in books
File "site-packages\calibre\devices\kobo\driver.py", line 161, in device_database_connection
IOError: IOError: disk I/O error

I've been in IT quite a while and normally figure out stuff like this but after spending hours and hours on this trying many permutations - I'm just having to grumpily give up and manage by transferring epub files using windows explorer - disappointed as in all other aspects I believe the Kobo Aura H2o Ed2 is a much better option for those who want the flexibility and capacity.

FYI I've got W10 on an HP Pavillion laptop - I have the latest Kobo firmware 4.7.10413 and Caliber 3.19.0. I've tried USB 2 and USB 3 ports, factory-resetting the Kobo, re-powering Kobo and laptop, with and without the Kobo extended Touch and utility plugins, I'm always seeing the same issue - once I've connected to Caliber after initialising everything and done something such as transferring ebooks ; the next connect I always get an IO error despite a reboot of laptop and Kobo - the first sync between Caliber and the Kobo cannot finish - it seems arbitrary. (FYI I've also tried using the device detection utility in Caliber and entered to USB parameters into the User defined USP port device plugin).

If you have any ideas I'd be REALLY HAPPY to hear from you thanks ....! My suspicion is that its a bug in Caliber or an HP USB driver issue- I'm more inclined to think it's a Caliber derived issue but at Wits end trying to solve this....!! If you read this many Thanks.....

davidfor · 03-28-2018, 02:16 AM

Quote:

Originally Posted by kingzaphod

Similar messages to those that have gone before: my last IOError message
Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 87, in run
File "site-packages\calibre\gui2\device.py", line 510, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1761, in books
File "site-packages\calibre\devices\kobo\driver.py", line 161, in device_database_connection
IOError: IOError: disk I/O error

I've been in IT quite a while and normally figure out stuff like this but after spending hours and hours on this trying many permutations - I'm just having to grumpily give up and manage by transferring epub files using windows explorer - disappointed as in all other aspects I believe the Kobo Aura H2o Ed2 is a much better option for those who want the flexibility and capacity.

FYI I've got W10 on an HP Pavillion laptop - I have the latest Kobo firmware 4.7.10413 and Caliber 3.19.0. I've tried USB 2 and USB 3 ports, factory-resetting the Kobo, re-powering Kobo and laptop, with and without the Kobo extended Touch and utility plugins, I'm always seeing the same issue - once I've connected to Caliber after initialising everything and done something such as transferring ebooks ; the next connect I always get an IO error despite a reboot of laptop and Kobo - the first sync between Caliber and the Kobo cannot finish - it seems arbitrary.

That all sounds like problems that have been reported and the suggestions in the thread above were the ways to solve or workaround it. But, it not being solved by restarting the PC and device between is a little different.

Do you have another PC you can test on? And if it works there, can you connect to the HP, and then connect to the other PC. If the above error happens, then it is something on the HP corrupting the disk or database before or during the eject.

Or reconnect to HP and use an SQLite management tool to check the database. And when the above happens, can you still see the device in Windows and use it?

Quote:

(FYI I've also tried using the device detection utility in Caliber and entered to USB parameters into the User defined USP port device plugin).

The way you state that makes me think it didn't work. Is that right? With the User Defined driver, it doesn't access the database on the device, so there shouldn't have been an error like this. The driver will scan the drive looking for books. If you did get the above error, then you need to disable the KoboTouch driver and try again.

Quote:

If you have any ideas I'd be REALLY HAPPY to hear from you thanks ....! My suspicion is that its a bug in Caliber or an HP USB driver issue- I'm more inclined to think it's a Caliber derived issue but at Wits end trying to solve this....!! If you read this many Thanks.....

And I tend to think it isn't a calibre bug. It might be a "calibre derived" issue as when you connect the Kobo device, it does a lot of work reading the database and otherwise accessing the drive. If there is something flaky in that connection, this is more likely to show that flakiness than simply copying a few files to the drive.

kingzaphod · 03-28-2018, 12:54 PM

Thank You for the reply so quickly - you are a Gent..!

Quote:
The way you state that makes me think it didn't work. Is that right? With the User Defined driver, it doesn't access the database on the device, so there shouldn't have been an error like this. The driver will scan the drive looking for books. If you did get the above error, then you need to disable the KoboTouch driver and try again.

Well, interesting as I thought I had removed the Kobotouch Extended plugin and then connected with the User defined driver (and go that error message) - so I coudn't have disabled the kobo driver driver properly as the database connected in some manner - please excuse my ignorance as I am not sure why this has happened.
Incidentally once I get this error message the laptop's USB port becomes unusable for anything and I have to re-initialise it with a laptop reboot

I do have an old Lenovo laptop so will do some testing with that as soon as I have time next week (that is to be the next step to be honest if nothing obvious transpires from this conversation).

I will also install a SQLLite management tool to check the database - I like your idea the HP is corrupting the database.....Best I do some more testing and will add back to this thread, really appreciate the time you took to answer - Thanks.

kingzaphod · 04-02-2018, 10:04 AM

Hi David - as you suspected the issue is with my laptop, even though the issue happened using a USB 2 connection (as well as USB 3)

My old Lenovo laptop worked fine using a USB 2 port so I was able to to use the extended Kobo driver and Kobo Utiilties which are so useful, so many thanks.

PS - I'm going to get a USB hub with a USB 2 port try that with the HP.

Kind Regards
Mike

JeanPierre · 12-22-2018, 03:07 AM

Quote:

Originally Posted by kingzaphod

Incidentally once I get this error message the laptop's USB port becomes unusable for anything and I have to re-initialise it with a laptop reboot

I am seeing exactly the same symptoms with my Macbook Pro. In my case the error looks a little different, like below:

calibre, version 3.36.0
ERROR: Error: Error communicating with device

IOError: disk I/O error

Traceback (most recent call last):
File "site-packages/calibre/gui2/device.py", line 87, in run
File "site-packages/calibre/gui2/device.py", line 540, in _sync_booklists
File "calibre_plugins.kobotouch_extended.device.driver" , line 447, in sync_booklists
File "calibre_plugins.kobotouch_extended.device.driver" , line 442, in __rows_needing_imageid
File "src/cursor.c", line 236, in resetcursor
IOError: IOError: disk I/O error

Stevex · 12-22-2018, 05:50 AM

Those kind of things can sometimes be caused by voltage errors on the usb ports

12-26-2017, 05:59 PM	#1
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	error in calibre Not sure if this belongs here or in the calibre forum. I am having problems with calibre generating an error when connecting to my H2O edition 2. This doesn't happen all of the time, but once it starts happening it seems to keep happening until I do a factory reset on my device. I finally was able to get my entire library loaded on the H2O but the error started again today. Before I go back to zero, I thought I would see if there is another solution. I also worry that I may need to work with Kobo to return/replace it. The error I am getting is during the job "Get list of books on device". ERROR: Error: Error communicating with device IOError: disk I/O error Traceback (most recent call last): File "site-packages\calibre\gui2\device.py", line 87, in run File "site-packages\calibre\gui2\device.py", line 510, in _books File "site-packages\calibre\devices\kobo\driver.py", line 1859, in books File "c:\t\t\apsw-9hooel\apsw-3.13.0-r1\src\cursor.c", line 236, in resetcursor IOError: IOError: disk I/O error There is also a corresponding USB error that causes the USB drive to disappear. However, this action doesn't happen until after the error above. Cablibre version: 3.14 and using the latest Kobo utilities. Kobo firmware version: 4.4.9298 (factory default). I have tried upgrading the firmware to 4.6.9995 (side-loaded) with the same results. I have not upgraded to the latest firmware 4.7.10413, due to the reported problem with statistics. My PC is running Windows 7. Would appreciate any advice.

03-27-2018, 04:40 PM	#10
kingzaphod Junior Member Posts: 5 Karma: 10 Join Date: Mar 2018 Device: Kobo Aura H2o	Totally Flummoxed - No USB 2 fairytale ending here! Similar messages to those that have gone before: my last IOError message Traceback (most recent call last): File "site-packages\calibre\gui2\device.py", line 87, in run File "site-packages\calibre\gui2\device.py", line 510, in _books File "site-packages\calibre\devices\kobo\driver.py", line 1761, in books File "site-packages\calibre\devices\kobo\driver.py", line 161, in device_database_connection IOError: IOError: disk I/O error I've been in IT quite a while and normally figure out stuff like this but after spending hours and hours on this trying many permutations - I'm just having to grumpily give up and manage by transferring epub files using windows explorer - disappointed as in all other aspects I believe the Kobo Aura H2o Ed2 is a much better option for those who want the flexibility and capacity. FYI I've got W10 on an HP Pavillion laptop - I have the latest Kobo firmware 4.7.10413 and Caliber 3.19.0. I've tried USB 2 and USB 3 ports, factory-resetting the Kobo, re-powering Kobo and laptop, with and without the Kobo extended Touch and utility plugins, I'm always seeing the same issue - once I've connected to Caliber after initialising everything and done something such as transferring ebooks ; the next connect I always get an IO error despite a reboot of laptop and Kobo - the first sync between Caliber and the Kobo cannot finish - it seems arbitrary. (FYI I've also tried using the device detection utility in Caliber and entered to USB parameters into the User defined USP port device plugin). If you have any ideas I'd be REALLY HAPPY to hear from you thanks ....! My suspicion is that its a bug in Caliber or an HP USB driver issue- I'm more inclined to think it's a Caliber derived issue but at Wits end trying to solve this....!! If you read this many Thanks.....

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
calibre corrupt error corrupt error database disk image is malformed	didu812	Calibre	50	04-10-2024 08:51 AM
Calibre Hudl 2: calibre, version 3.2.1 ERROR: Error: Error communicating with device	elfed	Devices	4	07-21-2017 05:33 AM
Error Message with Calibre & Calibre Companion	wildoatz	Devices	2	09-28-2015 03:31 AM
Calibre plugIn Kindle Collections Error message "Value Error:month..."	readee	Plugins	4	10-10-2011 11:21 AM
calibre, version 0.8.8 ERROR: Error: Error communicating with device no such column:	e-bookuser	Devices	1	07-03-2011 04:09 PM

12-26-2017, 08:23 PM	#2
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	That error usually means that the database on the device is corrupt. But, if there is a USB error at the same time, it probably means something else is going on. At the point where the error is happening, calibre is trying to read the database. It sounds like there is a problem with the connection to the device and when the calibre starts accessing the database, the connection fails. There are a few things to try: - Different USB cables - a faulty cable can cause weird problems. - Different USB port - If this is a USB 3 port, try a USB2 port. - Can you successfully use Windows to copy files to and from the device? - Is there another PC you can try with? - Is it always the same error? Or do you get that error and a different one later? I'm wondering if the last line has a different description or the line number in "driver.py" is different. - Are you restarting the PC and device after the error happens? - Have you tried signing out of the Kobo account rather than a factory reset? This will rebuild the database on the device without needing to resend the books.

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.

12-27-2017, 03:00 AM	#4
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Changing to the USB2 port is probably the solution. Using USB3 seems to be a problem with the newer Kobo devices. It isn't everyone, and it isn't all the time. But, changing to the USB2 port seems to fix it every time. Or changing to a hub. How much is the Kobo devices, and how much is the PC or drivers, I don't know. My laptop only has USB3 ports, and I've never had this problem with my Aura ONE. I do have problem, but it is caused by having loose USB ports on the laptop and the position of the ports. They are in a place where I can bump them partly out. If calibre is processing the device, I'll get an error, but, I don't think it was the one you are seeing. And when this happens, the device is ejected without closing the file system, and it also seems to put the port into strange state. Afterwards, the Kobo devices won't work with the port, and some other devices won't as well. A simple USB memory stick will, but I don't trust it. Other ports are OK. I have to reboot the laptop to get the port working properly again. That sounds like one of the things you are seeing.

12-27-2017, 04:08 AM	#5
J_K Enthusiast Posts: 47 Karma: 26706 Join Date: Jan 2014 Location: London, UK Device: H2O 2, Aura 2, Clara HD, Touch	This happened to me yesterday on my new H2o Edition 2 using Calibre on Windows 10. H2o 2 is on the latest firmware. I normally don't use Calibre so it was the first time I had ever tried using it with the H2o 2 (I was trying to fix this). I tried a couple of times and Calibre hung, and when I checked the jobs it was unable to get the list of books. It was also not possible to cancel this. It would give an error if you left it long enough, though I did force close Calibre when it first happened. I had loads of trouble with explorer.exe afterwards when trying to eject the H2o 2. It was hanging and eventually I had to use Task Manager to try and close explorer.exe and start a new process. Windows showed the 'problem with drive' error when the H2o 2 was next connected so I did a factory reset and thought I'd try Calibre again. Same thing happened. It was unable to read the list of books and Windows started giving the 'problem with drive' error. When I next got the 'problem with drive' error, I let Windows scan and it said it found an error, but I thought safer to do a second factory reset than let Windows fix. So I will not be attempting to use Calibre again with the H2o 2 (my old Touch works fine with Calibre). I am able to use Windows to edit the files on the H2o 2 (have done the full screen reading fix) so it seems to me that Calibre is the problem.

01-02-2018, 12:42 PM	#6
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	Switching to the USB2 has solved my issues. However, transfers within Calibre take much longer. I have a library of about 800 books, but it took 6.5 minutes run the job, "Get list of books on device" and 29 minutes to "Backing up Kobo device database". Is it safe to assume this is solely due to use of USB2? thanks.

01-02-2018, 12:48 PM	#7
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	Huh. A subsequent connection (to update series info on books I uploaded in the previous connection) only took about 1 minute for each of those jobs.

03-28-2018, 12:54 PM	#12
kingzaphod Junior Member Posts: 5 Karma: 10 Join Date: Mar 2018 Device: Kobo Aura H2o	Thank You for the reply so quickly - you are a Gent..! Quote: The way you state that makes me think it didn't work. Is that right? With the User Defined driver, it doesn't access the database on the device, so there shouldn't have been an error like this. The driver will scan the drive looking for books. If you did get the above error, then you need to disable the KoboTouch driver and try again. Well, interesting as I thought I had removed the Kobotouch Extended plugin and then connected with the User defined driver (and go that error message) - so I coudn't have disabled the kobo driver driver properly as the database connected in some manner - please excuse my ignorance as I am not sure why this has happened. Incidentally once I get this error message the laptop's USB port becomes unusable for anything and I have to re-initialise it with a laptop reboot I do have an old Lenovo laptop so will do some testing with that as soon as I have time next week (that is to be the next step to be honest if nothing obvious transpires from this conversation). I will also install a SQLLite management tool to check the database - I like your idea the HP is corrupting the database.....Best I do some more testing and will add back to this thread, really appreciate the time you took to answer - Thanks.

04-02-2018, 10:04 AM	#13
kingzaphod Junior Member Posts: 5 Karma: 10 Join Date: Mar 2018 Device: Kobo Aura H2o	Hi David - as you suspected the issue is with my laptop, even though the issue happened using a USB 2 connection (as well as USB 3) My old Lenovo laptop worked fine using a USB 2 port so I was able to to use the extended Kobo driver and Kobo Utiilties which are so useful, so many thanks. PS - I'm going to get a USB hub with a USB 2 port try that with the HP. Kind Regards Mike

12-22-2018, 05:50 AM	#15
Stevex Addict Posts: 225 Karma: 15318 Join Date: Nov 2015 Device: Kobo Glo HD	Those kind of things can sometimes be caused by voltage errors on the usb ports

Advert

Advert