Linux fails to write to Jetbook SD Card

[louisvd]

Hi

I hope someone can help me - I have tried everything I can think of!

My Jetbook is new (it was my Christmas present)! It is running Firmware v0.35m and Patch v18.

I run Fedora 13 on my home PC (Fedora 14 on my notebook). My notebook has a built-in card reader. Using this I have confirmed that my 16GB SD Card works 100%. I can format it, copy data to and from it, etc. But the moment I insert it into me JetBook I have problems. The Jetbook can READ it, but I can't write data to it via USB from my PC. This WOULD be my preferred way of adding e-books!

I have tested this 16GB card (formatted FAT32), and also a 2GB card (formatted to FAT32 and then FAT16). Both fail. I found something stating that dropping the max_sectors value in
/sys/block/sde/device/max_sectors
to 128 or even 64 (where the default is 240) might work ... but this made no noticeable difference either.

I have noticed that copying only 10 MB of data seems to work. Copying more than that - even in stages - leads to the failure below.

Here are the logs as the JetBook is connected to my PC:

Jan  2 02:32:24 fedora kernel: usb 5-2: new full speed USB device using uhci_hcd and address 32
Jan  2 02:32:24 fedora kernel: usb 5-2: New USB device found, idVendor=0525, idProduct=a4a5
Jan  2 02:32:24 fedora kernel: usb 5-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Jan  2 02:32:24 fedora kernel: usb 5-2: Product: File-backed Storage Gadget
Jan  2 02:32:24 fedora kernel: usb 5-2: Manufacturer: Linux 2.6.16.14 with imx_udc
Jan  2 02:32:24 fedora kernel: usb 5-2: SerialNumber: 3238204E6F76
Jan  2 02:32:24 fedora kernel: scsi48 : usb-storage 5-2:1.0
Jan  2 02:32:25 fedora kernel: scsi 48:0:0:0: Direct-Access     Linux    ebook            0314 PQ: 0 ANSI: 2
Jan  2 02:32:25 fedora kernel: scsi 48:0:0:1: Direct-Access     Linux    ebook            0314 PQ: 0 ANSI: 2
Jan  2 02:32:25 fedora kernel: sd 48:0:0:0: Attached scsi generic sg4 type 0
Jan  2 02:32:25 fedora kernel: sd 48:0:0:1: Attached scsi generic sg5 type 0
Jan  2 02:32:25 fedora kernel: sd 48:0:0:0: [sdd] 186368 512-byte logical blocks: (95.4 MB/91.0 MiB)
Jan  2 02:32:25 fedora kernel: sd 48:0:0:0: [sdd] Write Protect is off
Jan  2 02:32:25 fedora kernel: sd 48:0:0:0: [sdd] Assuming drive cache: write through
Jan  2 02:32:25 fedora kernel: sd 48:0:0:1: [sde] 3987209 512-byte logical blocks: (2.04 GB/1.90 GiB)
Jan  2 02:32:25 fedora kernel: sd 48:0:0:1: [sde] Write Protect is off
Jan  2 02:32:25 fedora kernel: sd 48:0:0:1: [sde] Assuming drive cache: write through
Jan  2 02:32:25 fedora kernel: sd 48:0:0:0: [sdd] Assuming drive cache: write through
Jan  2 02:32:25 fedora kernel: sdd:
Jan  2 02:32:25 fedora kernel: sd 48:0:0:1: [sde] Assuming drive cache: write through
Jan  2 02:32:25 fedora kernel: sde:
Jan  2 02:32:25 fedora kernel: sd 48:0:0:1: [sde] Assuming drive cache: write through
Jan  2 02:32:25 fedora kernel: sd 48:0:0:1: [sde] Attached SCSI removable disk
Jan  2 02:32:25 fedora kernel: sd 48:0:0:0: [sdd] Assuming drive cache: write through
Jan  2 02:32:25 fedora kernel: sd 48:0:0:0: [sdd] Attached SCSI removable disk

The internal memory is sdd and the SD Card is sde. All is well, the devices auto-mount and I can open files on them. Now I begin to copy data to the SD Card. After a minute or two, the first few lines appear in the log:

Jan  2 02:36:35 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:36:45 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:37:01 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:37:02 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:37:12 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32

