Kobo reader trouble: can't access it

abject · 2022-03-04 21:56:43

Hello Arch's folks,

I have a Kobo EPub reader that works perfectly... Well for reading book and so it's works as expected. My problem is to connect the reader to my computer.

I suspect an hardware problem on the reader. In fact both OS are up-to-date (Kobo OS on the reader and Arch on the computer). When I plug the reader via the USB cable, the reader ask to be connected (or not) with the computer.I accept and then the reader show the message "you are connected blablabla". From the computer side now the lsusb command see perfectly the Reader, its number, ... dmesg show a connection on a USB port with no error message. However in most of the case nothing happen. The reader is not mounted: it's not appearing in Thunar, Calibre can't see it, no mounting point corresponding appear in mount output.

If I reboot the computer with the Reader plugged, I can see it with Thunar and Calibre detect the device. However any attempt to access it close the connection from the computer side: the device is kind of "ejected". Looking at dmesg I see some error message. I suspect an hardware problem with my reader... Any clues about this?

Here are the lsusb and dmesg output in the second case: when the reader is visible from the computer:

[   30.337410] usb 3-10: new high-speed USB device number 2 using xhci_hcd
[   30.523453] usb 3-10: New USB device found, idVendor=2237, idProduct=4223, bcdDevice= 1.10
[   30.523459] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   30.523462] usb 3-10: Product: eReader-4.31.19086
[   30.523464] usb 3-10: Manufacturer: Kobo
[   30.523466] usb 3-10: SerialNumber: N437623901026
[   30.539558] usb-storage 3-10:1.0: USB Mass Storage device detected
[   30.539787] scsi host4: usb-storage 3-10:1.0
[   30.539878] usbcore: registered new interface driver usb-storage
[   30.543917] usbcore: registered new interface driver uas
[   31.609073] scsi 4:0:0:0: Direct-Access     Kobo     eReader-4.31.190 0110 PQ: 0 ANSI: 2
[   31.613862] sd 4:0:0:0: Power-on or device reset occurred
[   31.616892] sd 4:0:0:0: [sdc] 6632445 512-byte logical blocks: (3.40 GB/3.16 GiB)
[   31.723834] sd 4:0:0:0: [sdc] Write Protect is off
[   31.723838] sd 4:0:0:0: [sdc] Mode Sense: 0f 00 00 00
[   31.833814] sd 4:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   32.055881]  sdc:
[   32.274012] sd 4:0:0:0: [sdc] Attached SCSI removable disk
... Lot of PAM messages that have no links to our problems ...
[  132.929014] usb usb3-port10: disabled by hub (EMI?), re-enabling...
[  132.929020] usb 3-10: USB disconnect, device number 2
[  133.029061] sd 4:0:0:0: [sdc] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK cmd_age=0s
[  133.029075] sd 4:0:0:0: [sdc] tag#0 CDB: Read(10) 28 00 00 54 31 d8 00 00 58 00
[  133.029076] blk_update_request: I/O error, dev sdc, sector 5517784 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
[  133.029098] blk_update_request: I/O error, dev sdc, sector 5517816 op 0x0:(READ) flags 0x80000 phys_seg 1 prio class 0
[  133.029114] blk_update_request: I/O error, dev sdc, sector 5517880 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  133.029121] blk_update_request: I/O error, dev sdc, sector 5517968 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  133.029148] blk_update_request: I/O error, dev sdc, sector 5518040 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[  133.029227] blk_update_request: I/O error, dev sdc, sector 5517784 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  133.029243] blk_update_request: I/O error, dev sdc, sector 4620296 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0
[  133.029247] Buffer I/O error on dev sdc, logical block 4620296, lost async page write
[  133.029265] blk_update_request: I/O error, dev sdc, sector 4621096 op 0x1:(WRITE) flags 0x100000 phys_seg 2 prio class 0
[  133.029266] Buffer I/O error on dev sdc, logical block 4621096, lost async page write
[  133.029268] Buffer I/O error on dev sdc, logical block 4621097, lost async page write
[  133.029273] blk_update_request: I/O error, dev sdc, sector 5517784 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[  133.029277] blk_update_request: I/O error, dev sdc, sector 1303224 op 0x1:(WRITE) flags 0x100000 phys_seg 1 prio class 0
[  133.029279] Buffer I/O error on dev sdc, logical block 1303224, lost async page write
[  133.029295] Buffer I/O error on dev sdc, logical block 1303240, lost async page write
[  133.029304] Buffer I/O error on dev sdc, logical block 4127076, lost async page write
[  133.029305] Buffer I/O error on dev sdc, logical block 4127077, lost async page write
[  133.029306] Buffer I/O error on dev sdc, logical block 4127078, lost async page write
[  133.029307] Buffer I/O error on dev sdc, logical block 4127079, lost async page write
[  133.029315] Buffer I/O error on dev sdc, logical block 5040120, lost async page write
[  133.031471] FAT-fs (sdc): unable to read inode block for updating (i_pos 79868045)
[  133.060192] FAT-fs (sdc): unable to read boot sector to mark fs as dirty
[  133.091152] sd 4:0:0:0: [sdc] Synchronizing SCSI cache
[  133.097839] sd 4:0:0:0: [sdc] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
[  134.347391] usb usb3-port10: Cannot enable. Maybe the USB cable is bad?
[  135.317400] usb usb3-port10: Cannot enable. Maybe the USB cable is bad?
[  135.317443] usb usb3-port10: attempt power cycle
[  136.377532] usb usb3-port10: Cannot enable. Maybe the USB cable is bad?
[  137.337467] usb usb3-port10: Cannot enable. Maybe the USB cable is bad?
[  137.337553] usb usb3-port10: unable to enumerate USB device

