External HDD connecting through USB(3) errors

koenc86
Posts: 22
Joined: Sun Aug 26, 2012 1:06 pm

External HDD connecting through USB(3) errors

Post by koenc86 »

This morning I discovered my external HDD, connected to IntensePC by an USB3 port, was no longer recognized. I found this error in syslog:
Nov 4 08:32:47 Amsterdam kernel: [75998.226964] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 4 08:32:50 Amsterdam kernel: [76001.191733] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 4 08:32:53 Amsterdam kernel: [76004.156460] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 4 08:32:56 Amsterdam kernel: [76007.121217] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 4 08:32:56 Amsterdam kernel: [76007.121376] usb 6-1: USB disconnect, device number 2
Nov 4 08:32:59 Amsterdam kernel: [76010.281763] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 4 08:33:02 Amsterdam kernel: [76012.611920] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #20971522: comm sabnzbdplus: reading directory lblock 0
Nov 4 08:33:02 Amsterdam kernel: [76013.246505] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 4 08:33:05 Amsterdam kernel: [76016.211239] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 4 08:33:08 Amsterdam kernel: [76019.175991] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 4 08:33:08 Amsterdam kernel: [76019.176089] hub 6-0:1.0: unable to enumerate USB device on port 1
I connected the HDD to the other USB3 port and tried mounting it. This worked:
Nov 4 13:01:36 Amsterdam kernel: [92109.400715] usb 6-2: new SuperSpeed USB device number 7 using xhci_hcd
Nov 4 13:01:36 Amsterdam kernel: [92109.421783] scsi9 : usb-storage 6-2:1.0
Nov 4 13:01:36 Amsterdam mtp-probe: checking bus 6, device 7: "/sys/devices/pci0000:00/0000:00:1c.3/0000:03:00.0/usb6/6-2"
Nov 4 13:01:36 Amsterdam mtp-probe: bus: 6, device: 7 was not an MTP device
Nov 4 13:01:37 Amsterdam kernel: [92110.420248] scsi 9:0:0:0: Direct-Access WD Elements 1042 1007 PQ: 0 ANSI: 6
Nov 4 13:01:37 Amsterdam kernel: [92110.421748] sd 9:0:0:0: Attached scsi generic sg1 type 0
Nov 4 13:01:43 Amsterdam kernel: [92110.422964] sd 9:0:0:0: [sdb] Spinning up disk.........ready
Nov 4 13:01:43 Amsterdam kernel: [92116.441378] sd 9:0:0:0: [sdb] 1953519616 512-byte logical blocks: (1.00 TB/931 GiB)
Nov 4 13:01:43 Amsterdam kernel: [92116.441898] sd 9:0:0:0: [sdb] Write Protect is off
Nov 4 13:01:43 Amsterdam kernel: [92116.441909] sd 9:0:0:0: [sdb] Mode Sense: 47 00 10 08
Nov 4 13:01:43 Amsterdam kernel: [92116.442332] sd 9:0:0:0: [sdb] No Caching mode page present
Nov 4 13:01:43 Amsterdam kernel: [92116.442398] sd 9:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 13:01:43 Amsterdam kernel: [92116.444114] sd 9:0:0:0: [sdb] No Caching mode page present
Nov 4 13:01:43 Amsterdam kernel: [92116.444178] sd 9:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 13:01:43 Amsterdam kernel: [92116.460292] sdb: sdb1
Nov 4 13:01:43 Amsterdam kernel: [92116.462086] sd 9:0:0:0: [sdb] No Caching mode page present
Nov 4 13:01:43 Amsterdam kernel: [92116.462152] sd 9:0:0:0: [sdb] Assuming drive cache: write through
Nov 4 13:01:43 Amsterdam kernel: [92116.462214] sd 9:0:0:0: [sdb] Attached SCSI disk
Nov 4 13:01:43 Amsterdam ata_id[7692]: HDIO_GET_IDENTITY failed for '/dev/sdb': Invalid argument
Nov 4 13:02:02 Amsterdam kernel: [92135.038342] EXT4-fs (sdb1): recovery complete
Nov 4 13:02:02 Amsterdam kernel: [92135.038821] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
Just now it happened again. I found these messages in syslog:
Nov 4 15:50:49 Amsterdam kernel: [102251.047446] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #57026935: comm Plex Media Serv: reading directory lblock 0
Nov 4 15:51:21 Amsterdam kernel: [102283.336962] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #20971521: comm smbd: reading directory lblock 0
Nov 4 15:51:21 Amsterdam kernel: [102283.347098] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #20971521: comm smbd: reading directory lblock 0
Nov 4 15:52:05 Amsterdam kernel: [102327.012173] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #20971522: comm nspr-2: reading directory lblock 0
Nov 4 15:52:22 Amsterdam kernel: [102343.460141] device eth0 left promiscuous mode
Nov 4 15:53:15 Amsterdam kernel: [102396.398344] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #20971521: comm Plex Media Scan: reading directory lblock 0
Nov 4 15:53:15 Amsterdam kernel: [102396.660386] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3676: inode #57026935: block 228065975: comm Plex Media Scan: unable to read itable block
Nov 4 15:53:15 Amsterdam kernel: [102396.662205] EXT4-fs error (device sdb1) in ext4_reserve_inode_write:4494: IO failure
Nov 4 15:53:20 Amsterdam kernel: [102402.101287] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #20971522: comm sabnzbdplus: reading directory lblock 0
Nov 4 15:53:20 Amsterdam kernel: [102402.103136] EXT4-fs error (device sdb1): ext4_read_inode_bitmap:161: comm sabnzbdplus: Cannot read inode bitmap - block_group = 2800, inode_bitmap = 91750416
Nov 4 15:53:20 Amsterdam kernel: [102402.106332] EXT4-fs error (device sdb1) in ext4_new_inode:941: IO failure
Nov 4 15:53:20 Amsterdam kernel: [102402.107965] Aborting journal on device sdb1-8.
Nov 4 15:53:20 Amsterdam kernel: [102402.109135] Buffer I/O error on device sdb1, logical block 121667584
Nov 4 15:53:20 Amsterdam kernel: [102402.110582] lost page write due to I/O error on sdb1
Nov 4 15:53:20 Amsterdam kernel: [102402.110585] JBD2: I/O error detected when updating journal superblock for sdb1-8.
When now trying to connect the HDD again, it can't find the device.
mount: special device /dev/sdb1 does not exist
Syslog shows:
Nov 4 16:03:34 Amsterdam kernel: [103015.303434] EXT4-fs error (device sdb1): ext4_journal_start_sb:327: Detected aborted journal
Nov 4 16:03:34 Amsterdam kernel: [103015.307889] EXT4-fs (sdb1): Remounting filesystem read-only
Nov 4 16:03:39 Amsterdam kernel: [103020.571944] EXT4-fs error (device sdb1): ext4_find_entry:935: inode #2: comm nautilus: reading directory lblock 0
Nov 4 16:06:42 Amsterdam kernel: [103202.580126] EXT4-fs error (device sdb1): ext4_put_super:819: Couldn't clean up the journal
Could you help me figure out what is causing this issue? I hope it's not a malfunction of the USB ports but something I can fix myself.
If you need more information I'll ofcourse provide it.

