External HDD connecting through USB(3) errors

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

Re: External HDD connecting through USB(3) errors

Post by koenc86 »

I'm suspecting that this might not only be a Intense-PC issue, but something in the kernel. Is that possible?

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

Re: External HDD connecting through USB(3) errors

Post by gabrielh »

We are still in the middle of the QA tests of the new BIOS release. Ones there will be a final release, we will be able to more accurately isolate the problem.
Gabriel Heifets

Fit-PC2/3/IntensePC support.

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

Re: External HDD connecting through USB(3) errors

Post by gabrielh »

A new BIOS version for Intense has been released.

Please check it to see if you have the mentioned above issues with the new BIOS version.
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 »

Thanks for the notification, gabrielh!

Can you clarify - as the readme doesn't state this clearly - whether Intense-PC should be restarted and booted (change bootorder) from the USB flashdrive?
Or should the USB flashdrive be booted while the operating system, in my case Ubuntu, is running?

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

Re: External HDD connecting through USB(3) errors

Post by gabrielh »

You should change the boot order to boot from the USB drive.
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 »

Way to go spambots! Pity it ain't even on-topic. They could do better!

Either way. I updated the BIOS, thanks for the info gabrielh!

Unfortunately soon enough today the HDD errored on the USB3 port. I connected it to the USB2 port again, that works fine.

