Aura H2O Kobo Aura H2O Edition 2 not recognised

AstralGisei · 01-14-2018, 03:49 PM

Hi, i have a serious problem with my kobo.
When I plug it into my pc, evrything is fine, the pc recognizes kobo and I'm allowed to navigate and transfer file into it. But when I open calibre, the software attempts to verify which book is in the kobo, nothing happens and then after some seconds windows can't be able to recognizes kobo anymore. Do anyone know how to fix it?

davidfor · 01-14-2018, 05:39 PM

What is the error that calibre displays when this happens?

J_K · 01-14-2018, 06:08 PM

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.

PeterT · 01-14-2018, 06:11 PM

The issue is not with calibre, but with the PC

icallaci · 01-14-2018, 08:14 PM

Quote:

Originally Posted by PeterT

The issue is not with calibre, but with the PC

I'm not sure it is a problem with the PC. My original Mark 6 devices (Aura One and H202) have intermittent problems connecting to all three of the PCs in our house (one Windows 7, one Windows 8.1, one Windows 10). My Mark 5 device (the original H20) never has a problem (same cables, same ports). The most common problem I encounter with the Mark 6 devices is "Error communicating with device" but I also get "This device has errors and needs to be scanned" (or whatever the actual message is--I forget the exact wording), and also a problem where the device connects for a few seconds, then loses the connection. Anyway, the original Aura One and H202 have trouble connecting about 60-70% of the time. It is beyond frustrating. I took a chance and bought an Aura One Limited Edition, which I've had for 4-5 weeks. I have had not a single problem with it. It connects reliably every single time, and it stays connected. I have no idea why the Aura One Limited Edition is so reliable compared to the original Aura One, but there is definitely something going on. I gave up trying to track it down, so this post won't help you, but I wish somebody could figure this out. Good luck.

davidfor · 01-15-2018, 12:44 AM

Quote:

Originally Posted by J_K

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.

JSWolf · 01-15-2018, 05:41 AM

Why not run calibre first and then plug in the H2O2? I always run Calibre first and then plug in my H2O.

davidfor · 01-15-2018, 06:09 AM

Quote:

Originally Posted by JSWolf

Why not run calibre first and then plug in the H2O2? I always run Calibre first and then plug in my H2O.

There shouldn't be any difference. But, it is possible that if the device is slow in mounting properly, then calibre will attempt to access it before it is completely ready. That could cause problems. And people have reported this.

Or, if the filesystem is dirty, calibre will access it while Windows is prompting you for what you want to do. If there is a real problem, it could get worse.

And of course, when you are trying to work out what is wrong, you try all sorts of things. But, connecting without calibre running is what I would recommend in circumstances like the OP describes.

And that brings up a thought. Has anyone with this problem done anything to make sure nothing else is accessing the device? The traditional culprit for this is the virus scanner. But, if there are indexing utilities or something else accessing the device at the same time as calibre, it might help trigger the problem. Even waiting a few minutes before starting calibre might help. I don't think this is a true solution, but it might alleviate things and point to a possible cause.

J_K · 01-15-2018, 08:54 AM

I was using the latest Calibre. I also tried the Touch and that worked fine. I was using a USB 2.0 port.

Shadowjack · 01-15-2018, 11:05 AM