Denis
Posts: 301
Joined: Sun Apr 26, 2009 3:24 pm

Re: External HDD connecting through USB(3) errors

Post by Denis »

What kernel do you use? I advice you to try Ubuntu 12.10 LiveUSB, it comes with kernel 3.5.0. I hope USB3 issues will be fixed.

If not - please help us to reproduce the problem on our side.
What docking station and HDD do you use? If you can reproduce it - what leads to the error case?
Compulab's Linux support

koenc86
Posts: 22
Joined: Sun Aug 26, 2012 1:06 pm

Re: External HDD connecting through USB(3) errors

Post by koenc86 »

Thanks for your reply Denis.
Ubuntu 12.04.1 LTS (GNU/Linux 3.2.0-32-generic x86_64)
The HDD is a "Western Digital Elements SE 1TB (USB3)"

During the first occasion, the HDD was idle (as far as I know; I wasn't using it actively since I was sleeping).
The second occassion was different. I was watching a movie on my TV. Data was streamed from the ext HDD via PlexMediaServer installed on IntensePC. But I do not know if this is related. In other occasions where I was streaming media off the HDD it worked fine.
I currently do not have an idea which specific situation may have caused an issue. I do not know how to debug this. If you have a suggestion, please let me know.

When I plug-out and then plug-in the HDD device to one of the USB3 ports now, the light indicator on the HDD starts flashing which is good.
In syslog, however, no messages are appearing anymore at all. I don't know what this means.

On a sidenote, you suggest using Ubuntu 12.10. Do you suggest upgrading my current installation from 12.04 to 12.10 (no fresh install, but upgrade) ? I think I could give this a try if I could keep all my settings etc., since I just spent a whole lot of time setting up the machine completely.

Thanks for your help.

Denis
Posts: 301
Joined: Sun Apr 26, 2009 3:24 pm

Re: External HDD connecting through USB(3) errors

Post by Denis »

Yes, you can try to upgrade to 12.10. It's safe and could be solution to your problem.
Compulab's Linux support

koenc86
Posts: 22
Joined: Sun Aug 26, 2012 1:06 pm

Re: External HDD connecting through USB(3) errors

Post by koenc86 »

Upgrading to 12.10 fixed the errors it seems. External drive is working fine now. So far, so good! :)

