Thread: Aura H2O Kobo Aura H2O Edition 2 not recognised
View Single Post
Old 01-15-2018, 12:44 AM   #6
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 J_K View Post
This also happened to me on the H2O Edition 2. Calibre was unable to get the list of books and either hung or gave an error about not being able to get the list of books.

I ended up doing a factory reset twice as Windows then showed a 'problem with drive' error after it happened.

I presume there is a problem with Calibre due to the H2O being a fairly new device.
No, it is not a calibre problem unless you are running a version of calibre from before the Aura H2O Edition 2 was released. And that would mean you are using a version of calibre that was over 6 months old. The update to calibre to support the Aura H2O Edition 2 was released in May last year. Probably in the same week the device actually became available.

We don't know what is happening. It seems that there is some instability in the connection between these devices and the PC. And it seems that something in the way that calibre reads the database on the device is triggering it. But, I am sure I could reproduce the problem with other mechanisms if this problem happened to me. And there is another thread discussing a similar sounding issue from someone who doesn't use calibre. In that case, the second or third time the device is connected, while copying files it kills the USB device on the PC and the connection stops.

The problem is that there isn't a good pattern. Some people have problems, some don't. icallaci reported issues with an Aura ONE. I have never had a problem with my Aura ONE. This makes it hard to debug. It could be a fault on particular devices, or it could be a problem with particular PC hardware or drivers. Either would explain why it isn't seen by everyone.

One possible cause is USB3. It seems some PCs with USB3 ports don't like these new devices. Using a USB2 port or a hub seems to fix things. And I think others have gotten it working by changing the ports to USB2 only mode.

I doubt this helps, but, it's my attempt to explain what we know about this problem: very little.

One thing, if Windows is reporting a problem with the drive, it will be one of two reasons. Once is that it is dirty and needs a chckdsk run. This was caused by the disconnect and usually no problems are found. The other is that the USB port is put into a strange state. Neither need a factory reset, but, if the disk is dirty and needed repairs, it might mean the database is corrupt and the setup needs to be done again.
davidfor is offline   Reply With Quote