And the lsusb output:

Bus 003 Device 002: ID 2237:4223 Kobo Inc. eReader-4.31.19086
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x2237 Kobo Inc.
  idProduct          0x4223 
  bcdDevice            1.10
  iManufacturer           1 Kobo
  iProduct                2 eReader-4.31.19086
  iSerial                 3 #Here is the right serial number
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          4 Self-powered
    bmAttributes         0xc0
      Self Powered
    MaxPower                2mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              5 Mass Storage
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0001
  Self Powered

Of course I tried with several WORKING cables. I also clean the Reader and USB port. Nothing change. The problem persist. I would like to have any hope that is a software problem that I can fix from the computer (or Reader side). However I'm quiet worry with the dmesg message I read that points to a hardware fail.

Any idea to identify more precisely which is the problem?

drewcube · 2022-03-06 03:07:52

I cannot reproduce with my Kobo Glo HD, which is very old (2015) but has up to date software. Mine connects with my Arch install. Mounts, visibile in pcmanfm and I'm able to traverse through the folders on the device, no issues.

Maybe connect the Kobo to a friend's pc to rule out the device?

seth · 2022-03-06 08:07:19

Sounds like a loose jack.
Try to get some *delicate!!!* tension on the plug (build a spring by folding some paper, maybe flipping the reader on its face is enough to have gravity pull the cable the other direction)

abject · 2022-03-08 07:27:42

drewcube wrote:

Maybe connect the Kobo to a friend's pc to rule out the device?

I tried on a laptop with Ubuntu 20.04. I tried several USB port with the same result as with my Arch computer: nothing work, the reader is not detected or not working.
However this laptop has a USB-C port and the reader works well if I connect it on this USB-C port with and USB<->USB-C adapter.

@seth: You might be right. But that's a very weird problem to found and fix... I'll try it.

Last edited by abject (2022-03-08 07:28:14)

seth · 2022-03-08 07:33:40

works well if I connect it on this USB-C port with and USB<->USB-C adapter

So it's the cable?

abject · 2022-03-08 07:47:40

seth wrote:

works well if I connect it on this USB-C port with and USB<->USB-C adapter
So it's the cable?

Sorry I was not clear in my previous message, I use the same cable connected into the Reader. The only thing that change is I use a USB-C port on the laptop (with Ubuntu). And as the cable isn't compatible with USB-C I use an adapter like this one.

I don't thing it's a cable problem. I tried several cable. All of them works well with other device like smartphone.

Is any difference between classic USB2 or USB3 port and USB-C ?

seth · 2022-03-08 08:16:28

USB-C can serve higher currents but the adapter negates that (and also the reader has a built-in power supply) - it's rather a mechanical issue then (the way the adpter angles the cable) or pure coincidence.