Attached are the error messages, similar to the previous ones.
Jan 5 14:32:14 Amsterdam kernel: [83642.122230] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Jan 5 14:32:17 Amsterdam kernel: [83645.086922] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Jan 5 14:32:20 Amsterdam kernel: [83648.051709] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Jan 5 14:32:23 Amsterdam kernel: [83651.016434] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Jan 5 14:32:23 Amsterdam kernel: [83651.016594] usb 6-2: USB disconnect, device number 2
Jan 5 14:32:23 Amsterdam kernel: [83651.024456] sd 8:0:0:0: [sdb] Unhandled error code
Jan 5 14:32:23 Amsterdam kernel: [83651.024474] sd 8:0:0:0: [sdb]
Jan 5 14:32:23 Amsterdam kernel: [83651.024478] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jan 5 14:32:23 Amsterdam kernel: [83651.024482] sd 8:0:0:0: [sdb] CDB:
Jan 5 14:32:23 Amsterdam kernel: [83651.024485] Write(10): 2a 00 3a 06 e1 08 00 00 10 00
Jan 5 14:32:23 Amsterdam kernel: [83651.024504] end_request: I/O error, dev sdb, sector 973529352
Jan 5 14:32:23 Amsterdam kernel: [83651.024639] sd 8:0:0:0: [sdb] Unhandled error code
Jan 5 14:32:23 Amsterdam kernel: [83651.024645] sd 8:0:0:0: [sdb]
Jan 5 14:32:23 Amsterdam kernel: [83651.024660] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jan 5 14:32:23 Amsterdam kernel: [83651.024664] sd 8:0:0:0: [sdb] CDB:
Jan 5 14:32:23 Amsterdam kernel: [83651.024666] Write(10): 2a 00 48 4f cd 40 00 00 60 00
Jan 5 14:32:23 Amsterdam kernel: [83651.024681] end_request: I/O error, dev sdb, sector 1213189440
Jan 5 14:32:23 Amsterdam kernel: [83651.024687] Aborting journal on device sdb1-8.
Jan 5 14:32:23 Amsterdam kernel: [83651.024722] JBD2: Error -5 detected when updating journal superblock for sdb1-8.
Jan 5 14:32:23 Amsterdam kernel: [83651.024730] EXT4-fs error (device sdb1) in ext4_da_writepages:2388: IO failure
Jan 5 14:32:23 Amsterdam kernel: [83651.024764] Buffer I/O error on device sdb1, logical block 146840479
Jan 5 14:32:23 Amsterdam kernel: [83651.024771] Buffer I/O error on device sdb1, logical block 146840480
Jan 5 14:32:23 Amsterdam kernel: [83651.024774] Buffer I/O error on device sdb1, logical block 146840481
Jan 5 14:32:23 Amsterdam kernel: [83651.024777] Buffer I/O error on device sdb1, logical block 146840482
Jan 5 14:32:23 Amsterdam kernel: [83651.024788] EXT4-fs warning (device sdb1): ext4_end_bio:250: I/O error writing to inode 29622301 (offset 2461659136 size 16384 starting block 146840739)
Jan 5 14:32:23 Amsterdam kernel: [83651.024809] EXT4-fs error (device sdb1) in ext4_reserve_inode_write:4483: Journal has aborted
Jan 5 14:32:23 Amsterdam kernel: [83651.024812] EXT4-fs (sdb1): previous I/O error to superblock detected
Jan 5 14:32:23 Amsterdam kernel: [83651.024815] EXT4-fs (sdb1): previous I/O error to superblock detected
Jan 5 14:32:23 Amsterdam kernel: [83651.024851] EXT4-fs error (device sdb1): ext4_journal_start_sb:371: Detected aborted journal
Jan 5 14:32:23 Amsterdam kernel: [83651.024856] EXT4-fs (sdb1): Remounting filesystem read-only
Jan 5 14:32:23 Amsterdam kernel: [83651.024859] EXT4-fs (sdb1): previous I/O error to superblock detected
Jan 5 14:32:23 Amsterdam kernel: [83651.024882] EXT4-fs (sdb1): ext4_da_writepages: jbd2_start: 13308 pages, ino 29622301; err -30
Jan 5 14:32:23 Amsterdam kernel: [83651.025873] Buffer I/O error on device sdb1, logical block 151648424
Jan 5 14:32:23 Amsterdam kernel: [83651.026069] Buffer I/O error on device sdb1, logical block 151648425
Jan 5 14:32:23 Amsterdam kernel: [83651.026150] Buffer I/O error on device sdb1, logical block 151648426
Jan 5 14:32:23 Amsterdam kernel: [83651.026232] Buffer I/O error on device sdb1, logical block 151648427
Jan 5 14:32:23 Amsterdam kernel: [83651.026315] Buffer I/O error on device sdb1, logical block 151648428
Jan 5 14:32:23 Amsterdam kernel: [83651.026397] Buffer I/O error on device sdb1, logical block 151648429
Jan 5 14:32:23 Amsterdam kernel: [83651.026479] Buffer I/O error on device sdb1, logical block 151648430
Jan 5 14:32:23 Amsterdam kernel: [83651.026561] Buffer I/O error on device sdb1, logical block 151648431
Jan 5 14:32:23 Amsterdam kernel: [83651.026642] Buffer I/O error on device sdb1, logical block 151648432
Jan 5 14:32:23 Amsterdam kernel: [83651.026724] Buffer I/O error on device sdb1, logical block 151648433
Jan 5 14:32:23 Amsterdam kernel: [83651.026805] Buffer I/O error on device sdb1, logical block 151648434
Jan 5 14:32:23 Amsterdam kernel: [83651.026886] Buffer I/O error on device sdb1, logical block 151648435
Jan 5 14:32:23 Amsterdam kernel: [83651.026976] EXT4-fs warning (device sdb1): ext4_end_bio:250: I/O error writing to inode 29622304 (offset 5612666880 size 49152 starting block 151648692)
Jan 5 14:32:23 Amsterdam kernel: [83651.027154] JBD2: Detected IO errors while flushing file data on sdb1-8
Jan 5 14:32:23 Amsterdam kernel: [83651.027186] journal commit I/O error
Jan 5 14:32:25 Amsterdam kernel: [83652.655529] EXT4-fs error (device sdb1): ext4_find_entry:1209: inode #20971522: comm rtorrent: reading directory lblock 0
Jan 5 14:32:26 Amsterdam kernel: [83654.057155] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Jan 5 14:32:29 Amsterdam kernel: [83657.021919] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Jan 5 14:32:32 Amsterdam kernel: [83659.986661] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Jan 5 14:32:35 Amsterdam kernel: [83662.951339] hub 6-0:1.0: Cannot enable port 2. Maybe the USB cable is bad?
Jan 5 14:32:35 Amsterdam kernel: [83662.951500] hub 6-0:1.0: unable to enumerate USB device on port 2

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

Re: External HDD connecting through USB(3) errors

Post by gabrielh »

Thank you for your update. I will update you with our research progress
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 »

Hi gabriel & co,

The past year I had my external HDD connected to a usb2 port as a result of the beforementioned usb3 issue.
Recently I upgraded to Ubuntu 14.04 running kernel 3.8, so I figured I could try connecting the harddisk to the usb3 port. The same problem sadly still occurs.

As you can see in this log little over a day after connecting the drive it suddenly starts to show errors and fails any more input/output.

I hope we can find a solution to fix this in order to actually be able to use the usb3 ports to connect a usb3 harddrive.

