EXT4 partition gets disconnected while using rtorrent


9 posts
by gabello » Tue Nov 06, 2012 11:00 pm
Hello, I have an external USB HDD that I recently formatted to EXT4. this HDD is connected via a powered hub and previously had a NTFS file system. I'm using rtorrent to download on this hdd and (after I did the switch to ext4) quite often the HDD gets disconnected (hence rtorrent crashes) and I have to remount it.

The relevant content of the dmseg can be seen below:

Code: Select all
[317211.217423] wlan0: No basic rates in AssocResp. Using min supported rate instead.
[324920.877001] ieee80211 phy0: wlan0: No probe response from AP f8:d1:11:b7:de:2c after 500ms, disconnecting.
[324920.903592] cfg80211: Calling CRDA to update world regulatory domain
[324922.230940] wlan0: authenticate with f8:d1:11:b7:de:2c (try 1)
[324922.233325] wlan0: authenticated
[324922.255323] wlan0: associate with f8:d1:11:b7:de:2c (try 1)
[324922.258298] wlan0: RX ReassocResp from f8:d1:11:b7:de:2c (capab=0x431 status=0 aid=1)
[324922.258329] wlan0: associated
[324922.258354] wlan0: No basic rates in AssocResp. Using min supported rate instead.
[333926.834244] ieee80211 phy0: wlan0: No probe response from AP f8:d1:11:b7:de:2c after 500ms, disconnecting.
[333926.861008] cfg80211: Calling CRDA to update world regulatory domain
[333928.187751] wlan0: authenticate with f8:d1:11:b7:de:2c (try 1)
[333928.189840] wlan0: authenticated
[333928.212250] wlan0: associate with f8:d1:11:b7:de:2c (try 1)
[333928.215202] wlan0: RX ReassocResp from f8:d1:11:b7:de:2c (capab=0x431 status=0 aid=1)
[333928.215233] wlan0: associated
[333928.215257] wlan0: No basic rates in AssocResp. Using min supported rate instead.
[350923.916712] ieee80211 phy0: wlan0: No probe response from AP f8:d1:11:b7:de:2c after 500ms, disconnecting.
[350923.943610] cfg80211: Calling CRDA for country: RO
[350925.270226] wlan0: authenticate with f8:d1:11:b7:de:2c (try 1)
[350925.272762] wlan0: authenticated
[350925.294846] wlan0: associate with f8:d1:11:b7:de:2c (try 1)
[350925.297761] wlan0: RX ReassocResp from f8:d1:11:b7:de:2c (capab=0x431 status=0 aid=1)
[350925.297789] wlan0: associated
[350925.297813] wlan0: No basic rates in AssocResp. Using min supported rate instead.
[353674.395707] sd 0:0:0:0: Device offlined - not ready after error recovery
[353674.395875] sd 0:0:0:0: [sda] Unhandled error code
[353674.395896] sd 0:0:0:0: [sda]  Result: hostbyte=0x05 driverbyte=0x00
[353674.395957] sd 0:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 05 1b 6b 17 00 00 58 00
[353674.396003] end_request: I/O error, dev sda, sector 85682967
[353674.396118] EXT4-fs (sda1): delayed block allocation failed for inode 1835027 at logical offset 154974 with max blocks 8 with error -5
[353674.417234] EXT4-fs (sda1): This should not happen!! Data will be lost
[353674.417257]
[353674.442864] usb 1-1.2.3: USB disconnect, device number 6
[353674.446956] JBD2: Detected IO errors while flushing file data on sda1-8
[353674.447058] Aborting journal on device sda1-8.
[353674.447129] JBD2: I/O error detected when updating journal superblock for sda1-8.
[353674.447584] EXT4-fs error (device sda1): ext4_journal_start_sb:327:
[353674.454916] EXT4-fs (sda1): previous I/O error to superblock detected
[353674.464242] Detected aborted journal
[353674.464328] EXT4-fs (sda1): Remounting filesystem read-only
[353674.479035] EXT4-fs error (device sda1): ext4_journal_start_sb:327: Detected aborted journal
[353674.496953] EXT4-fs (sda1): previous I/O error to superblock detected
[353674.528874] EXT4-fs (sda1): ext4_da_writepages: jbd2_start: 7762 pages, ino 1835027; err -30
[353674.693212] ------------[ cut here ]------------
[353674.693286] WARNING: at fs/buffer.c:668 __set_page_dirty+0xbc/0xd8()
[353674.693300] Modules linked in: aes_generic snd_bcm2835 snd_pcm snd_seq snd_timer snd_seq_device snd snd_page_alloc arc4 rt73usb rt2x00usb rt2x00lib mac80211 cfg80211
[353674.693422] [<c0013e1c>] (unwind_backtrace+0x0/0xf0) from [<c0028b24>] (warn_slowpath_common+0x4c/0x64)
[353674.693460] [<c0028b24>] (warn_slowpath_common+0x4c/0x64) from [<c0028b58>] (warn_slowpath_null+0x1c/0x24)
[353674.693494] [<c0028b58>] (warn_slowpath_null+0x1c/0x24) from [<c00e0810>] (__set_page_dirty+0xbc/0xd8)
[353674.693529] [<c00e0810>] (__set_page_dirty+0xbc/0xd8) from [<c00e0928>] (__set_page_dirty_buffers+0xfc/0x124)
[353674.693578] [<c00e0928>] (__set_page_dirty_buffers+0xfc/0x124) from [<c0091490>] (set_page_dirty+0x8c/0xa8)
[353674.693630] [<c0091490>] (set_page_dirty+0x8c/0xa8) from [<c00a30d0>] (unmap_vmas+0x438/0x5ec)
[353674.693666] [<c00a30d0>] (unmap_vmas+0x438/0x5ec) from [<c00a8964>] (exit_mmap+0x100/0x268)
[353674.693703] [<c00a8964>] (exit_mmap+0x100/0x268) from [<c00267b0>] (mmput+0x34/0x110)
[353674.693736] [<c00267b0>] (mmput+0x34/0x110) from [<c002aa08>] (exit_mm+0x130/0x150)
[353674.693765] [<c002aa08>] (exit_mm+0x130/0x150) from [<c002c778>] (do_exit+0x52c/0x704)
[353674.693795] [<c002c778>] (do_exit+0x52c/0x704) from [<c002cbf0>] (do_group_exit+0x3c/0xc4)
[353674.693830] [<c002cbf0>] (do_group_exit+0x3c/0xc4) from [<c0037a44>] (get_signal_to_deliver+0x158/0x56c)
[353674.693879] [<c0037a44>] (get_signal_to_deliver+0x158/0x56c) from [<c00103e4>] (do_signal+0x64/0x544)
[353674.693915] [<c00103e4>] (do_signal+0x64/0x544) from [<c0010e84>] (do_notify_resume+0x5c/0x68)
[353674.693947] [<c0010e84>] (do_notify_resume+0x5c/0x68) from [<c000d9d8>] (work_pending+0x24/0x28)
[353674.693966] ---[ end trace 67cbc78d8b934ac5 ]---
[353674.703327] EXT4-fs error (device sda1): ext4_discard_preallocations:3885: comm rtorrent: Error loading buddy information for 322
[353674.746222] EXT4-fs error (device sda1): ext4_discard_preallocations:3885: comm rtorrent: Error loading buddy information for 327
[353674.804693] usb 1-1.2.3: new high-speed USB device number 7 using dwc_otg
[353674.905899] usb 1-1.2.3: New USB device found, idVendor=152d, idProduct=2329
[353674.905933] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[353674.905951] usb 1-1.2.3: Product: USB to ATA/ATAPI Bridge
[353674.905965] usb 1-1.2.3: Manufacturer: JMicron
[353674.905977] usb 1-1.2.3: SerialNumber: 091008B20013
[353674.911306] usb-storage 1-1.2.3:1.0: Quirks match for vid 152d pid 2329: 8020
[353674.911507] scsi1 : usb-storage 1-1.2.3:1.0
[353675.946981] scsi 1:0:0:0: Direct-Access     Hitachi  HTS545025B9A300       PQ: 0 ANSI: 2 CCS
[353676.022137] sd 1:0:0:0: [sdb] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[353676.023227] sd 1:0:0:0: [sdb] Write Protect is off
[353676.023258] sd 1:0:0:0: [sdb] Mode Sense: 34 00 00 00
[353676.025294] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[353676.056798]  sdb: sdb1
[353676.060620] sd 1:0:0:0: [sdb] Attached SCSI disk
[353846.167907] EXT4-fs error (device sda1): ext4_find_entry:935: inode #1835009: comm rtorrent: reading directory lblock 0
[353887.571953] EXT4-fs (sdb1): recovery complete
[353887.573403] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[354001.908736] Buffer I/O error on device sda1, logical block 10622049
[354001.908761] lost page write due to I/O error on sda1
[354177.488549] Buffer I/O error on device sda1, logical block 10710374
[354177.488575] lost page write due to I/O error on sda1
[354177.488640] Buffer I/O error on device sda1, logical block 10710606
[354177.488656] lost page write due to I/O error on sda1
[354177.488702] Buffer I/O error on device sda1, logical block 10710710
[354177.488718] lost page write due to I/O error on sda1
[354187.028834] Buffer I/O error on device sda1, logical block 10708262
[354187.028860] lost page write due to I/O error on sda1
[354204.795591] Buffer I/O error on device sda1, logical block 10712670
[354204.795618] lost page write due to I/O error on sda1
[354488.398835] sd 1:0:0:0: Device offlined - not ready after error recovery
[354488.398896] sd 1:0:0:0: [sdb] Unhandled error code
[354488.398910] sd 1:0:0:0: [sdb]  Result: hostbyte=0x05 driverbyte=0x00
[354488.398931] sd 1:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 05 15 a6 3f 00 00 10 00
[354488.398973] end_request: I/O error, dev sdb, sector 85304895
[354488.399070] Buffer I/O error on device sdb1, logical block 10663104
[354488.399104] Buffer I/O error on device sdb1, logical block 10663105
[354488.399131] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 441188352 size 8192 starting block 10663113)
[354488.399183] sd 1:0:0:0: rejecting I/O to offline device
[354488.399205] sd 1:0:0:0: [sdb] killing request
[354488.399243] sd 1:0:0:0: rejecting I/O to offline device
[354488.399271] Buffer I/O error on device sdb1, logical block 10663715
[354488.399293] Buffer I/O error on device sdb1, logical block 10663716
[354488.399312] Buffer I/O error on device sdb1, logical block 10663717
[354488.399329] Buffer I/O error on device sdb1, logical block 10663718
[354488.399353] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 443691008 size 16384 starting block 10663726)
[354488.399388] sd 1:0:0:0: rejecting I/O to offline device
[354488.399411] Buffer I/O error on device sdb1, logical block 10663767
[354488.399431] Buffer I/O error on device sdb1, logical block 10663768
[354488.399450] Buffer I/O error on device sdb1, logical block 10663769
[354488.399468] Buffer I/O error on device sdb1, logical block 10663770
[354488.399487] Buffer I/O error on device sdb1, logical block 10663771
[354488.399505] Buffer I/O error on device sdb1, logical block 10663772
[354488.399522] Buffer I/O error on device sdb1, logical block 10663773
[354488.399540] Buffer I/O error on device sdb1, logical block 10663774
[354488.399557] Buffer I/O error on device sdb1, logical block 10663775
[354488.399574] Buffer I/O error on device sdb1, logical block 10663776
[354488.399592] Buffer I/O error on device sdb1, logical block 10663777
[354488.399610] Buffer I/O error on device sdb1, logical block 10663778
[354488.399628] Buffer I/O error on device sdb1, logical block 10663779
[354488.399646] Buffer I/O error on device sdb1, logical block 10663780
[354488.399669] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 443904000 size 57344 starting block 10663788)
[354488.399699] sd 1:0:0:0: rejecting I/O to offline device
[354488.399723] Buffer I/O error on device sdb1, logical block 10663971
[354488.399744] Buffer I/O error on device sdb1, logical block 10663972
[354488.399767] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 444739584 size 8192 starting block 10663980)
[354488.399796] sd 1:0:0:0: rejecting I/O to offline device
[354488.399821] Buffer I/O error on device sdb1, logical block 10664403
[354488.399842] Buffer I/O error on device sdb1, logical block 10664404
[354488.399861] Buffer I/O error on device sdb1, logical block 10664405
[354488.399879] Buffer I/O error on device sdb1, logical block 10664406
[354488.399897] Buffer I/O error on device sdb1, logical block 10664407
[354488.399914] Buffer I/O error on device sdb1, logical block 10664408
[354488.399932] Buffer I/O error on device sdb1, logical block 10664409
[354488.399950] Buffer I/O error on device sdb1, logical block 10664410
[354488.399967] Buffer I/O error on device sdb1, logical block 10664411
[354488.399986] Buffer I/O error on device sdb1, logical block 10664412
[354488.400004] Buffer I/O error on device sdb1, logical block 10664413
[354488.400021] Buffer I/O error on device sdb1, logical block 10664414
[354488.400039] Buffer I/O error on device sdb1, logical block 10664415
[354488.400056] Buffer I/O error on device sdb1, logical block 10664416
[354488.400073] Buffer I/O error on device sdb1, logical block 10664417
[354488.400090] Buffer I/O error on device sdb1, logical block 10664418
[354488.400108] Buffer I/O error on device sdb1, logical block 10664419
[354488.400125] Buffer I/O error on device sdb1, logical block 10664420
[354488.400143] Buffer I/O error on device sdb1, logical block 10664421
[354488.400161] Buffer I/O error on device sdb1, logical block 10664422
[354488.400179] Buffer I/O error on device sdb1, logical block 10664423
[354488.400196] Buffer I/O error on device sdb1, logical block 10664424
[354488.400214] Buffer I/O error on device sdb1, logical block 10664425
[354488.400232] Buffer I/O error on device sdb1, logical block 10664426
[354488.400250] Buffer I/O error on device sdb1, logical block 10664427
[354488.400267] Buffer I/O error on device sdb1, logical block 10664428
[354488.400284] Buffer I/O error on device sdb1, logical block 10664429
[354488.400301] Buffer I/O error on device sdb1, logical block 10664430
[354488.400318] Buffer I/O error on device sdb1, logical block 10664431
[354488.400335] Buffer I/O error on device sdb1, logical block 10664432
[354488.400358] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 446509056 size 126976 starting block 10664440)
[354488.400389] sd 1:0:0:0: rejecting I/O to offline device
[354488.400412] Buffer I/O error on device sdb1, logical block 10664433
[354488.400432] Buffer I/O error on device sdb1, logical block 10664434
[354488.400451] Buffer I/O error on device sdb1, logical block 10664435
[354488.400468] Buffer I/O error on device sdb1, logical block 10664436
[354488.400487] Buffer I/O error on device sdb1, logical block 10664437
[354488.400504] Buffer I/O error on device sdb1, logical block 10664438
[354488.400522] Buffer I/O error on device sdb1, logical block 10664439
[354488.400539] Buffer I/O error on device sdb1, logical block 10664440
[354488.400556] Buffer I/O error on device sdb1, logical block 10664441
[354488.400573] Buffer I/O error on device sdb1, logical block 10664442
[354488.400591] Buffer I/O error on device sdb1, logical block 10664443
[354488.400610] Buffer I/O error on device sdb1, logical block 10664444
[354488.400627] Buffer I/O error on device sdb1, logical block 10664445
[354488.400644] Buffer I/O error on device sdb1, logical block 10664446
[354488.400667] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 446631936 size 57344 starting block 10664454)
[354488.400697] sd 1:0:0:0: rejecting I/O to offline device
[354488.400721] Buffer I/O error on device sdb1, logical block 10665470
[354488.400741] Buffer I/O error on device sdb1, logical block 10665471
[354488.400759] Buffer I/O error on device sdb1, logical block 10665472
[354488.400776] Buffer I/O error on device sdb1, logical block 10665473
[354488.400793] Buffer I/O error on device sdb1, logical block 10665474
[354488.400810] Buffer I/O error on device sdb1, logical block 10665475
[354488.400827] Buffer I/O error on device sdb1, logical block 10665476
[354488.400843] Buffer I/O error on device sdb1, logical block 10665477
[354488.400862] Buffer I/O error on device sdb1, logical block 10665478
[354488.400879] Buffer I/O error on device sdb1, logical block 10665479
[354488.400896] Buffer I/O error on device sdb1, logical block 10665480
[354488.400912] Buffer I/O error on device sdb1, logical block 10665481
[354488.400930] Buffer I/O error on device sdb1, logical block 10665482
[354488.400947] Buffer I/O error on device sdb1, logical block 10665483
[354488.400965] Buffer I/O error on device sdb1, logical block 10665484
[354488.400983] Buffer I/O error on device sdb1, logical block 10665485
[354488.401005] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 450879488 size 65536 starting block 10665493)
[354488.401035] sd 1:0:0:0: rejecting I/O to offline device
[354488.401058] Buffer I/O error on device sdb1, logical block 10665549
[354488.401077] Buffer I/O error on device sdb1, logical block 10665550
[354488.401095] Buffer I/O error on device sdb1, logical block 10665551
[354488.401113] Buffer I/O error on device sdb1, logical block 10665552
[354488.401130] Buffer I/O error on device sdb1, logical block 10665553
[354488.401147] Buffer I/O error on device sdb1, logical block 10665554
[354488.401164] Buffer I/O error on device sdb1, logical block 10665555
[354488.401181] Buffer I/O error on device sdb1, logical block 10665556
[354488.401197] Buffer I/O error on device sdb1, logical block 10665557
[354488.401214] Buffer I/O error on device sdb1, logical block 10665558
[354488.401232] Buffer I/O error on device sdb1, logical block 10665559
[354488.401250] Buffer I/O error on device sdb1, logical block 10665560
[354488.401267] Buffer I/O error on device sdb1, logical block 10665561
[354488.401284] Buffer I/O error on device sdb1, logical block 10665562
[354488.401306] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 451203072 size 57344 starting block 10665570)
[354488.401335] sd 1:0:0:0: rejecting I/O to offline device
[354488.401385] sd 1:0:0:0: rejecting I/O to offline device
[354488.401429] sd 1:0:0:0: rejecting I/O to offline device
[354488.401512] EXT4-fs (sdb1): delayed block allocation failed for inode 1835027 at logical offset 110354 with max blocks 3 with error -5
[354488.423185] sd 1:0:0:0: [sdb] Unhandled error code
[354488.423217] sd 1:0:0:0: [sdb]  Result: hostbyte=0x01 driverbyte=0x00
[354488.423242] sd 1:0:0:0: [sdb] CDB: cdb[0]=0x2a: 2a 00 05 15 ab 27 00 00 30 00
[354488.423289] end_request: I/O error, dev sdb, sector 85306151
[354488.423318] Buffer I/O error on device sdb1, logical block 10663261
[354488.423350] Buffer I/O error on device sdb1, logical block 10663262
[354488.423370] Buffer I/O error on device sdb1, logical block 10663263
[354488.423388] Buffer I/O error on device sdb1, logical block 10663264
[354488.423405] Buffer I/O error on device sdb1, logical block 10663265
[354488.423423] Buffer I/O error on device sdb1, logical block 10663266
[354488.423450] EXT4-fs warning (device sdb1): ext4_end_bio:251: I/O error writing to inode 1835027 (offset 441831424 size 24576 starting block 10663274)
[354488.425266] sd 1:0:0:0: rejecting I/O to offline device
[354488.426259] EXT4-fs (sdb1): This should not happen!! Data will be lost
[354488.426273]
[354488.454438] usb 1-1.2.3: USB disconnect, device number 7
[354488.462476] JBD2: Detected IO errors while flushing file data on sdb1-8
[354488.462582] Aborting journal on device sdb1-8.
[354488.462653] JBD2: I/O error detected when updating journal superblock for sdb1-8.
[354488.464254] EXT4-fs error (device sdb1): ext4_journal_start_sb:327:
[354488.474046] EXT4-fs (sdb1): previous I/O error to superblock detected
[354488.483831] Detected aborted journal
[354488.483872] EXT4-fs (sdb1): Remounting filesystem read-only
[354488.499699] EXT4-fs error (device sdb1): ext4_journal_start_sb:327: Detected aborted journal
[354488.519903] EXT4-fs (sdb1): previous I/O error to superblock detected
[354488.520283] EXT4-fs (sdb1): ext4_da_writepages: jbd2_start: 8051 pages, ino 1835027; err -30
[354488.797635] usb 1-1.2.3: new high-speed USB device number 8 using dwc_otg
[354488.899442] usb 1-1.2.3: New USB device found, idVendor=152d, idProduct=2329
[354488.899504] usb 1-1.2.3: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[354488.899568] usb 1-1.2.3: Product: USB to ATA/ATAPI Bridge
[354488.899586] usb 1-1.2.3: Manufacturer: JMicron
[354488.899599] usb 1-1.2.3: SerialNumber: 091008B20013
[354488.906771] usb-storage 1-1.2.3:1.0: Quirks match for vid 152d pid 2329: 8020
[354488.909995] scsi2 : usb-storage 1-1.2.3:1.0
[354489.950091] scsi 2:0:0:0: Direct-Access     Hitachi  HTS545025B9A300       PQ: 0 ANSI: 2 CCS
[354490.026625] sd 2:0:0:0: [sdc] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[354490.028119] sd 2:0:0:0: [sdc] Write Protect is off
[354490.028154] sd 2:0:0:0: [sdc] Mode Sense: 34 00 00 00
[354490.028954] sd 2:0:0:0: [sdc] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[354490.057662]  sdc: sdc1
[354490.061486] sd 2:0:0:0: [sdc] Attached SCSI disk