abject · 2022-03-08 08:30:33

When connected on USB-C port and so with a working connection, I can explore files, add ebook on the Reader and synchronize the library using Calibre software. The only thing that crash is when I tried to make a backup of the sqlite database stored in the Reader. I tried to save this database using Calibre or directly by coping the sqlite file from the Reader on the computer.

When I copy the file I got error and the device is ejected and re-mounted. In dmesg message I saw some block error. I suspect some hardware corrupted (or damaged) block on the internal Reader memory .

Here are the dmesg log:

[ 90.981296] usb-storage 1-5:1.0: USB Mass Storage device detected
[ 90.981810] scsi host3: usb-storage 1-5:1.0
[ 91.996573] scsi 3:0:0:0: Direct-Access Kobo eReader-4.31.190 0110 PQ: 0 ANSI: 2
[ 91.997205] sd 3:0:0:0: Attached scsi generic sg1 type 0
[ 91.999056] sd 3:0:0:0: Power-on or device reset occurred
[ 92.002055] sd 3:0:0:0: [sdb] 6632445 512-byte logical blocks: (3.40 GB/3.16 GiB)
[ 92.111120] sd 3:0:0:0: [sdb] Write Protect is off
[ 92.111129] sd 3:0:0:0: [sdb] Mode Sense: 0f 00 00 00
[ 92.221174] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 92.464619] sdb:
[ 92.701423] sd 3:0:0:0: [sdb] Attached SCSI removable disk
... Huge amount of UFW AUDIT message
[ 285.023816] usb usb1-port5: disabled by hub (EMI?), re-enabling...
[ 285.023829] usb 1-5: USB disconnect, device number 9
[ 285.023986] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
[ 285.023993] sd 3:0:0:0: [sdb] tag#0 CDB: Read(10) 28 00 00 00 01 10 00 00 f0 00
[ 285.023998] blk_update_request: I/O error, dev sdb, sector 272 op 0x0:(READ) flags 0x80700 phys_seg 29 prio class 0
[ 285.024044] blk_update_request: I/O error, dev sdb, sector 272 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 285.024048] Buffer I/O error on dev sdb, logical block 272, async page read
[ 285.024062] blk_update_request: I/O error, dev sdb, sector 273 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 285.024065] Buffer I/O error on dev sdb, logical block 273, async page read
[ 285.024174] blk_update_request: I/O error, dev sdb, sector 274 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 285.024190] Buffer I/O error on dev sdb, logical block 274, async page read
[ 285.024207] blk_update_request: I/O error, dev sdb, sector 275 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 285.024210] Buffer I/O error on dev sdb, logical block 275, async page read
[ 285.024457] blk_update_request: I/O error, dev sdb, sector 276 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 285.024462] Buffer I/O error on dev sdb, logical block 276, async page read
[ 285.024503] blk_update_request: I/O error, dev sdb, sector 277 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 285.024506] Buffer I/O error on dev sdb, logical block 277, async page read
[ 285.024519] blk_update_request: I/O error, dev sdb, sector 278 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 285.024523] Buffer I/O error on dev sdb, logical block 278, async page read
[ 285.028802] blk_update_request: I/O error, dev sdb, sector 279 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 285.028807] Buffer I/O error on dev sdb, logical block 279, async page read
[ 285.028919] blk_update_request: I/O error, dev sdb, sector 16 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 285.028931] Buffer I/O error on dev sdb, logical block 16, async page read
[ 285.028947] Buffer I/O error on dev sdb, logical block 17, async page read
[ 285.029162] sd 3:0:0:0: [sdb] Synchronizing SCSI cache
[ 285.029198] sd 3:0:0:0: [sdb] Synchronize Cache(10) failed: Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK

I suspect the Reader's memory begin to be old and damaged... For the moment all is working well except the connection with computer but if I can manage at least a quiet stable connection to add new ebook on the device it' fine for me. However, the problem is still here and I can't use it with my Arch computer.

frostschutz · 2022-03-08 10:05:27

you could replace the internal sd card, clone it with ddrescue to a new card

kobo does not handle usb mass storage correctly, it doesn't always properly unmount the vfat filesystem before exporting it. so filesystem corruption is possible but it shouldn't show up as read errors in dmesg.