Once the last line appears, it is immediately followed by a MASSIVE number of lines (of which I include a sample below). The SD Card drive then automatically dismounts (as it goes offline). I manually unmount the internal drive, and disconnect the USB plug. The Jetbook still has the picture of the PC connected to the Reader on the display. The only way to fix this, is to press the RESET button on the back of the unit. Once it resets, I can reconnect it to the PC, but running a file system check returns errors where there are files that have no data and must be truncated:
/Books/Folder/Book1.epub
File size is 2022559 bytes, cluster chain length is 495616 bytes.
Truncating file to 495616 bytes.

Here is the log when the SD Card copy fails with the final USB device reset:

Jan  2 02:37:12 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: Device offlined - not ready after error recovery
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: [sde] Unhandled error code
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: [sde] Result: hostbyte=DID_ABORT driverbyte=DRIVER_OK
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: [sde] CDB: Write(10): 2a 20 00 01 3a 50 00 00 f0 00
Jan  2 02:37:12 fedora kernel: end_request: I/O error, dev sde, sector 80464
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: [sde] Unhandled error code
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: [sde] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: [sde] CDB: Write(10): 2a 00 00 01 3b 40 00 00 f0 00
Jan  2 02:37:12 fedora kernel: end_request: I/O error, dev sde, sector 80704
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: sd 48:0:0:1: rejecting I/O to offline device
Jan  2 02:37:12 fedora kernel: VFS: busy inodes on changed media or resized disk sde
Jan  2 02:37:23 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:37:33 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:37:49 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:37:50 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:38:00 fedora kernel: usb 5-2: reset full speed USB device using uhci_hcd and address 32
Jan  2 02:38:00 fedora kernel: sd 48:0:0:0: Device offlined - not ready after error recovery
Jan  2 02:38:00 fedora kernel: sd 48:0:0:0: rejecting I/O to offline device

Your help would be GREATLY appreciated.

[cromag]

I can't offer too much help, but I can tell you that I use my Acer Aspire One netbook running Ubuntu 10.04 LTS to manage contents of the 2 GB SanDisk SD class 4 card in my Jetbook Lite. The card was formatted on an XP desktop to "FAT" (which would be FAT16, and probably the best option for a 2 GB card) and I have no trouble uploading files to it from Ubuntu while it's in the connected JBL.

Just to make sure I removed the Patriot 16 GB class 10 SDHC card, formatted to FAT32 on the XP desktop, from my pocket camera and put it in the JBL. Files uploaded to it through the JBL with no problem.

Ubuntu uses the Debian kernal, so there may be differences. Also, the Jetboook Lite probably has internal differences from the Jetbook.

Do you have access to a computer running a different OS, even Windows, just to see if you can get the card to write?

[louisvd]

I will try one at work tomorrow. Both my home PC and my laptop run Fedora.

Thanks for the reply. At least I now know it SHOULD work on Linux, as I expect the Jetbook and Jetbook Lite shouldn't be vastly different from an interface point of view.

I guess there is always the chance that my Jetbook is faulty. I am hoping it's not that as postage Internationally is almost the same price as the Jetbook!!

[louisvd]

Nope. Complete fail on the Windows XP PC at work too. I have contacted Tech Support at Ectaco and sent them all the details and logs.

I await their reply.

[cromag]

Good luck!

[Ken Maltby]

Originally Posted by louisvd

Nope. Complete fail on the Windows XP PC at work too. I have contacted Tech Support at Ectaco and sent them all the details and logs.

I await their reply.

I'm not sure what you mean by "Complete fail on the Windows XP PC at work".

Does your XP PC at work have an SD card reader/writer?

Was it that an SD card formatted in the XP PC and given some test files in
a test folder, did not show up in the jetbook's menu, when you iserted it into
your jetbook while it was on? Was there any error message when you
inserted the SD Card? If so, what did it say?

If you are using the Jetbook as an SD card reader/writer for your work XP PC,
do both the Jetbook's internal memory and the SD card in the Jetbook, show
as new drive letters? This should be happening when you connect your
Jetbook to your PC using an USB cable.

XP should popup a window labled "Removable Disk (X: )" and offer to open a
folder in Windows Explorer. If you have an SD Card in the Jetbook then the
Drive letter in the "Removable Disk (X: )" will be the letter assigned to the SD
card and there will be the next lower letter assigned to the Jetbook's internal memory.

You should be able to format a workable FAT32 SD card for the Jetbook using
tools for just about any operating system. (After all, that is one of the
reasons that the relatively simple FAT formats are used for these flash
memory external devices.) The external drive interface in your "notebook" is
sure to be much faster and more stable than working through the old 1.1 USB
interface, to get to the SD card when it is in the Jetbook.