I know that there were/are several USB related issues, but i wonder why this did not manifest when I was using NTFS and if the USB issues are indeed linked to this behavior.


pi@raspberrypi /media/LG_EXT_HDD/torrent $ uname -a
Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux
Posts: 44
Joined: Sun Aug 05, 2012 8:02 pm
by jojopi » Wed Nov 07, 2012 1:33 pm
Although it not always clear from the order of the messages, the fundamental issue here is a USB problem that makes the drive disconnect and reconnect with a new device number:
[353674.442864] usb 1-1.2.3: USB disconnect, device number 6
[353674.804693] usb 1-1.2.3: new high-speed USB device number 7 using dwc_otg
[354488.454438] usb 1-1.2.3: USB disconnect, device number 7
[354488.797635] usb 1-1.2.3: new high-speed USB device number 8 using dwc_otg
Each time this happens, the corresponding sdX device stops working and a new one is created:
[353674.395707] sd 0:0:0:0: Device offlined - not ready after error recovery
[353674.395875] sd 0:0:0:0: [sda] Unhandled error code
[353676.060620] sd 1:0:0:0: [sdb] Attached SCSI disk
[354488.398835] sd 1:0:0:0: Device offlined - not ready after error recovery
[354488.398896] sd 1:0:0:0: [sdb] Unhandled error code
[354490.061486] sd 2:0:0:0: [sdc] Attached SCSI disk
The filesystem errors are just a symptom of the fact that the underlying device stops responding.