Thank you kindly for your efforts!
May 11 14:04:59 Amsterdam kernel: [1808706.764428] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
May 11 16:41:56 Amsterdam kernel: [1818114.487473] usb 3-1: USB disconnect, device number 2
May 11 16:42:03 Amsterdam kernel: [1818121.684122] usb 6-1: new SuperSpeed USB device number 2 using xhci_hcd
May 11 16:42:04 Amsterdam kernel: [1818121.701428] usb 6-1: Parent hub missing LPM exit latency info. Power management will be impacted.
May 11 16:42:04 Amsterdam kernel: [1818121.703588] usb 6-1: New USB device found, idVendor=1058, idProduct=1042
May 11 16:42:04 Amsterdam kernel: [1818121.703597] usb 6-1: New USB device strings: Mfr=1, Product=2, SerialNumber=5
May 11 16:42:04 Amsterdam kernel: [1818121.703603] usb 6-1: Product: Elements 1042
May 11 16:42:04 Amsterdam kernel: [1818121.703607] usb 6-1: Manufacturer: Western Digital
May 11 16:42:04 Amsterdam kernel: [1818121.703612] usb 6-1: SerialNumber: 575835314333325234373535
May 11 16:42:04 Amsterdam kernel: [1818121.705197] scsi7 : usb-storage 6-1:1.0
May 11 16:42:05 Amsterdam kernel: [1818122.703724] scsi 7:0:0:0: Direct-Access WD Elements 1042 1007 PQ: 0 ANSI: 6
May 11 16:42:05 Amsterdam kernel: [1818122.706936] sd 7:0:0:0: Attached scsi generic sg1 type 0
May 11 16:42:05 Amsterdam kernel: [1818122.707419] sd 7:0:0:0: [sdb] Spinning up disk...
May 11 16:42:11 Amsterdam kernel: [1818123.709836] ......ready
May 11 16:42:11 Amsterdam kernel: [1818128.725274] sd 7:0:0:0: [sdb] 1953519616 512-byte logical blocks: (1.00 TB/931 GiB)
May 11 16:42:11 Amsterdam kernel: [1818128.725862] sd 7:0:0:0: [sdb] Write Protect is off
May 11 16:42:11 Amsterdam kernel: [1818128.725874] sd 7:0:0:0: [sdb] Mode Sense: 47 00 10 08
May 11 16:42:11 Amsterdam kernel: [1818128.726485] sd 7:0:0:0: [sdb] No Caching mode page present
May 11 16:42:11 Amsterdam kernel: [1818128.726564] sd 7:0:0:0: [sdb] Assuming drive cache: write through
May 11 16:42:11 Amsterdam kernel: [1818128.728491] sd 7:0:0:0: [sdb] No Caching mode page present
May 11 16:42:11 Amsterdam kernel: [1818128.728634] sd 7:0:0:0: [sdb] Assuming drive cache: write through
May 11 16:42:11 Amsterdam kernel: [1818128.743575] sdb: sdb1
May 11 16:42:11 Amsterdam kernel: [1818128.746154] sd 7:0:0:0: [sdb] No Caching mode page present
May 11 16:42:11 Amsterdam kernel: [1818128.746264] sd 7:0:0:0: [sdb] Assuming drive cache: write through
May 11 16:42:11 Amsterdam kernel: [1818128.746374] sd 7:0:0:0: [sdb] Attached SCSI disk
May 11 16:43:41 Amsterdam kernel: [1818218.673572] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)

May 11 22:23:07 Amsterdam kernel: [1838563.704146] usb 6-1: reset SuperSpeed USB device number 2 using xhci_hcd
May 11 22:23:07 Amsterdam kernel: [1838563.721414] usb 6-1: Parent hub missing LPM exit latency info. Power management will be impacted.
May 11 22:23:07 Amsterdam kernel: [1838563.722135] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7800
May 11 22:23:07 Amsterdam kernel: [1838563.722147] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7840

May 12 01:41:01 Amsterdam kernel: [1850426.073401] usb 6-1: reset SuperSpeed USB device number 2 using xhci_hcd
May 12 01:41:01 Amsterdam kernel: [1850426.090723] usb 6-1: Parent hub missing LPM exit latency info. Power management will be impacted.
May 12 01:41:01 Amsterdam kernel: [1850426.091448] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7800
May 12 01:41:01 Amsterdam kernel: [1850426.091460] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7840

May 12 08:36:51 Amsterdam kernel: [1875350.242576] usb 6-1: reset SuperSpeed USB device number 2 using xhci_hcd
May 12 08:36:51 Amsterdam kernel: [1875350.259772] usb 6-1: Parent hub missing LPM exit latency info. Power management will be impacted.
May 12 08:36:51 Amsterdam kernel: [1875350.260578] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7800
May 12 08:36:51 Amsterdam kernel: [1875350.260590] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7840

May 12 10:25:42 Amsterdam kernel: [1881873.817654] usb 6-1: reset SuperSpeed USB device number 2 using xhci_hcd
May 12 10:25:42 Amsterdam kernel: [1881873.834825] usb 6-1: Parent hub missing LPM exit latency info. Power management will be impacted.
May 12 10:25:42 Amsterdam kernel: [1881873.835575] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7800
May 12 10:25:42 Amsterdam kernel: [1881873.835586] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7840