Others who have lost the functioning of the Jetbook's SD card reader, have
gotten it back by "restoring" to factory settings using the Diagnostic Screen
functions built-into the Jetbook. **Caution** doing so can wipe out your
internal user memory, so it is a good idea to first copy the internal memory to
a folder on your PC hard drive, using the USB cable.

To enter the diagnostics screen:
Reset the device.
Then hold down three buttons. They are: "on/off" "zoom" and "menu".
When you see the jetBook screen let go of "on.off". Keep holding the "zoom"
and "menu" keys until you see a 16 item screen.
It's tricky, so it may take a couple of tries.

Then you can reset the Jetbook to factory defaults.

After that is done, reset the device again.

Luck;
Ken

[jorlando]

This line from the log:

I/O error, dev sde, sector 80704

Have you tried a fsck check or scandisk?

Test the card outside of jetbook, you must rule out a bad USB cable problem and a physical card problem

Try another cable, I read a thread where someone received a faulty cable

[louisvd]

I'm not sure what you mean by "Complete fail on the Windows XP PC at work".

First, I bought a 16GB Class 10 SD Card for the unit. I have been able to format it and transfer files to it using my Notebook, which has an internal card reader. I run Fedora 14 on my Notebook. I also have a 2GB Class 4 SD Card, which I ALSO used to test with after having problems with the 16GB Card. Again, this works perfectly in the Notebook's card reader. Thus we can be sure that the SD Cards are OK.

Secondly, I had repeated failure in using my home PC (Fedora 13) and my Notebook (Fedora 14) to copy data successfully to the SD Card inserted into the Jetbook and connected by USB Cable. For this reason I tried my work PC. I thus had failures on three different PC's.

Thirdly, I used three different USB cables in my tests.

Fourthly, I had thus tested on Linux (Fedora 13 and Fedora 14) and Windows XP, so it cannot be an operating system issue.

You can see that I have eliminated all BUT the JetBook.

My tests on XP: (see the first post for details on Linux)
1. Connect the SD card to the PC and format with Linux's ext2 filesystem. I do this because it's not understood by XP, thus forcing the need to reformat it.
2. Insert the SD Card into the Jetbook. Power it on and wait for the main menu. Connect it via USB to the XP PC.
3. The Internal Memory shows as the E: drive. The SD Card is not yet formatted so has no drive letter.
4. Open Disk Manager. The SD Card is listed as a drive without a letter. Right click on it and choose FORMAT. Ensure FAT32 is the filesystem and choose Quick Format. (A fill format takes a LOOONG time and always fails eventually, both from the GUI and from the Command Prompt.)
-- on the 16GB Card this process failed. I formatted it as FAT32 on the Linux Notebook to continue testing with it. When inserted it showed as the F: drive.
-- on the 2GB Card the format succeeded. I suspect that's because there was less to write as it has a smaller FAT table. It showed as the F: drive.
5. Select a folder with e-books in it. Some PDF, some epub, some metadata.opf (generated by Calibre) and some cover.jpg files. Most of the files are less than 500 kB. the largest file is around 19MB, and the folder size is 211MB. Note: I am NOT using Calibre to transfer files, just a normal file system drag and drop / copy and paste. Copy the folder to the F: drive.
6. The copies failed. There were "Delayed Write Failure" yellow pop-up balloons, and the event log show MANY (almost 1 a second) disk events with ID 11 (hard disk controller error). The 2GB lasted longer than the 16GB, but both copies crashed long before the folder copy could complete.

Does your XP PC at work have an SD card reader/writer?

No

Was it that an SD card formatted in the XP PC and given some test files in
a test folder, did not show up in the jetbook's menu, when you iserted it into
your jetbook while it was on? Was there any error message when you
inserted the SD Card? If so, what did it say?

See the test above.
But once data is successfully written to the card by the Notebook, that data is readable by the Jetbook: both in it being able to display the files, and being able to copy it off the card - although this takes a long time because of the USB 1.1 interface.

If you are using the Jetbook as an SD card reader/writer for your work XP PC,
do both the Jetbook's internal memory and the SD card in the Jetbook, show
as new drive letters? This should be happening when you connect your
Jetbook to your PC using an USB cable.

Yes, both show up once the SD Card has been formatted.

XP should popup a window labled "Removable Disk (X: )" and offer to open a
folder in Windows Explorer. If you have an SD Card in the Jetbook then the
Drive letter in the "Removable Disk (X: )" will be the letter assigned to the SD
card and there will be the next lower letter assigned to the Jetbook's internal memory.