Do you get the same problem if you use wired ethernet instead of wifi?
User avatar
Posts: 1873
Joined: Tue Oct 11, 2011 8:38 pm
by gabello » Wed Nov 07, 2012 2:36 pm
Thanks for the reply, I suspected this was the case.
I can not test this with eth, since I can't really bring a cable to the Pi (also, I've disabled the eth interface using instructions from here: www.raspberrypi.org/phpBB3/viewtopic.php?f=28&t=8670).
I presume that there is no way to reduce the occurrences of this error so I stand in line for the USB fixes. To be honest the wi-fi usb dongles behaves much better than compared to a few months ago so probably they are on the right track.
Posts: 44
Joined: Sun Aug 05, 2012 8:02 pm
by scoot76 » Wed Dec 12, 2012 7:07 pm
Hi,

I'm getting the same issue though mine is just an external drive set up with samba,
Code: Select all
[373237.687288] usb-storage 1-1.2:1.0: Quirks match for vid 14cd pid 6600: 20
[373237.687923] scsi5896 : usb-storage 1-1.2:1.0
[373259.942218] usb 1-1.2: reset high-speed USB device number 72 using dwc_otg
[373270.122470] usb 1-1.2: reset high-speed USB device number 72 using dwc_otg
[373272.003076] scsi 5896:0:0:0: Device offlined - not ready after error recovery
[373272.004077] usb 1-1.2: USB disconnect, device number 72
[373272.652646] usb 1-1.2: new high-speed USB device number 73 using dwc_otg
[373272.754104] usb 1-1.2: New USB device found, idVendor=14cd, idProduct=6600
[373272.754133] usb 1-1.2: New USB device strings: Mfr=1, Product=3, SerialNumber=2