May 12 12:17:18 Amsterdam kernel: [1888562.961255] usb 6-1: reset SuperSpeed USB device number 2 using xhci_hcd
May 12 12:17:18 Amsterdam kernel: [1888562.978561] usb 6-1: Parent hub missing LPM exit latency info. Power management will be impacted.
May 12 12:17:18 Amsterdam kernel: [1888562.979262] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7800
May 12 12:17:18 Amsterdam kernel: [1888562.979274] xhci_hcd 0000:05:00.0: xHCI xhci_drop_endpoint called with disabled ep ffff8802061c7840

May 12 18:37:36 Amsterdam kernel: [1911357.505606] hub 6-0:1.0: Cannot enable port 1. Maybe the USB cable is bad?
May 12 18:37:36 Amsterdam kernel: [1911358.025180] usb 6-1: USB disconnect, device number 2
May 12 18:37:41 Amsterdam kernel: [1911362.064677] EXT4-fs error (device sdb1): ext4_find_entry:1273: inode #20971522: comm rtorrent: reading directory lblock 0

May 13 02:00:26 Amsterdam kernel: [1937900.296971] EXT4-fs error (device sdb1): ext4_find_entry:1273: inode #20971521: comm Plex Media Serv: reading directory lblock 0
May 13 02:00:26 Amsterdam kernel: [1937900.297024] EXT4-fs error (device sdb1): ext4_find_entry:1273: inode #20971521: comm Plex Media Serv: reading directory lblock 0
May 13 02:00:26 Amsterdam kernel: [1937900.297182] EXT4-fs error (device sdb1): __ext4_get_inode_loc:3761: inode #57026935: block 228065975: comm Plex Media Serv: unable to read itable block
May 13 02:00:26 Amsterdam kernel: [1937900.297223] EXT4-fs error (device sdb1) in ext4_reserve_inode_write:4688: IO failure
May 13 02:00:31 Amsterdam kernel: [1937905.388087] Aborting journal on device sdb1-8.
May 13 02:00:31 Amsterdam kernel: [1937905.388123] Buffer I/O error on device sdb1, logical block 121667584
May 13 02:00:31 Amsterdam kernel: [1937905.388158] lost page write due to I/O error on sdb1
May 13 02:00:31 Amsterdam kernel: [1937905.388161] JBD2: Error -5 detected when updating journal superblock for sdb1-8.

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

Re: External HDD connecting through USB(3) errors

Post by koenc86 »

Hi gabriel,

Any news on this topic?

Also I am wondering if anyone else is having issues with the USB3 ports in a similar way. Hoping other forum readers can respond too.

Thanks

hwmartin
Posts: 49
Joined: Thu Dec 05, 2013 12:42 am

Re: External HDD connecting through USB(3) errors

Post by hwmartin »

@koenc86: I have a USB3 external hard drive (laptop SATA hard drive in a USB3 enclosure) and I have no problems using the hard drive with my MintBox 2 via USB3.

From your syslog it sounds like you have either a bad USB port, bad cable, or bad sectors on your external hard drive. Do you experience these issues on other computers with USB3? It's possible the fault lies with the external hard drive or enclosure and not with the IPC.

Can you install 'smartmontools' on your IPC and run as root 'smartctl --test=long /dev/sdX' where X is the device letter of your external hard drive. From your syslog this would appear to be /dev/sdb. This will issue a SMART command to the drive to run an extended test in offline mode. This will instruct the drive controller to verify every sector on the drive. If there are bad sectors on the drive the test will fail. Monitor the test progress by executing (again as root) 'smartctl --all /dev/sdb'

The test will likely take 2-3 hours to complete. You may continue to use the drive during that time but it should not be powered off until the self-test is complete.

Example of failure:

Code: Select all

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed: read failure       90%      4860         280578
Example of success:

Code: Select all

SMART Self-test log structure revision number 1
Num  Test_Description    Status                  Remaining  LifeTime(hours)  LBA_of_first_error
# 1  Extended offline    Completed without error 00%         11320         -
smartctl shows you lots of information on the health of the hard drive. On a healthy hard drive you should see that there are 0 reallocated sectors. More than 0 reallocated sectors indicates that the drive will fail in the near future.

Code: Select all

ID# ATTRIBUTE_NAME          FLAG     VALUE WORST THRESH TYPE      UPDATED  WHEN_FAILED RAW_VALUE
  5 Reallocated_Sector_Ct   0x0033   100   100   036    Pre-fail  Always       -       0

Post Reply

Return to “Storage”