Correct

You should be able to format a workable FAT32 SD card for the Jetbook using
tools for just about any operating system. (After all, that is one of the
reasons that the relatively simple FAT formats are used for these flash
memory external devices.) The external drive interface in your "notebook" is
sure to be much faster and more stable than working through the old 1.1 USB
interface, to get to the SD card when it is in the Jetbook.

Whilst that fact is true, I cannot format the 16 GB SD Card that is inserted in the JetBook at the time. The 2 GB did format - once - but failed when I tried it again. Using Linux I can get the 16 GB card formatted.

Others who have lost the functioning of the Jetbook's SD card reader, have
gotten it back by "restoring" to factory settings using the Diagnostic Screen
functions built-into the Jetbook. **Caution** doing so can wipe out your
internal user memory, so it is a good idea to first copy the internal memory to
a folder on your PC hard drive, using the USB cable.

Although I had the problem out of the box with my brand new JetBook I will give this a try and report back.

Thank you to all for your responses thus far.

BTW: Still no reply from Ectaco yet.

[louisvd]

Originally Posted by jorlando

This line from the log:

I/O error, dev sde, sector 80704

Have you tried a fsck check or scandisk?

Test the card outside of jetbook, you must rule out a bad USB cable problem and a physical card problem

Try another cable, I read a thread where someone received a faulty cable

Yes, I did run a fsck. It indicated files with incorrect length, and sometimes lost clusters. Usually I would re-format before testing again to clear the filesystem. The cards work perfectly in my Notebook's card reader, and I tried with three different USB cables.

[Ken Maltby]

So the only issue left is your 16GB SDHC card not formatting to FAT32 in your Notebook,
is that correct?

Using your Jetbook as a USB SD media reader/writer for your home PC makes little sense
when you can get a good USB 2.0 SD media reader/writer for your PC (OS not an issue)
for so little money. Using the Jetbook's SD card reader for anything but storing your
ebook library and other media makes no sense either. All the file manipulation is much
better done on your notebook or PC. As I understand it, you Linux users are using Wine
to run ADE and perhaps other ebook software. You must have some way to handle the
ebook files.

Perhaps there are better formatting utilities for your Linux Notebook?
Or perhaps the SD manufacturer has information on formatting their SD cards?

Luck;
Ken

[louisvd]

Originally Posted by Ken Maltby

So the only issue left is your 16GB SDHC card not formatting to FAT32 in your Notebook,
is that correct?

Using your Jetbook as a USB SD media reader/writer for your home PC makes little sense
when you can get a good USB 2.0 SD media reader/writer for your PC (OS not an issue)
for so little money. Using the Jetbook's SD card reader for anything but storing your
ebook library and other media makes no sense either. All the file manipulation is much
better done on your notebook or PC. As I understand it, you Linux users are using Wine
to run ADE and perhaps other ebook software. You must have some way to handle the
ebook files.

Perhaps there are better formatting utilities for your Linux Notebook?
Or perhaps the SD manufacturer has information on formatting their SD cards?

Luck;
Ken

Hi Ken, I think you misunderstood.

Both SD Cards format and work PERFECTLY in the Notebook's SD Card reader. They fail when accessed through the JetBook via USB.

I am not trying to use the Jetbook as a card reader for my PC. But I WOULD like to be able to copy my ebooks to it via the usb cable - a reasonable expectation I think! Especially since software such as Calibre exists to manage one's ebook collection and synchronise the library to the Jetbook. Cailbre runs natively on many operating systems.

There is no problem using Linux to manage / format / copy to the SD Cards.

One other test I did: I found that if I copy one or two files to the SD card - I am talking less than 5 MB of data (because it crashes around 10 MB) - then it appeared to work. Ejecting the drive, it flushed the data to the drive, and it stayed. But then, adding the device back to the PC and writing more data (again under 5MB) it seemed to crash every time. The only solution then is to press reset on the Jetbook (because even when disconnected, the USB conneted image is on its screen). When restarting I have a filesystem with errors, and the data just written is gone.

Haven't tried the reset yet, but will let you know when I try it later today.

[Ken Maltby]

Well you obviously have a problem with your jetBook, it could be a hardware
defect or in the firmware but the reader and/or USB interface is not working
properly. You should not be having the problem you describe. You should
contact Ectaco for an RMA under the one year warranty.