I experienced the same problem with my H2O edition 2 (see https://www.mobileread.com/forums/sh...d.php?t=293370). The solution that worked for me was connecting to a USB 2 port.

icallaci · 01-15-2018, 01:34 PM

Quote:

Originally Posted by Shadowjack

I experienced the same problem with my H2O edition 2 (see https://www.mobileread.com/forums/sh...d.php?t=293370). The solution that worked for me was connecting to a USB 2 port.

USB2 seems to work a little more consistently than USB3, although not 100%. It's difficult for me to test things now because once I received my Aura One Limited Edition, I gave my original Aura One and the H202 to my daughter, so I don't have immediate access to those two devices anymore. But the last time I visited her (in December), I tried connecting the devices to USB2 instead of USB3. Worked once, then failed. I've had all kinds of theories but they're difficult to test when the problem is so random.

JSWolf · 01-15-2018, 07:45 PM

I am curious. What chipset is the USB on the computer where the H2O2 has trouble? Is the USB driver up-to-date? Go to the manufacturer's (of the USB chipset) website and see if they have a newer driver. If not, try the computer manufacturer's website.

I know this isn't USB, but when I got my laptop, the audio sometimes made crackling noises. I went to the chipset manufacturer's website, found a newer driver, installed it and the problem was solved.

icallaci · 01-15-2018, 09:13 PM

I've used five different computers (made by four different manufacturers) to connect various Kobo readers, and the drivers have been updated on all computers. The OS varies from Windows 7 to Windows 8.1 to Windows 10. The same Kobo readers have trouble on all of the computers. The Mark 5 H20 never has a problem on any computer. The Mark 6 Aura One (original) and H202 are frustratingly unstable on all five computers. The Mark 6 Aura One (Limited Edition) is rock solid stable (and it's been connected to four of the five computers that the other Kobo readers have trouble with). I've had several theories (for example, I thought resetting the USB ports or using only USB2 was a clue, but those didn't work on my daughter's computer, so out they went). I've spent countless hours trying to track this down with no luck, and now that I have a stable device, I just want to read.

DNSB · 01-15-2018, 11:39 PM

Quote:

Originally Posted by icallaci

I've spent countless hours trying to track this down with no luck, and now that I have a stable device, I just want to read.

What a odd idea -- actually using an ereader to read. What made you think of it?

Seriously, a lot of people seem to forget that is what we bought the devices for.

icallaci · 01-15-2018, 11:52 PM

Quote:

Originally Posted by DNSB

What a odd idea -- actually using an ereader to read. What made you think of it?

Seriously, a lot of people seem to forget that is what we bought the devices for.

Bingo. Plus, I really don't want to do a lot of testing with my stable Aura One LE at this point, for obvious reasons. If someone comes up with some theories, I might give them a try on the unstable devices the next time I visit my daughter, but I feel very protective towards my working, stable Aura One LE.

01-14-2018, 03:49 PM	#1
AstralGisei Junior Member Posts: 1 Karma: 10 Join Date: Jan 2018 Device: Kobo Aura H20 Edition 2	Kobo Aura H2O Edition 2 not recognised Hi, i have a serious problem with my kobo. When I plug it into my pc, evrything is fine, the pc recognizes kobo and I'm allowed to navigate and transfer file into it. But when I open calibre, the software attempts to verify which book is in the kobo, nothing happens and then after some seconds windows can't be able to recognizes kobo anymore. Do anyone know how to fix it? Last edited by AstralGisei; 01-14-2018 at 03:55 PM.

01-15-2018, 07:45 PM	#12
JSWolf Resident Curmudgeon Posts: 79,591 Karma: 145863177 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	I am curious. What chipset is the USB on the computer where the H2O2 has trouble? Is the USB driver up-to-date? Go to the manufacturer's (of the USB chipset) website and see if they have a newer driver. If not, try the computer manufacturer's website. I know this isn't USB, but when I got my laptop, the audio sometimes made crackling noises. I went to the chipset manufacturer's website, found a newer driver, installed it and the problem was solved. Last edited by JSWolf; 01-15-2018 at 07:47 PM.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Kobo Aura H2O Edition 2 on sale Nov 22 at Chapters Indigo	icedtea_gal	Deals and Resources (No Self-Promotion or Affiliate Links)	0	11-22-2017 05:06 PM
Next model kobo? Kobo Aura H2O Edition 2	surquizu	Kobo Reader	570	11-12-2017 09:18 AM
Can not install KSM 08 on Kobo Aura H2O Edition 2	viktormadarasz	Kobo Reader	11	10-08-2017 12:24 PM
Kobo Aura H2O 2nd Edition vs old Kobo Aura H2O screen dimentions.	iXPert12	Kobo Reader	1	09-18-2017 09:35 AM
Aura H2O Kobo Aura H2O Edition 2	moofychops	Kobo Reader	2	05-27-2017 06:59 PM

01-14-2018, 05:39 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	What is the error that calibre displays when this happens?

01-14-2018, 06:08 PM	#3
J_K Enthusiast Posts: 47 Karma: 26706 Join Date: Jan 2014 Location: London, UK Device: H2O 2, Aura 2, Clara HD, Touch	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.

01-14-2018, 06:11 PM	#4
PeterT Grand Sorcerer Posts: 13,437 Karma: 78880114 Join Date: Nov 2007 Location: Toronto Device: Libra H2O, Libra Colour	The issue is not with calibre, but with the PC

01-15-2018, 05:41 AM	#7
JSWolf Resident Curmudgeon Posts: 79,591 Karma: 145863177 Join Date: Nov 2006 Location: Roslindale, Massachusetts Device: Kobo Libra 2, Kobo Aura H2O, PRS-650, PRS-T1, nook STR, PW3	Why not run calibre first and then plug in the H2O2? I always run Calibre first and then plug in my H2O.

01-15-2018, 08:54 AM	#9
J_K Enthusiast Posts: 47 Karma: 26706 Join Date: Jan 2014 Location: London, UK Device: H2O 2, Aura 2, Clara HD, Touch	I was using the latest Calibre. I also tried the Touch and that worked fine. I was using a USB 2.0 port.

01-15-2018, 11:05 AM	#10
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 experienced the same problem with my H2O edition 2 (see https://www.mobileread.com/forums/sh...d.php?t=293370). The solution that worked for me was connecting to a USB 2 port.

01-15-2018, 09:13 PM	#13
icallaci Guru Posts: 817 Karma: 6528026 Join Date: Sep 2012 Device: Kobo Elipsa	I've used five different computers (made by four different manufacturers) to connect various Kobo readers, and the drivers have been updated on all computers. The OS varies from Windows 7 to Windows 8.1 to Windows 10. The same Kobo readers have trouble on all of the computers. The Mark 5 H20 never has a problem on any computer. The Mark 6 Aura One (original) and H202 are frustratingly unstable on all five computers. The Mark 6 Aura One (Limited Edition) is rock solid stable (and it's been connected to four of the five computers that the other Kobo readers have trouble with). I've had several theories (for example, I thought resetting the USB ports or using only USB2 was a clue, but those didn't work on my daughter's computer, so out they went). I've spent countless hours trying to track this down with no luck, and now that I have a stable device, I just want to read.

Advert

Advert