workaround (at least in current 4.3x firmwares) is to make the usb connection from within an epub book, doesn't work properly for kepub or home menu

Last edited by frostschutz (2022-03-08 10:08:03)

seth · 2022-03-08 13:41:55

The device first disconnects, then you get a bunch of expectable IO errors.
I'm still betting on a loose jack.

frostschutz · 2022-03-08 13:49:20

If nothing else helps, it's possible to install an ftp server on it to transfer files over wifi, and trigger book database update with nickelmenu. You can find such mods on mobileread.com in the Kobo (developer) section.

Then the USB port is only used for charging the battery... hopefully that still works...

abject · 2022-03-08 18:57:48

frostschutz wrote:

you could replace the internal sd card, clone it with ddrescue to a new card
kobo does not handle usb mass storage correctly, it doesn't always properly unmount the vfat filesystem before exporting it. so filesystem corruption is possible but it shouldn't show up as read errors in dmesg.
workaround (at least in current 4.3x firmwares) is to make the usb connection from within an epub book, doesn't work properly for kepub or home menu

My very old Kobo Glo HD has no external SD memory card. You talk about an internal SC card that I could replace. I didn't knew that. How do you proceed?

I'll try the workaround of connection from within an epub. Didn't test it. I'll let you know.

frostschutz wrote:

If nothing else helps, it's possible to install an ftp server on it to transfer files over wifi, and trigger book database update with nickelmenu. You can find such mods on mobileread.com in the Kobo (developer) section.
Then the USB port is only used for charging the battery... hopefully that still works...

USB power supply works like a charm. Until now I was using my own web site to add new ebook to the Kobo by adding the epub file in a web page. But I had to open the browser in the Kobo, then go to the site, download one by one the epub... It's very slow and painful... This idea of having an FTP server could make thing easier. I'll look for it. Thanks a lot for the clue!

abject · 2022-03-10 06:09:37

I tried to connect the Reader within an ebook. I got the same error message from dmesg.

I think we can close this discussion that's help me a lot: at least to be pretty sure that the problem comes from the internal SC card (with either a file system corruption or some bad memory block). I learn some thing thanks to you: Reader has SC card and we can change them or we can install FTP server on a Reader!

For now as the power supply by USB is working and the Reader works as expected except for adding new ebook, I'll keep it intact but if find more problem using it, I'll think to change the SD Card.

My problem is not exactly resolved but the problem wasn't from Arch side. Thanks for your help.

Spheerys · 2022-08-26 13:11:44

I had the same behavior with mounting problem with my Kobo Glo HD and I changed the sdcard (for a bigger one ^^) and it's work perfectly now !
For records, I did a complete copy of the 3 partitions of the original sdcard :

sudo dd if=/dev/sdc of=kobo.img bs=4M

And I extract this image to the new sdcard :

sudo dd of=/dev/sdc if=kobo.img bs=4M

And after, I enlarged the data partition with gparted.

2ManyDogs · 2022-08-26 14:31:44

Closing this old thread.

Arch Linux

#1 2022-03-04 21:56:43

Kobo reader trouble: can't access it

#2 2022-03-06 03:07:52

Re: Kobo reader trouble: can't access it

#3 2022-03-06 08:07:19

Re: Kobo reader trouble: can't access it

#4 2022-03-08 07:27:42

Re: Kobo reader trouble: can't access it

#5 2022-03-08 07:33:40

Re: Kobo reader trouble: can't access it

#6 2022-03-08 07:47:40

Re: Kobo reader trouble: can't access it

#7 2022-03-08 08:16:28

Re: Kobo reader trouble: can't access it

#8 2022-03-08 08:30:33

Re: Kobo reader trouble: can't access it

#9 2022-03-08 10:05:27

Re: Kobo reader trouble: can't access it

#10 2022-03-08 13:41:55

Re: Kobo reader trouble: can't access it

#11 2022-03-08 13:49:20

Re: Kobo reader trouble: can't access it

#12 2022-03-08 18:57:48

Re: Kobo reader trouble: can't access it

#13 2022-03-10 06:09:37

Re: Kobo reader trouble: can't access it

#14 2022-08-26 13:11:44

Re: Kobo reader trouble: can't access it

#15 2022-08-26 14:31:44

Re: Kobo reader trouble: can't access it

Board footer