Any ideas? I've already checked hdd with badblocks and it seems to in full working order.

Thanks

Scoot
Posts: 13
Joined: Mon Aug 06, 2012 7:44 pm
by scoot76 » Wed Dec 12, 2012 7:08 pm
Sorry, forgot to mention it's wired and I formatted it to ext4 as well
Posts: 13
Joined: Mon Aug 06, 2012 7:44 pm
by fieldsem » Fri Mar 15, 2013 3:18 pm
I'm having the same issue, USB drive continually resetting. (unrelated to rtorrent.)
This seems to be a common error: a google search for "raspberry pi Device offlined - not ready after error recovery" turned up several hits. They all seem to involve:
1. External USB drive
2. Powered USB hub
Have you had any further progress? Please post any update, thanks.
- matt f
Posts: 1
Joined: Fri Mar 15, 2013 3:04 pm
by scoot76 » Fri Mar 15, 2013 7:21 pm
I tested the hard drive with seatools extended tests both in my pc and in the usb caddy and no fault, so the only thing I can think of is that it's an issue either with the pi or just a compatibility issue with the caddy
Posts: 13
Joined: Mon Aug 06, 2012 7:44 pm
by chad » Fri Mar 15, 2013 9:33 pm
Are you auto mounting the drives? I've had similar issues in the past whilst trying to use MiniDLNA and found the simple solution was to use fstab to mount the drive with it's UUID to a specific location. When the Pi tries to connect to the drive again it's at the same address and picks up where it left off without affecting playback.
Posts: 2
Joined: Mon Jun 11, 2012 3:43 pm
by scoot76 » Sat Mar 16, 2013 9:12 am
so use uuid instead of /dev entry? interesting, the only thing I was using was samba as I planned to use it as web serving drive, might give that a try then
Posts: 13
Joined: Mon Aug 06, 2012 7:44 pm