Thanks for the advice, Denis!

koenc86
Posts: 22
Joined: Sun Aug 26, 2012 1:06 pm

Re: External HDD connecting through USB(3) errors

Post by koenc86 »

Unfortunately this happened again on Ubuntu 12.10. The HDD wasn't in use other than rtorrent may be have reading or writing data, but I don't know how that can be related.

The following errors are the first one I found in syslog.

Any ideas? :(
Nov 13 21:21:58 Amsterdam kernel: [372191.774098] usb 6-1: reset SuperSpeed USB device number 2 using xhci_hcd
Nov 13 21:21:58 Amsterdam kernel: [372191.791270] usb 6-1: Parent hub missing LPM exit latency info. Power management will be impacted.
Nov 13 21:21:58 Amsterdam kernel: [372191.792021] xhci_hcd 0000:03:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880427e1ce00
Nov 13 21:21:58 Amsterdam kernel: [372191.792024] xhci_hcd 0000:03:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff880427e1ce40
Nov 13 21:27:24 Amsterdam kernel: [372517.120458] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 13 21:27:26 Amsterdam kernel: [372520.085225] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 13 21:27:29 Amsterdam kernel: [372523.049950] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 13 21:27:32 Amsterdam kernel: [372526.014749] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 13 21:27:32 Amsterdam kernel: [372526.014920] usb 6-1: USB disconnect, device number 2
Nov 13 21:27:32 Amsterdam kernel: [372526.018773] sd 6:0:0:0: [sdb] Unhandled error code
Nov 13 21:27:32 Amsterdam kernel: [372526.018780] sd 6:0:0:0: [sdb]
Nov 13 21:27:32 Amsterdam kernel: [372526.018783] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Nov 13 21:27:32 Amsterdam kernel: [372526.018787] sd 6:0:0:0: [sdb] CDB:
Nov 13 21:27:32 Amsterdam kernel: [372526.018790] Write(10): 2a 00 3a 05 1f 48 00 00 18 00
Nov 13 21:27:32 Amsterdam kernel: [372526.018808] end_request: I/O error, dev sdb, sector 973414216
Nov 13 21:27:32 Amsterdam kernel: [372526.018917] Buffer I/O error on device sdb1, logical block 97477244
Nov 13 21:27:32 Amsterdam kernel: [372526.018927] Aborting journal on device sdb1-8.
Nov 13 21:27:32 Amsterdam kernel: [372526.018938] EXT4-fs error (device sdb1) in ext4_reserve_inode_write:4483: Journal has aborted
Nov 13 21:27:32 Amsterdam kernel: [372526.019176] Buffer I/O error on device sdb1, logical block 97477245
Nov 13 21:27:32 Amsterdam kernel: [372526.019287] Buffer I/O error on device sdb1, logical block 97477246
Nov 13 21:27:32 Amsterdam kernel: [372526.019365] Buffer I/O error on device sdb1, logical block 97477247
<alot of similar lines>
Nov 13 21:27:32 Amsterdam kernel: [372526.058549] Buffer I/O error on device sdb1, logical block 97477315
Nov 13 21:27:32 Amsterdam kernel: [372526.059374] Buffer I/O error on device sdb1, logical block 97477316
Nov 13 21:27:32 Amsterdam kernel: [372526.060231] EXT4-fs warning (device sdb1): ext4_end_bio:250: I/O error writing to inode 24117258 (offset 246120448 size 53248 starting block 97477573)
Nov 13 21:27:32 Amsterdam kernel: [372526.060277] sd 6:0:0:0: [sdb] Unhandled error code
Nov 13 21:27:32 Amsterdam kernel: [372526.060281] sd 6:0:0:0: [sdb]
Nov 13 21:27:32 Amsterdam kernel: [372526.060285] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Nov 13 21:27:32 Amsterdam kernel: [372526.060288] sd 6:0:0:0: [sdb] CDB:
Nov 13 21:27:32 Amsterdam kernel: [372526.060290] Write(10): 2a 00 2e 75 6e 58 00 00 88 00
Nov 13 21:27:32 Amsterdam kernel: [372526.060307] end_request: I/O error, dev sdb, sector 779447896
Nov 13 21:27:32 Amsterdam kernel: [372526.060431] EXT4-fs error (device sdb1) in ext4_dirty_inode:4610: Journal has aborted
Nov 13 21:27:32 Amsterdam kernel: [372526.060433] EXT4-fs (sdb1): previous I/O error to superblock detected
Nov 13 21:27:32 Amsterdam kernel: [372526.060585] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
Nov 13 21:27:32 Amsterdam kernel: [372526.060607] EXT4-fs (sdb1): delayed block allocation failed for inode 24117278 at logical offset 7773 with max blocks 10 with error -5
Nov 13 21:27:32 Amsterdam kernel: [372526.060608] EXT4-fs (sdb1): This should not happen!! Data will be lost
Nov 13 21:27:32 Amsterdam kernel: [372526.060608]
Nov 13 21:27:32 Amsterdam kernel: [372526.060613] EXT4-fs (sdb1): previous I/O error to superblock detected
Nov 13 21:27:32 Amsterdam kernel: [372526.060620] EXT4-fs error (device sdb1): ext4_journal_start_sb:370: Detected aborted journal
Nov 13 21:27:32 Amsterdam kernel: [372526.060622] EXT4-fs (sdb1): Remounting filesystem read-only
Nov 13 21:27:32 Amsterdam kernel: [372526.060623] EXT4-fs (sdb1): previous I/O error to superblock detected
Nov 13 21:27:32 Amsterdam kernel: [372526.060624] EXT4-fs error (device sdb1) in ext4_da_writepages:2388: IO failure
Nov 13 21:27:32 Amsterdam kernel: [372526.060626] EXT4-fs (sdb1): previous I/O error to superblock detected
Nov 13 21:27:32 Amsterdam kernel: [372526.060636] EXT4-fs (sdb1): ext4_da_writepages: jbd2_start: 9223372036854775807 pages, ino 24117278; err -30
Nov 13 21:27:32 Amsterdam kernel: [372526.067557] Buffer I/O error on device sdb1, logical block 97430731
Nov 13 21:27:32 Amsterdam kernel: [372526.068867] Buffer I/O error on device sdb1, logical block 97430732
Nov 13 21:27:32 Amsterdam kernel: [372526.069421] Buffer I/O error on device sdb1, logical block 97430733
Nov 13 21:27:32 Amsterdam kernel: [372526.069973] Buffer I/O error on device sdb1, logical block 97430734
Nov 13 21:27:32 Amsterdam kernel: [372526.070526] Buffer I/O error on device sdb1, logical block 97430735
Nov 13 21:27:32 Amsterdam kernel: [372526.071086] Buffer I/O error on device sdb1, logical block 97430736
Nov 13 21:27:32 Amsterdam kernel: [372526.071640] Buffer I/O error on device sdb1, logical block 97430737
Nov 13 21:27:32 Amsterdam kernel: [372526.072192] Buffer I/O error on device sdb1, logical block 97430738
Nov 13 21:27:32 Amsterdam kernel: [372526.072744] Buffer I/O error on device sdb1, logical block 97430739
Nov 13 21:27:32 Amsterdam kernel: [372526.073293] Buffer I/O error on device sdb1, logical block 97430740
Nov 13 21:27:32 Amsterdam kernel: [372526.073842] Buffer I/O error on device sdb1, logical block 97430741
Nov 13 21:27:32 Amsterdam kernel: [372526.074391] Buffer I/O error on device sdb1, logical block 97430742
Nov 13 21:27:32 Amsterdam kernel: [372526.074974] Buffer I/O error on device sdb1, logical block 97430743
Nov 13 21:27:32 Amsterdam kernel: [372526.075528] Buffer I/O error on device sdb1, logical block 97430744
Nov 13 21:27:32 Amsterdam kernel: [372526.076078] Buffer I/O error on device sdb1, logical block 97430745
Nov 13 21:27:32 Amsterdam kernel: [372526.076630] Buffer I/O error on device sdb1, logical block 97430746
Nov 13 21:27:32 Amsterdam kernel: [372526.077179] Buffer I/O error on device sdb1, logical block 97430747
Nov 13 21:27:32 Amsterdam kernel: [372526.077730] EXT4-fs warning (device sdb1): ext4_end_bio:250: I/O error writing to inode 24117258 (offset 55357440 size 69632 starting block 97431004)
Nov 13 21:27:32 Amsterdam kernel: [372526.077731] JBD2: Detected IO errors while flushing file data on sdb1-8
Nov 13 21:27:32 Amsterdam kernel: [372526.077740] journal commit I/O error
Nov 13 21:27:36 Amsterdam kernel: [372529.199214] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 13 21:27:38 Amsterdam kernel: [372531.086307] EXT4-fs error (device sdb1): ext4_find_entry:1209: inode #20971522: comm rtorrent: reading directory lblock 0
Nov 13 21:27:38 Amsterdam kernel: [372531.088825] EXT4-fs error (device sdb1): ext4_wait_block_bitmap:447: comm rtorrent: Cannot read block bitmap - block_group = 2970, block_bitmap = 96993290
Nov 13 21:27:38 Amsterdam kernel: [372531.090815] EXT4-fs error (device sdb1): ext4_discard_preallocations:3838: comm rtorrent: Error reading block bitmap for 2970
Nov 13 21:27:38 Amsterdam kernel: [372531.093700] EXT4-fs error (device sdb1): ext4_wait_block_bitmap:447: comm rtorrent: Cannot read block bitmap - block_group = 2975, block_bitmap = 96993295
Nov 13 21:27:38 Amsterdam kernel: [372531.095853] EXT4-fs error (device sdb1): ext4_discard_preallocations:3838: comm rtorrent: Error reading block bitmap for 2975
Nov 13 21:27:38 Amsterdam kernel: [372531.099964] ------------[ cut here ]------------
Nov 13 21:27:38 Amsterdam kernel: [372531.099981] WARNING: at /build/buildd/linux-3.5.0/fs/buffer.c:618 __set_page_dirty+0xca/0xe0()
Nov 13 21:27:38 Amsterdam kernel: [372531.099985] Hardware name: Intense-PC
Nov 13 21:27:38 Amsterdam kernel: [372531.099987] Modules linked in: xt_dscp btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs vboxpci(O) vboxnetadp(O) vboxnetflt(O) vboxdrv(O) pci_stub ip6table_filter $
Nov 13 21:27:38 Amsterdam kernel: [372531.100119] Pid: 2609, comm: rtorrent Tainted: G O 3.5.0-18-generic #29-Ubuntu
Nov 13 21:27:38 Amsterdam kernel: [372531.100122] Call Trace:
Nov 13 21:27:38 Amsterdam kernel: [372531.100136] [<ffffffff81051c1f>] warn_slowpath_common+0x7f/0xc0
Nov 13 21:27:38 Amsterdam kernel: [372531.100144] [<ffffffff81051c7a>] warn_slowpath_null+0x1a/0x20
Nov 13 21:27:38 Amsterdam kernel: [372531.100151] [<ffffffff811b1d9a>] __set_page_dirty+0xca/0xe0
Nov 13 21:27:38 Amsterdam kernel: [372531.100159] [<ffffffff811b274e>] __set_page_dirty_buffers+0xce/0xf0
Nov 13 21:27:38 Amsterdam kernel: [372531.100170] [<ffffffff8112c372>] set_page_dirty+0x62/0x70
Nov 13 21:27:38 Amsterdam kernel: [372531.100179] [<ffffffff81148e08>] unmap_page_range+0x608/0x740
Nov 13 21:27:38 Amsterdam kernel: [372531.100187] [<ffffffff81148fcb>] unmap_single_vma+0x8b/0xd0
Nov 13 21:27:38 Amsterdam kernel: [372531.100195] [<ffffffff811497e2>] unmap_vmas+0x52/0xa0
Nov 13 21:27:38 Amsterdam kernel: [372531.100203] [<ffffffff8114e0d4>] unmap_region+0xa4/0x120
Nov 13 21:27:38 Amsterdam kernel: [372531.100209] [<ffffffff8114fcf6>] do_munmap+0x2b6/0x410
Nov 13 21:27:38 Amsterdam kernel: [372531.100214] [<ffffffff8114fe9e>] vm_munmap+0x4e/0x70
Nov 13 21:27:38 Amsterdam kernel: [372531.100220] [<ffffffff81150ccb>] sys_munmap+0x2b/0x40
Nov 13 21:27:38 Amsterdam kernel: [372531.100231] [<ffffffff8168b629>] system_call_fastpath+0x16/0x1b
Nov 13 21:27:38 Amsterdam kernel: [372531.100235] ---[ end trace 028f3d8f979384d4 ]---
Nov 13 21:27:38 Amsterdam kernel: [372531.100869] EXT4-fs error (device sdb1): ext4_wait_block_bitmap:447: comm rtorrent: Cannot read block bitmap - block_group = 2964, block_bitmap = 96993284
Nov 13 21:27:38 Amsterdam kernel: [372531.103301] EXT4-fs error (device sdb1): ext4_discard_preallocations:3838: comm rtorrent: Error reading block bitmap for 2964
Nov 13 21:27:39 Amsterdam kernel: [372532.163954] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 13 21:27:42 Amsterdam kernel: [372535.128753] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 13 21:27:45 Amsterdam kernel: [372538.093445] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
Nov 13 21:27:45 Amsterdam kernel: [372538.095920] hub 6-0:1.0: unable to enumerate USB device on port 1

gabrielh
Site Admin
Posts: 1260
Joined: Thu Jun 02, 2011 1:13 pm

Re: External HDD connecting through USB(3) errors

Post by gabrielh »

New BIOS revision for the IntensePC will be released soon. In the upcoming revision was implemented fixes regarding an USB3 performance. Please apply the new BIOS upon it's release and check if the issue will be gone
Gabriel Heifets

Fit-PC2/3/IntensePC support.

koenc86
Posts: 22
Joined: Sun Aug 26, 2012 1:06 pm

Re: External HDD connecting through USB(3) errors

Post by koenc86 »

Thank you for your reply Gabriel. Please let me know when it's released.

Thanks.

gabrielh
Site Admin
Posts: 1260
Joined: Thu Jun 02, 2011 1:13 pm

Re: External HDD connecting through USB(3) errors

Post by gabrielh »

It's my pleasure.
Gabriel Heifets

Fit-PC2/3/IntensePC support.

koenc86
Posts: 22
Joined: Sun Aug 26, 2012 1:06 pm

Re: External HDD connecting through USB(3) errors

Post by koenc86 »

I noticed that these USB-outages with my HDD also happen on USB2 ports, so not only USB3.

Don't know if this changes the situation?

Nov 25 16:23:26 Amsterdam kernel: [15708.826191] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:26 Amsterdam kernel: [15708.838159] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:29 Amsterdam kernel: [15711.802973] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:32 Amsterdam kernel: [15714.767675] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:35 Amsterdam kernel: [15717.732424] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:35 Amsterdam kernel: [15717.732580] usb 6-2: USB disconnect, device number 2
Nov 25 16:23:35 Amsterdam kernel: [15717.740360] sd 8:0:0:0: [sdb] Unhandled error code
Nov 25 16:23:35 Amsterdam kernel: [15717.740368] sd 8:0:0:0: [sdb]
Nov 25 16:23:35 Amsterdam kernel: [15717.740372] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Nov 25 16:23:35 Amsterdam kernel: [15717.740377] sd 8:0:0:0: [sdb] CDB:
Nov 25 16:23:35 Amsterdam kernel: [15717.740380] Read(10): 28 00 18 b4 4b 80 00 00 f0 00
Nov 25 16:23:35 Amsterdam kernel: [15717.740399] end_request: I/O error, dev sdb, sector 414468992
Nov 25 16:23:35 Amsterdam kernel: [15717.740520] sd 8:0:0:0: [sdb] Unhandled error code
Nov 25 16:23:35 Amsterdam kernel: [15717.740525] sd 8:0:0:0: [sdb]
Nov 25 16:23:35 Amsterdam kernel: [15717.740528] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Nov 25 16:23:35 Amsterdam kernel: [15717.740532] sd 8:0:0:0: [sdb] CDB:
Nov 25 16:23:35 Amsterdam kernel: [15717.740535] Read(10): 28 00 18 b4 4c 70 00 00 10 00
Nov 25 16:23:35 Amsterdam kernel: [15717.740552] end_request: I/O error, dev sdb, sector 414469232
Nov 25 16:23:38 Amsterdam kernel: [15721.240590] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:41 Amsterdam kernel: [15724.205345] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:44 Amsterdam kernel: [15727.170112] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:47 Amsterdam kernel: [15730.134838] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Nov 25 16:23:47 Amsterdam kernel: [15730.134944] hub 6-0:1.0: unable to enumerate USB device on port 2

Post Reply

Return to “Storage”