USB 3.0 Not mounting

[marbletravis]

I have two USB 3.0 drives that I am trying to mount on a pogoplug v4 running arch.

I am seeing the following output on dmesg

[ 72.479176] usb 2-2: reset high speed USB device number 2 using xhci_hcd
[ 72.499441] xhci_hcd 0000:00:01.0: WARN: short transfer on control ep
[ 72.499498] xhci_hcd 0000:00:01.0: xHCI xhci_drop_endpoint called with disabled ep c7a06f60
[ 72.499520] xhci_hcd 0000:00:01.0: xHCI xhci_drop_endpoint called with disabled ep c7a06f8c
[ 72.501189] scsi 2:0:0:0: Device offlined - not ready after error recovery


Everything I have found on the internet points to a kernal issue, but points to issues in the 2.6 kernal, as far as I can tell arch is running a 3.x kernal.

Has anyone else ran into this.

I can mount a USB 2.0 device on the USB 3.0 ports, just not a USB 3.0 device.

Thanks,
Travis

[winestock]

On PPv4 I was able to mount my USB 3.0 Segate portable HD. I was able to mount both partitions. Here is what dmesg reported:
$this->bbcode_second_pass_quote('', '[')66414.202915] usb 3-1: new SuperSpeed USB device number 2 using xhci_hcd
[66414.223182] usb 3-1: Parent hub missing LPM exit latency info. Power management will be impacted.
[66414.225084] scsi2 : usb-storage 3-1:1.0
[66415.223501] scsi 2:0:0:0: Direct-Access Seagate Backup+ BK 0409 PQ: 0 ANSI: 6
[66415.224953] sd 2:0:0:0: [sdd] 1953525167 512-byte logical blocks: (1.00 TB/931 GiB)
[66415.225228] sd 2:0:0:0: Attached scsi generic sg3 type 0
[66415.225614] sd 2:0:0:0: [sdd] Write Protect is off
[66415.225637] sd 2:0:0:0: [sdd] Mode Sense: 4f 00 00 00
[66415.226019] sd 2:0:0:0: [sdd] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[66415.258656] sdd: sdd1 sdd2
[66415.265871] sd 2:0:0:0: [sdd] Attached SCSI disk
[66524.712566] EXT3-fs (sdd1): using internal journal
[66524.712591] EXT3-fs (sdd1): mounted filesystem with writeback data mode
[66524.717242] kjournald starting. Commit interval 5 seconds
[66548.728919] EXT4-fs (sdd2): mounted filesystem with ordered data mode. Opts: (null)

[marbletravis]

I am running 3.1.10-16-ARCH

I had read that people had better luck with Linux-Kirkwood, which I tried and couldn't get arch to boot afterwards. Did you run into that issue?

I just did a clean install I will update to linux-kirkwood, through pacman and see if it works better this time.

Thanks

[marbletravis]

Ok, it worked this time... But I am still having an issue

I see this in dmesg


[ 73.811195] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 73.831656] usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 73.837656] scsi2 : usb-storage 3-2:1.0
[ 74.831692] scsi 2:0:0:0: Direct-Access JMB352 RAID-1 1234 PQ: 0 ANSI: 2 CCS
[ 74.833077] sd 2:0:0:0: [sdb] 3907029152 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 74.833494] sd 2:0:0:0: [sdb] Write Protect is off
[ 74.833517] sd 2:0:0:0: [sdb] Mode Sense: 28 00 00 00
[ 74.833649] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 74.833927] sd 2:0:0:0: [sdb] No Caching mode page present
[ 74.839398] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 74.860879] sd 2:0:0:0: [sdb] No Caching mode page present
[ 74.870637] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 74.888879] sdb: sdb1
[ 74.891201] sd 2:0:0:0: [sdb] No Caching mode page present
[ 74.896682] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 74.914776] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 75.620802] fuse init (API version 7.20)

However when I try to access the mount in /media, it says Transport endpoint is not connected, is this a problem with udev-automount? The drive is a USB raid enclosure, that has worked in the past on USB 2.0 (in arch), just doesn't want to work on USB 3.0 in arch linux. I do have another usb 3.0 drive, non raid, and it worked. So I am wondering if I need to mount it differently.

Edit: the USB raid enclosure is GPT not MBR. I can change it, I don't see a real need for GPT, I will see if that works and report back.

Thanks

[winestock]

$this->bbcode_second_pass_quote('marbletravis', 'O')k, it worked this time... But I am still having an issue

I see this in dmesg


[ 73.811195] usb 3-2: new SuperSpeed USB device number 2 using xhci_hcd
[ 73.831656] usb 3-2: Parent hub missing LPM exit latency info. Power management will be impacted.
[ 73.837656] scsi2 : usb-storage 3-2:1.0
[ 74.831692] scsi 2:0:0:0: Direct-Access JMB352 RAID-1 1234 PQ: 0 ANSI: 2 CCS
[ 74.833077] sd 2:0:0:0: [sdb] 3907029152 512-byte logical blocks: (2.00 TB/1.81 TiB)
[ 74.833494] sd 2:0:0:0: [sdb] Write Protect is off
[ 74.833517] sd 2:0:0:0: [sdb] Mode Sense: 28 00 00 00
[ 74.833649] sd 2:0:0:0: Attached scsi generic sg1 type 0
[ 74.833927] sd 2:0:0:0: [sdb] No Caching mode page present
[ 74.839398] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 74.860879] sd 2:0:0:0: [sdb] No Caching mode page present
[ 74.870637] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 74.888879] sdb: sdb1
[ 74.891201] sd 2:0:0:0: [sdb] No Caching mode page present
[ 74.896682] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 74.914776] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 75.620802] fuse init (API version 7.20)

However when I try to access the mount in /media, it says Transport endpoint is not connected, is this a problem with udev-automount? The drive is a USB raid enclosure, that has worked in the past on USB 2.0 (in arch), just doesn't want to work on USB 3.0 in arch linux. I do have another usb 3.0 drive, non raid, and it worked. So I am wondering if I need to mount it differently.

Edit: the USB raid enclosure is GPT not MBR. I can change it, I don't see a real need for GPT, I will see if that works and report back.

Thanks

[marbletravis]

Converted raid to MBR and it still didn't work.

The raid enclosure is a 2tb (2x2TB Raid 1) MBR NTFS volume, the other drive (Seagate) is a USB 3.0 3TB MBR NTFS volume.

I realize I could just use the Seagate, but for my purposes I want the raid 1 enclosure, for backups. Again any help greatly appreciated.

[marbletravis]

Manual mounting does work, I found this thread

viewtopic.php?f=18&t=4376

This will work for me, for now at least. Any ideas on why automount doesn't work, is it just a bug?

Thanks,
Travis

[moonman]

Did you actually read the thread?

You need to remove udev-automount and install devmon for ntfs drives to automount