That said; Calibre can work with your SD card as a removable drive of your PC,
and accomplish everything you can with "send to device". Doing it with a USB
2.0 interface, is a major advantage for that approach. Even with a perfectly
working JBL SD card reader and USB interface, I would never use it the way you
describe.

Luck;
Ken

[jorlando]

louisvd,

if fsck tells that you have a corrupt file system, you have a corrupt filesystem, even if that filesystem appears to be ok under certain circunstances (different computers and/or operating systems)

Maybe windows is more forginving with FAT32 errors than linux (by the way, don't you get an allert message in Windows when you connect the jetbook asking for a filesystem check in the USB drive?)

For now the easier solution is to reformat the card and test it again.

Take care when transfering files to dismount the drive before removing the card I already damged files due late writes.

By the way, it is considered better/faster to use card readers to transfer files to the SD card of your JB, since the JB is a USB 1.1 device. It takes forever to transfer large data amounts to USB 1.1 devices. I really don't have the patience...

[Ken Maltby]

With flash memory there is the issue of "ware leveling" that can be addressed, in part,
by the file structure and format, the normal FAT file format does not have such features.
FAT is still used with flash as it generally works well, but it would be wise to ocasionally
(perhaps once every 3 months) run ChkDsk (for windows based systems) or the UNIX/
Linux equivalent on any active flash memory structures. That is easily accomplished
during a reformat. It is easy to temporally backup an SD card to your hard drive, do the
reformat and file system checks & automatic repairs, then restore the contents to the
SD card. It is much easier to do this using the 2.0 USB interface. For the jetBook's
internal memory you are stuck with using the 1.1 USB interface, but you are only working
with 128MB in total.

The same argument could be made for reflashing the NOR memory (but the technical
reasoning would be a little different).

While it is possible that all OP's SD cards could have been corrupted in the same fashion
so that the same problem occurs on them, I think a problem with the JB is more likely.
While it is new and under warranty I would be sure and address any existing problems,
even if operational practice makes it easier to work in a more efficient manner that is
not impacted by the "problem".

Luck;
Ken

[louisvd]

Thanks Ken. Yes I agree with getting the problem fixed under warranty.

Having discovered the Diagnostics menu you pointed out, and being technical in nature, I have been working through the menu.

A few observations:
1. The key press responses tend to be sluggish!
2. Test 4 - SD Card passes test 4.1. Test 4.2 seems to need some external program. Where can I get that from?
3. Test 6 wants a file copied. usb.bin Any idea where I can get this from?
4. Test 12 I would LOVE to do - Whole USB Test. Again I think it needs external software. Any idea where I can get that from?
5. Test 14 is simple memory check. 14.1 test SD RAM. This passed. 14.2 tests NOR flash checksum. This passed too. 14.3 tests NAND Flash checksum. This has two: mtd3 passed, but mtd4 FAILED (has a X). then it just sits there and doesn't respond to ANY keys (even the green LED is off) and I have to press RESET to get out.

Is there something that this indicates?

Would re-flashing something sort any of this out?

If I could sort this out WITHOUT having to pay Fed-Ex a fortune to ship to and fro between the US and South Africa, I would be glad to try it!!!

One more observation: After performing the Restore to Factory Defaults, yes, my mtd6 was formatted, thus erasing my Internal Memory. So I booted the Jetbook, and the went to the "charging" screen (the USB cable was connected during bootup) but DID mount (only) the Internal Memory. (The SD Card was blanked by me last night.) In this state I copied my backed up contents of that drive to the Jetbook's Internal Memory in one drag and drop operation. No errors. I did an "Eject" and the data flushed to the Jetbook.

So I tried to format the SD Card - the 16GB - (from my Linux PC, with the SD Card in the Jetbook). I mean, if it can write 50MB to the Internal Memory OK, then surely it should manage a few kilobytes for the FAT table during a format. But alas:

Jan 11 22:40:01 fedora kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 18
Jan 11 22:40:12 fedora kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 18
Jan 11 22:40:28 fedora kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 18
Jan 11 22:40:28 fedora kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 18
Jan 11 22:40:38 fedora kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 18
Jan 11 22:40:39 fedora kernel: sd 20:0:0:1: Device offlined - not ready after error recovery

So sadly the Reset didn't work for the SD Card. BTW, the SD Card is formatted WITHOUT a partition table - i.e. the whole device is formatted. I have tried writing a partition table to it and formatting that, but it had made no difference.

Again, thanks for the input.