Ipods react badly to checks for EFI partition tables

[Pontus Schönberg]

My iPod (that worked with Hoary & Breezy) fails to work in Dapper. It mounts automaticly, and unmounts without any problems. But when I try to read or write to it, it freezes after random time (usualy about 10 seconds), with lots of I/O errors in kern.log and sys.log. After that it will fail to unmount, or do anything else. This also corrupts iPods database and all stored data. Only way to fix it is full reset and clearing all settings and data from iPod. (and that needs apple's iPod updater software, only available for OSX and Windows)

Mar 28 16:13:54 localhost kernel: [4295710.047000] usb 1-5: new high speed USB device using ehci_hcd and address 6
Mar 28 16:13:54 localhost kernel: [4295710.162000] scsi5 : SCSI emulation for USB Mass Storage devices
Mar 28 16:13:59 localhost kernel: [4295715.163000] Vendor: Apple Model: iPod Rev: 1.62
Mar 28 16:13:59 localhosWht kernel: [4295715.163000] Type: Direct-Access ANSI SCSI revision: 00
Mar 28 16:13:59 localhost kernel: [4295715.164000] SCSI device sdb: 12000555 512-byte hdwr sectors (6144 MB)
Mar 28 16:13:59 localhost kernel: [4295715.165000] sdb: Write Protect is off
Mar 28 16:13:59 localhost kernel: [4295715.167000] SCSI device sdb: 12000555 512-byte hdwr sectors (6144 MB)
Mar 28 16:13:59 localhost kernel: [4295715.167000] sdb: Write Protect is off
Mar 28 16:14:00 localhost kernel: [4295715.167000] sdb: sdb1 sdb2
Mar 28 16:14:00 localhost kernel: [4295715.483000] sd 5:0:0:0: Attached scsi removable disk sdb
Mar 28 16:14:00 localhost kernel: [4295715.483000] sd 5:0:0:0: Attached scsi generic sg1 type 0
.
.
Mar 28 16:27:58 localhost kernel: [4296554.241000] usb 1-5: reset high speed USB device using ehci_hcd and address 6
Mar 28 16:27:58 localhost kernel: [4296554.356000] sd 5:0:0:0: scsi: Device offlined - not ready after error recovery
Mar 28 16:27:58 localhost kernel: [4296554.356000] sd 5:0:0:0: SCSI error: return code = 0x50000
Mar 28 16:27:58 localhost kernel: [4296554.356000] end_request: I/O error, dev sdb, sector 1416681
Mar 28 16:27:58 localhost kernel: [4296554.356000] printk: 152925 messages suppressed.
Mar 28 16:27:58 localhost kernel: [4296554.356000] lost page write due to I/O error on sdb2
Mar 28 16:27:58 localhost last message repeated 9 times
Mar 28 16:27:58 localhost kernel: [4296554.367000] sd 5:0:0:0: SCSI error: return code = 0x10000
Mar 28 16:27:58 localhost kernel: [4296554.367000] end_request: I/O error, dev sdb, sector 1416809
Mar 28 16:28:19 localhost kernel: [4296574.521000] printk: 53765 messages suppressed.
Mar 28 16:28:27 localhost kernel: [4296582.814000] printk: 20 messages suppressed.
Mar 28 16:28:27 localhost kernel: [4296582.814000] lost page write due to I/O error on sdb2
.
.
Mar 28 14:45:51 localhost kernel: [4311435.158000] usb 1-5: reset high speed USB device using ehci_hcd and address 7
Mar 28 14:46:02 localhost kernel: [4311445.378000] usb 1-5: reset high speed USB device using ehci_hcd and address 7
Mar 28 14:46:18 localhost kernel: [4311461.697000] usb 1-5: reset high speed USB device using ehci_hcd and address 7
Mar 28 14:46:18 localhost kernel: [4311461.915000] usb 1-5: reset high speed USB device using ehci_hcd and address 7
Mar 28 14:46:28 localhost kernel: [4311472.132000] usb 1-5: reset high speed USB device using ehci_hcd and address 7
Mar 28 14:46:28 localhost kernel: [4311472.247000] sd 6:0:0:0: scsi: Device offlined - not ready after error recovery
Mar 28 14:46:28 localhost kernel: [4311472.247000] sd 6:0:0:0: SCSI error: return code = 0x50000
Mar 28 14:46:28 localhost kernel: [4311472.247000] end_request: I/O error, dev sdb, sector 1701609
Mar 28 14:46:30 localhost kernel: <<3>[4311473.240000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:46:31 localhost kernel: <3<3>[4311474.240000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:46:33 localhost kernel: [4311477.247000] printk: 602161 messages suppressed.
Mar 28 14:46:34 localhost kernel: <<3>[4311477.792000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:46:38 localhost kernel: [4311482.247000] printk: 309879 messages suppressed.
Mar 28 14:46:43 localhost kernel: [4311487.247000] printk: 338423 messages suppressed.
Mar 28 14:46:47 localhost kernel: <<3>[4311490.471000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:46:47 localhost kernel: <<3>[4311491.000000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:46:48 localhost kernel: [4311492.311000] printk: 350391 messages suppressed.
Mar 28 14:46:52 localhost kernel: <<3>[4311495.379000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:46:52 localhost kernel: <<3>[4311495.858000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:46:53 localhost kernel: [4311497.247000] printk: 365375 messages suppressed.
Mar 28 14:46:55 localhost kernel: <<3>[4311498.818000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:46:58 localhost kernel: [4311502.270000] printk: 356711 messages suppressed.
Mar 28 14:46:59 localhost kernel: <<3>[4311502.941000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:00 localhost kernel: <<3>[4311503.636000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:01 localhost kernel: <<3>[4311504.265000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:01 localhost kernel: <<3>[4311504.891000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:02 localhost kernel: <<3>[4311505.479000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:02 localhost kernel: <<3>[4311506.066000] sd 6:0:0:0<3>[4311506.066000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:03 localhost kernel: <<3>[4311506.732000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:04 localhost kernel: [4311507.255000] printk: 662527 messages suppressed.
Mar 28 14:47:04 localhost kernel: <<3>[4311508.003000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:05 localhost kernel: <<3>[4311508.616000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:05 localhost kernel: <<3>[4311509.188000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:06 localhost kernel: <<3>[4311509.791000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:07 localhost kernel: <<3>[4311510.378000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:07 localhost kernel: <<3>[4311510.929000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:08 localhost kernel: <<3>[4311511.544000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:08 localhost kernel: <<3>[4311512.191000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:09 localhost kernel: <<3>[4311512.821000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:10 localhost kernel: <<3>[4311513.388000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:10 localhost kernel: <<3>[4311513.990000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:11 localhost kernel: <<3>[4311514.658000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:12 localhost kernel: <<3>[4311515.327000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:12 localhost kernel: <<3>[4311516.010000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:13 localhost kernel: <<3>[4311516.666000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:14 localhost kernel: [4311517.263000] printk: 676744 messages suppressed.
Mar 28 14:47:14 localhost kernel: <<3>[4311518.044000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:15 localhost kernel: <<3>[4311518.638000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:16 localhost kernel: <<3>[4311519.268000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:16 localhost kernel: <<3>[4311519.866000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:17 localhost kernel: <<3>[4311520.483000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:17 localhost kernel: <<3>[4311521.021000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:18 localhost kernel: <<3>[4311521.711000] sd 6:0:0:0: rejecting I/O to offline device
Mar 28 14:47:19 localhost kernel: [4311522.247000] printk: 730416 messages suppressed.

kern.log:

Mar 28 14:12:00 localhost kernel: [4309403.225000] usb 1-5: new high speed USB device using ehci_hcd and address 3
Mar 28 14:12:01 localhost kernel: [4309403.423000] Initializing USB Mass Storage driver...
Mar 28 14:12:01 localhost kernel: [4309403.423000] scsi2 : SCSI emulation for USB Mass Storage devices
Mar 28 14:12:01 localhost kernel: [4309403.424000] usb-storage: device found at 3
Mar 28 14:12:01 localhost kernel: [4309403.424000] usb-storage: waiting for device to settle before scanning
Mar 28 14:12:01 localhost kernel: [4309403.424000] usbcore: registered new driver usb-storage
Mar 28 14:12:01 localhost kernel: [4309403.424000] USB Mass Storage support registered.
Mar 28 14:12:06 localhost kernel: [4309408.425000] Vendor: Apple Model: iPod Rev: 1.62
Mar 28 14:12:06 localhost kernel: [4309408.425000] Type: Direct-Access ANSI SCSI revision: 00
Mar 28 14:12:06 localhost kernel: [4309408.427000] SCSI device sdb: 12000555 512-byte hdwr sectors (6144 MB)
Mar 28 14:12:06 localhost kernel: [4309408.428000] sdb: Write Protect is off
Mar 28 14:12:06 localhost kernel: [4309408.428000] sdb: Mode Sense: 64 00 00 08
Mar 28 14:12:06 localhost kernel: [4309408.428000] sdb: assuming drive cache: write through
Mar 28 14:12:06 localhost kernel: [4309408.429000] SCSI device sdb: 12000555 512-byte hdwr sectors (6144 MB)
Mar 28 14:12:06 localhost kernel: [4309408.430000] sdb: Write Protect is off
Mar 28 14:12:06 localhost kernel: [4309408.430000] sdb: Mode Sense: 64 00 00 08
Mar 28 14:12:06 localhost kernel: [4309408.430000] sdb: assuming drive cache: write through
Mar 28 14:12:06 localhost kernel: [4309408.430000] sdb: sdb1 sdb2
Mar 28 14:12:06 localhost kernel: [4309408.774000] sd 2:0:0:0: Attached scsi removable disk sdb
Mar 28 14:12:06 localhost kernel: [4309408.774000] sd 2:0:0:0: Attached scsi generic sg1 type 0
Mar 28 14:12:06 localhost kernel: [4309408.775000] usb-storage: device scan complete
Mar 28 14:12:07 localhost kernel: [4309409.756000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Mar 28 14:13:49 localhost kernel: [4309512.063000] usb 1-5: reset high speed USB device using ehci_hcd and address 3
Mar 28 14:14:19 localhost kernel: [4309542.280000] usb 1-5: reset high speed USB device using ehci_hcd and address 3
Mar 28 14:14:30 localhost kernel: [4309552.497000] usb 1-5: reset high speed USB device using ehci_hcd and address 3
Mar 28 14:14:46 localhost kernel: [4309568.816000] usb 1-5: reset high speed USB device using ehci_hcd and address 3
Mar 28 14:14:46 localhost kernel: [4309569.034000] usb 1-5: reset high speed USB device using ehci_hcd and address 3
Mar 28 14:14:56 localhost kernel: [4309579.252000] usb 1-5: reset high speed USB device using ehci_hcd and address 3
Mar 28 14:14:57 localhost kernel: [4309579.369000] sd 2:0:0:0: scsi: Device offlined - not ready after error recovery
Mar 28 14:14:57 localhost kernel: [4309579.369000] sd 2:0:0:0: SCSI error: return code = 0x50000
Mar 28 14:14:57 localhost kernel: [4309579.369000] end_request: I/O error, dev sdb, sector 2867905
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787580
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787581
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787582
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787583
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787584
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787585
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787586
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787587
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787588
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] Buffer I/O error on device sdb2, logical block 2787589
Mar 28 14:14:57 localhost kernel: [4309579.369000] lost page write due to I/O error on sdb2
Mar 28 14:14:57 localhost kernel: [4309579.369000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 130 times
Mar 28 14:14:57 localhost kernel: [4309579.380000] sd 2:0:0:0: SCSI error: return code = 0x10000
Mar 28 14:14:57 localhost kernel: [4309579.380000] end_request: I/O error, dev sdb, sector 2868033
Mar 28 14:14:57 localhost kernel: [4309579.380000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.384000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.385000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 5 times
Mar 28 14:14:57 localhost kernel: [4309579.388000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.388000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.392000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.393000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.394000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.395000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 5 times
Mar 28 14:14:57 localhost kernel: [4309579.396000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.397000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.398000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.399000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.400000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
Mar 28 14:14:57 localhost kernel: [4309579.401000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 5 times
Mar 28 14:14:57 localhost kernel: [4309579.406000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 5 times
Mar 28 14:14:57 localhost kernel: [4309579.407000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 5 times
Mar 28 14:14:57 localhost kernel: [4309579.408000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 8 times
.
.
Mar 28 14:14:57 localhost kernel: [4309579.596000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 4 times
Mar 28 14:14:57 localhost kernel: [4309579.597000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.597000] FAT: Directory bread(block 547583) failed
Mar 28 14:14:57 localhost kernel: [4309579.597000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.597000] FAT: Directory bread(block 547583) failed
Mar 28 14:14:57 localhost kernel: [4309579.597000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.597000] FAT: Directory bread(block 547583) failed
Mar 28 14:14:57 localhost kernel: [4309579.598000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 9 times
Mar 28 14:14:57 localhost kernel: [4309579.599000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 2 times
Mar 28 14:14:57 localhost kernel: [4309579.599000] FAT: Directory bread(block 547580) failed
Mar 28 14:14:57 localhost kernel: [4309579.599000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.599000] FAT: Directory bread(block 547583) failed
Mar 28 14:14:57 localhost kernel: [4309579.599000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 2 times
Mar 28 14:14:57 localhost kernel: [4309579.599000] FAT: Directory bread(block 547580) failed
Mar 28 14:14:57 localhost kernel: [4309579.599000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.599000] FAT: Directory bread(block 547583) failed
Mar 28 14:14:57 localhost kernel: [4309579.599000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost last message repeated 2 times
Mar 28 14:14:57 localhost kernel: [4309579.599000] FAT: Directory bread(block 547580) failed
Mar 28 14:14:57 localhost kernel: [4309579.599000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.599000] FAT: Directory bread(block 547583) failed
Mar 28 14:14:57 localhost kernel: [4309579.599000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.599000] FAT: FAT read failed (blocknr 2616)
Mar 28 14:14:57 localhost kernel: [4309579.599000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.599000] FAT: bread failed in fat_clusters_flush
Mar 28 14:14:57 localhost kernel: [4309579.636000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.636000] FAT: FAT read failed (blocknr 2815)
Mar 28 14:14:57 localhost kernel: [4309579.636000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.636000] FAT: bread failed in fat_clusters_flush
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: FAT read failed (blocknr 2815)
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: bread failed in fat_clusters_flush
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: FAT read failed (blocknr 2815)
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: bread failed in fat_clusters_flush
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: FAT read failed (blocknr 2815)
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: bread failed in fat_clusters_flush
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: FAT read failed (blocknr 2815)
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: bread failed in fat_clusters_flush
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: FAT read failed (blocknr 2815)
Mar 28 14:14:57 localhost kernel: [4309579.637000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.637000] FAT: bread failed in fat_clusters_flush
Mar 28 14:14:57 localhost kernel: [4309579.638000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.638000] FAT: FAT read failed (blocknr 2815)
Mar 28 14:14:57 localhost kernel: [4309579.638000] sd 2:0:0:0: rejecting I/O to offline device
Mar 28 14:14:57 localhost kernel: [4309579.638000] FAT: bread failed in fat_clusters_flush

After searhing for any solution this I found this:

"When connecting an iPod via USB to a 2.6 kernel machine the iPod will
be recognized but not work correctly. In /var/log/messages you'll see
the a bunch of "Buffer I/O error on device sd?" when connecting the
iPod (Jonas Bergler, Kevin Venkiteswaran)

Solution (by "jeffmock"):

Disable CONFIG_EFI_PARTITION (File Systems -> Partition Types ->
Advanced Partition Selection -> EFI GUID Partition support) in your
kernel configuration, recompile.

Details can be found at
http://www.linuxquestions.org/questions/showthread.php?postid=1197015#post1197015

Excerpt:

"This problem could potentially happen with both 2.4 and 2.6 kernels.

A longer story follows and perhaps someone can come up with a more
sensible solution for the long run.

The iPod looks like a removable disk drive to the host computer. When it
is attached to the computer, the mini iPod reports a capacity of 7999488
512-byte sectors (or about 4GB). This turns out to be wrong for whatever
reason. The mini iPod only really has 7999376 sectors and it exaggerates
by 112 sectors. The other quality of the iPod is that if the computer
attempts to read a sector greater than the actual capacity but less than
the reported capacity, the iPod will dutifully report an I/O error, but
it won't respond to any future requests until you unplug/plug the iPod."

I followed the kernel recompile instructions for distro, disabled only
the CONFIG_EFI_PARTITION option, and things ran perfectly for me
afterwards. As indicated above, hopefully a better long-term solution
will emerge soon."

(Jorg Schuler: it seems a patch was introduced in kernel version 2.6.10:
"<email address hidden> [PATCH] USB Storage: Add unusual_devs entry for iPod
This patch adds an unusual_devs.h entry for the Apple iPod as it
reports one too many sectors. The patch was submitted by
Avi Kivity <email address hidden> and re-diffed by me.")"

As that was only thing worth trying, I recompiled kernel disabling EFI-PARTITION, and that solved the problem.

With EFI partition support disabled my iPod works perfectly. But that is hardly a suitable solution for all users, and the quoted post mentions a patch that fixes this problem allowing both EFI and iPods to be supported at the same time..

[Ben Collins (ben-collins)]

Have you tried to locate this patch and compile it with EFI enabled to see if it works as expected?

[Joachim Beckers (jbeckers)]

"Jorg Schuler: it seems a patch was introduced in kernel version 2.6.10" => it's included by default. so clearly it doesn't do the right job.

is there any way to disable EFI at boot-time? if not, the only way to fix this is by disabling it completely, I guess.

[EJ Finneran (ej-finneran)]

I had errors like this and the thing that fixed it was not plugging the iPod into a USB hub but directly into the computer itself.

I'm running dapper with kernel 2.6.15-21-k7 with a 4th Gen 20GB non-Photo iPod and it works fine.

[Joachim Beckers (jbeckers)]

I know that's a workaround, but not for everyone IMO. Imagine a laptop that has only one USB port (quite common right?). Now imagine that the user of this laptop cannot use his iPod trough a USB hub. It'll quickly become a hassle to switch cables all the time (even more so if there's a USB mouse connected, that the user will not be able to use while the iPod is connected). I could go on, but I guess you see my point.

Also, for the owners of this thing:
http://catalog.belkin.com/IWCatProductPage.process?Product_Id=250094
connecting without a hub is simply impossible. It's just a hub with a iPod dock connector mounted on top. I have one of those.

I'm thinking this issue should be reported upstream. can anyone fix that in launchpad? I'm not sure how to do that.

[Pontus Schönberg (pontus-schonberg)]

I haven't been able to locate the patch, but I'm still looking for it, but I've understood that it makes a special dev entry for iPods, just like there is one already, only the existing one doesn't work for all iPod versions..

Anyway, I'm not using any USB hub, I plug my iPod straight to the motherboards connectors, so no help there..

[Ylan (ylan-segal)]

I can report the same error while pluggin in my iPod directly into my laptop, on either one of the two ports. I haven't tried writting to it, just reading (this my iPod has not been corrupted yet). dosfsck reports no errors on the iPod (System log appropriate entries are at the bottom).

Hardware:
- Sony Vaio PEG-505exp
- iPod 20Gb click-wheel (no photo), windows formatted
Software:
- Ubuntu Dapper

Is it possible for someone to post to one of the repositories (or elsewhere) the kernel compiled with the workaround? It would make it much easier for users like me to get a quick fix without having to build the kernel ourselves (which is, quite frankly, way over my head).

Thanks,

System log:

Jun 15 20:21:04 ylan-laptop kernel: [4294856.736000] usb 4-1: new high speed USB device using ehci_hcd and address 3
Jun 15 20:21:04 ylan-laptop kernel: [4294856.852000] scsi1 : SCSI emulation for USB Mass Storage devices
Jun 15 20:21:04 ylan-laptop kernel: [4294856.852000] usb-storage: device found at 3
Jun 15 20:21:04 ylan-laptop kernel: [4294856.852000] usb-storage: waiting for device to settle before scanning
Jun 15 20:21:09 ylan-laptop kernel: [4294861.852000] Vendor: Apple Model: iPod Rev: 1.62
Jun 15 20:21:09 ylan-laptop kernel: [4294861.853000] Type: Direct-Access ANSI SCSI revision: 00
Jun 15 20:21:09 ylan-laptop kernel: [4294861.854000] SCSI device sdb: 39063023 512-byte hdwr sectors (20000 MB)
Jun 15 20:21:09 ylan-laptop kernel: [4294861.855000] sdb: Write Protect is off
Jun 15 20:21:09 ylan-laptop kernel: [4294861.855000] sdb: Mode Sense: 64 00 00 08
Jun 15 20:21:09 ylan-laptop kernel: [4294861.855000] sdb: assuming drive cache: write through
Jun 15 20:21:09 ylan-laptop kernel: [4294861.858000] SCSI device sdb: 39063023 512-byte hdwr sectors (20000 MB)
Jun 15 20:21:09 ylan-laptop kernel: [4294861.859000] sdb: Write Protect is off
Jun 15 20:21:09 ylan-laptop kernel: [4294861.859000] sdb: Mode Sense: 64 00 00 08
Jun 15 20:21:09 ylan-laptop kernel: [4294861.859000] sdb: assuming drive cache: write through
Jun 15 20:21:09 ylan-laptop kernel: [4294861.859000] sdb: sdb1 sdb2
Jun 15 20:21:09 ylan-laptop kernel: [4294861.882000] sd 1:0:0:0: Attached scsi removable disk sdb
Jun 15 20:21:09 ylan-laptop kernel: [4294861.882000] sd 1:0:0:0: Attached scsi generic sg1 type 0
Jun 15 20:21:09 ylan-laptop kernel: [4294861.883000] usb-storage: device scan complete
Jun 15 20:21:10 ylan-laptop kernel: [4294863.018000] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
Jun 15 20:27:30 ylan-laptop kernel: [4295243.091000] sd 1:0:0:0: SCSI error: return code = 0x8000002
Jun 15 20:27:30 ylan-laptop kernel: [4295243.091000] sdb: Current: sense key: Medium Error
Jun 15 20:27:30 ylan-laptop kernel: [4295243.091000] Additional sense: No additional sense information
Jun 15 20:27:30 ylan-laptop kernel: [4295243.091000] Info fld=0x0
Jun 15 20:27:30 ylan-laptop kernel: [4295243.091000] end_request: I/O error, dev sdb, sector 287597
Jun 15 20:27:30 ylan-laptop kernel: [4295243.091000] Buffer I/O error on device sdb2, logical block 207272
Jun...

[Joachim Beckers (jbeckers)]

so, to add it all up:

1) the current breezy kernel fries ipods

2) whether they're connected trough a hub or not

3) because there's a problem with it's firmware and how EFI handles the ipod's requests

4) and the patch that everyone is talking about is in the kernel already:
see: http://www.kernel.org/pub/linux/kernel/v2.6/testing/ChangeLog-2.6.10-rc2 (search for "Add unusual_devs entry for iPod")

5) the patch doesn't do what it should do

possible solutions:
* recompiling the kernel without EFI support
* fix the kernel

[Joachim Beckers (jbeckers)]

I double checked some things:

# apt-get install linux-source
# cd /usr/src/linux-source-2.6.15
# find ./ -name "unusual*"
./drivers/usb/storage/unusual_devs.h

so far so good. now upon inspection of this file, it turns out to have:

/* Submitted by Sven Anderson <email address hidden>
 * There are at least four ProductIDs used for iPods, so I added 0x1202 and
 * 0x1204. They just need the US_FL_FIX_CAPACITY. As the bcdDevice appears
 * to change with firmware updates, I changed the range to maximum for all
 * iPod entries.
 */
UNUSUAL_DEV( 0x05ac, 0x1202, 0x0000, 0x9999,
  "Apple",
  "iPod",
  US_SC_DEVICE, US_PR_DEVICE, NULL,
  US_FL_FIX_CAPACITY ),

/* Reported by Avi Kivity <email address hidden> */
UNUSUAL_DEV( 0x05ac, 0x1203, 0x0000, 0x9999,
  "Apple",
  "iPod",
  US_SC_DEVICE, US_PR_DEVICE, NULL,
  US_FL_FIX_CAPACITY ),

UNUSUAL_DEV( 0x05ac, 0x1204, 0x0000, 0x9999,
  "Apple",
  "iPod",
  US_SC_DEVICE, US_PR_DEVICE, NULL,
  US_FL_FIX_CAPACITY ),

UNUSUAL_DEV( 0x05ac, 0x1205, 0x0000, 0x9999,
  "Apple",
  "iPod",
  US_SC_DEVICE, US_PR_DEVICE, NULL,
  US_FL_FIX_CAPACITY ),

/*
 * Reported by Tyson Vinson <email address hidden>
 * This particular productId is the iPod Nano
 */
UNUSUAL_DEV( 0x05ac, 0x120a, 0x0000, 0x9999,
  "Apple",
  "iPod",
  US_SC_DEVICE, US_PR_DEVICE, NULL,
  US_FL_FIX_CAPACITY ),

so everything is there for it to work. my ipod is the 0x1203 type, according to hal-device-manager, but it does have problems.

[Ylan (ylan-segal)]

Update: Today, I was prompted by dapper to install a kernel update (2.6.15-25-386) and the problems with the iPod are still there.

[Matthew Garrett (mjg59)]

The alternate gpt tends to be at the end of the disk - I suspect that the EFI partition table check attempts to read from the last block declared by the ipod, the scsi layer chokes (due to that block not actually existing) and then everything falls over. The real issue is why the USB quirk is executed when the hardware is plugged in directly, but not when via a hub.

[Ylan (ylan-segal)]

I compiled a kernel without EFI support, like mentioned here, but I still encountered the same problems with the iPod.

Does this mean that the problem is not only related to EFI support?

I am using a Sony Vaio laptop (505exp) and it has two usb ports (one on each side of the computer). Could it be that it has some sort of internal USB hub and that is causing the problems?

[barryvoeten (barryvoeten)]

Same problem is here for the Cowon iAUDIO 6. This is also a USB disk device to play mp3/ogg etc.

Jul 3 04:34:46 flamingo kernel: [17179683.720000] usb 3-8: new high speed USB device using ehci_hcd and address 4
Jul 3 04:34:46 flamingo kernel: [17179683.968000] usb 3-8: new high speed USB device using ehci_hcd and address 5
Jul 3 04:34:46 flamingo kernel: [17179684.324000] scsi4 : SCSI emulation for USB Mass Storage devices
Jul 3 04:34:51 flamingo kernel: [17179689.360000] Vendor: COWON Model: iAUDIO 6 Rev: 0100
Jul 3 04:34:51 flamingo kernel: [17179689.360000] Type: Direct-Access ANSI SCSI revision: 00
Jul 3 04:34:51 flamingo kernel: [17179689.360000] SCSI device sda: 7855648 512-byte hdwr sectors (4022 MB)
Jul 3 04:34:51 flamingo kernel: [17179689.360000] sda: Write Protect is off
Jul 3 04:34:51 flamingo kernel: [17179689.364000] SCSI device sda: 7855648 512-byte hdwr sectors (4022 MB)
Jul 3 04:34:51 flamingo kernel: [17179689.364000] sda: Write Protect is off
Jul 3 04:34:51 flamingo kernel: [17179689.364000] sda:<6>usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:52 flamingo kernel: [17179689.880000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:52 flamingo kernel: [17179690.300000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:53 flamingo kernel: [17179690.664000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:53 flamingo kernel: [17179691.032000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:53 flamingo kernel: [17179691.288000] sd 4:0:0:0: SCSI error: return code = 0x70000
Jul 3 04:34:53 flamingo kernel: [17179691.288000] end_request: I/O error, dev sda, sector 0
Jul 3 04:34:53 flamingo kernel: [17179691.296000] unable to read partition table
Jul 3 04:34:53 flamingo kernel: [17179691.296000] sd 4:0:0:0: Attached scsi removable disk sda
Jul 3 04:34:53 flamingo kernel: [17179691.296000] sd 4:0:0:0: Attached scsi generic sg0 type 0
Jul 3 04:34:53 flamingo kernel: [17179691.548000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:54 flamingo kernel: [17179691.916000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:54 flamingo kernel: [17179692.280000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:55 flamingo kernel: [17179692.648000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:55 flamingo kernel: [17179693.016000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:55 flamingo kernel: [17179693.272000] sd 4:0:0:0: SCSI error: return code = 0x70000
Jul 3 04:34:55 flamingo kernel: [17179693.272000] end_request: I/O error, dev sda, sector 64
Jul 3 04:34:55 flamingo kernel: [17179693.384000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:56 flamingo kernel: [17179693.752000] usb 3-8: reset high speed USB device using ehci_hcd and address 5
Jul 3 04:34:56 flamingo kernel: [17179694.116000] usb 3-8: reset high spe...

[Joachim Beckers (jbeckers)]

with/without a hub? is there an enrty in /usr/src/linux-source-2.6.15/drivers/usb/storage/unusual_devs.h for it?

[scido (domi-mailing-list)]

Hi everyone. I've got an iPod Nano 4Gb and I get some problems. First, I found a difference between kernel 2.6.15-23 and 2.6.15-25. With the last one (2.6.15-25) I'm unable to copy both files using konqueror (as a normal USB Hard Disk) and music or photos using software like amarok, gpixpod and so on. With kernel 2.6.15-23 I'm able to copy music and photos with amarok and gpixpod BUT I'm unable to copy files using konqueror: when I try to do it, I get the same error:

reset high speed USB device using ehci_hcd and address

I tried vanilla kernel from kernel.org (2.6.17.3) too, but nothing changes.

I hope it'll help someone to resolve this problem.

Regards
Scido

[Kirk Bridger (kbridger)]

I'm seeing the exact same problem on Dapper - my 40 GB iPod Photo is mounted and is browseable via Nautilus, but gtkpod fails to find the iTunes database. Launching gtkpod produces the following in /var/log/messages

Jul 12 19:11:01 localhost kernel: [ 140.716633] usb 7-5: reset high speed USB device using ehci_hcd and address 2
Jul 12 19:11:02 localhost kernel: [ 140.783302] sd 1:0:0:0: SCSI error: return code = 0x70000
Jul 12 19:11:02 localhost kernel: [ 140.783307] end_request: I/O error, dev sdb, sector 20549599
Jul 12 19:11:02 localhost kernel: [ 140.783312] end_request: I/O error, dev sdb, sector 20549600
Jul 12 19:11:32 localhost kernel: [ 155.810031] usb 7-5: reset high speed USB device using ehci_hcd and address 2
Jul 12 19:11:42 localhost kernel: [ 160.924336] usb 7-5: reset high speed USB device using ehci_hcd and address 2
Jul 12 19:11:58 localhost kernel: [ 169.106827] usb 7-5: reset high speed USB device using ehci_hcd and address 2
Jul 12 19:11:59 localhost kernel: [ 169.234583] usb 7-5: reset high speed USB device using ehci_hcd and address 2
Jul 12 19:12:09 localhost kernel: [ 174.348892] usb 7-5: reset high speed USB device using ehci_hcd and address 2
Jul 12 19:12:09 localhost kernel: [ 174.417881] sd 1:0:0:0: scsi: Device offlined - not ready after error recovery
Jul 12 19:12:09 localhost kernel: [ 174.417889] sd 1:0:0:0: SCSI error: return code = 0x50000
Jul 12 19:12:09 localhost kernel: [ 174.417891] end_request: I/O error, dev sdb, sector 20549599
Jul 12 19:12:09 localhost kernel: [ 174.417912] lost page write due to I/O error on sdb2

The iPod is conneted via a USB PCI card to the dock directly. This is after upgrading the kernel this afternoon to 2.6.15-26-amd64-k8.

It seems to me that this makes Dapper unable to handle iPods at all - which is somewhat more dramatic than 'medium'. Rolling my own kernel is right now beyond my skills, and certainly those of the target Dapper user.

[Ylan (ylan-segal)]

It turns out that all my problems with the ipod had a simple explanation: The ipod's hard drive is faulty, as reported by its own diagnostics. (It just happened to coincide with me moving to dapper).

I would suggest that anyone still having problems without EFI support in their kernel try to run diagnostics on their ipod to eliminate that as a possibility.

http://www.methodshop.com/mp3/ipodsupport/diagnosticmode/

[Joachim Beckers (jbeckers)]

Mine (40GB 4th gen B/W) passed all tests. Still the same problems though.

Besides, there's other devices that experience the same problems.

Please check again when your iPod's back from repair.

[Ylan (ylan-segal)]

I took my ipod to one of the "geniuses" at the Mac store and he reformatted the hard drive.

Using the current stock dapper kernel (linux-image-2.6.15-26-686), I have succesfully used gtkpod to transfer music to the ipod (connected directly to the laptop, no hub). I no longer receive any Buffer I/O errors and everything appears to be working properly. Up to now, I have only transfered ~30 songs, so the test is limited, but I believe that in my case it was the ipod that was the problem.

[Ben Collins (ben-collins)]

All of the iPod unusual-dev entries should be present now. I'm hoping this is fixed.

[Joachim Beckers (jbeckers)]

I did a complete reset of my iPod today. First just an upgrade of the firmware (3.1 -> 3.1.1) to make sure all formatting bugs would be gone. Then a full format + fw-upgrade.

It still passes all built-in tests, but the problems with the EFI/kernel-thning persist.

So anyone who thinks of reformatting his/her iPod to make it work with dapper: think twice. ;-)

PS: Waiting for a new linux-image release. I hope this will be fixed in the next one.

[Joachim Beckers (jbeckers)]

linux-image 2.6.15-26.47 fixes this for me. others please check.

one small note: it only works the first time I plug in my iPod, the second time it doesn't get recognised. but it has always been like that before :-)

[Pontus Schönberg (pontus-schonberg)]

Ok, the last kernel version solved this problem for me too (and it even works if I unplug the iPod and plug nit back in again).

So big thanks for everybody involved. :)

[Dani Alonso (dalonso)]

Hi, I'm having again this bug with the 2.6.28-15 kernel image in Jaunty.

It's a severe bug: At first I thought it was the harddisk of the iPod failing, so I tried to reformat it. This was fatal, obviously, and rendered the harddisk to the trashcan. After getting my hands at a new harddisk, hoping to it to work I discovered it was working in windows but not in Linux for the same reason that the first one.

Fortunately, this time I did not reformat the harddisk, but began looking for other people having this issue. This is how I got here.

[Brian J. Murrell (brian-interlinx)]

And this also appears to be happening on 2.6.30-10-generic.

@Joachim: You said:

one small note: it only works the first time I plug in my iPod, the second time it doesn't get recognised. but it has always been like that before :-)

That's exactly what happened here. Got it to connect once, "eject"ed it and now it won't reconnect. If you say that it has always been like that, how'd you ever get it to connect a second time?