| Summary: | cannot mount 3TB sata drive from usb to sata docking station | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Natxo Asenjo <natxo> |
| Component: | kernel | Assignee: | Torez Smith <torez> |
| Status: | CLOSED NOTABUG | QA Contact: | Red Hat Kernel QE team <kernel-qe> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.1 | CC: | antoni+redhat-bugs, coughlan, dmilburn, jshortt, peterm, rtguille, rwheeler |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-09-17 14:27:06 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Natxo Asenjo
2011-08-29 07:46:09 UTC
We don't support NTFS-3G in RHEL. Do you see the same problem when using a supported file system like ext4? Thanks! Yes, originally the disk was unformatted. I thought there was a problem with the partition table so I built it locally (no usb docking station, direct sata connection) in another pc with rhel 6.1 amd64 and it got detected. I then used parted to make a gpt partition table and a ext4 file system. Everything worked on a direct sata connection. Back to the usb-to-sata docking, nothing worked. So, yes, in a direct sata connection with a ext4 filesystem it works. But this is a laptop, so I cannot install a 3''5 sata drive in it. That's why I want to use the docking station. My experience has been that several of the USB/e-sata docking stations work for large drives only when you use the e-sata connection. I assumed without digging into that this was a failure on the USB firmware side, but it might be libata related. When this works for you from windows, do you see the full size drive (3TB)? What is the specific USB enclosure you used (I saw the bridge info above which is useful as well, thanks!) I should have said USB SCSI related - libata is not used for USB devices I believe. Yes, windows sees the full drive size. Sorry, I missed your other question. I use no usb enclosure, this is a sharkoon drivelink usb 2 (if I may link the product, this is it: http://www.sharkoon.com/?q=en/content/drivelink-usb20). It works brilliantly with disks up to 2TB with rhel 6.1. update: I have bought a new usb docking station, a Sharkoon Quickport XT, and now I see the disk with usb. It only sees 801 GB, though: Aug 31 19:36:42 host kernel: usb 2-3: new high speed USB device using ehci_hcd and address 6 Aug 31 19:36:42 host kernel: usb 2-3: New USB device found, idVendor=152d, idProduct=2336 Aug 31 19:36:42 host kernel: usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=5 Aug 31 19:36:42 host kernel: usb 2-3: Product: JM20336 SATA, USB Combo Aug 31 19:36:42 host kernel: usb 2-3: Manufacturer: JMicron Aug 31 19:36:42 host kernel: usb 2-3: SerialNumber: DCA104624288 Aug 31 19:36:42 host kernel: usb 2-3: configuration #1 chosen from 1 choice Aug 31 19:36:42 host kernel: scsi9 : SCSI emulation for USB Mass Storage devices Aug 31 19:36:47 host kernel: scsi 9:0:0:0: Direct-Access WDC WD30 EZRX-00MMMB0 PQ: 0 ANSI: 2 CCS Aug 31 19:36:47 host kernel: sd 9:0:0:0: Attached scsi generic sg2 type 0 Aug 31 19:36:47 host kernel: sd 9:0:0:0: [sdb] 1565565872 512-byte logical blocks: (801 GB/746 GiB) Aug 31 19:36:47 host kernel: sd 9:0:0:0: [sdb] Write Protect is off Aug 31 19:36:47 host kernel: sd 9:0:0:0: [sdb] Assuming drive cache: write through Aug 31 19:36:47 host kernel: sd 9:0:0:0: [sdb] Assuming drive cache: write through Aug 31 19:36:57 host kernel: sdb: sdb1 Aug 31 19:36:57 host kernel: sd 9:0:0:0: [sdb] Assuming drive cache: write through Aug 31 19:36:57 host kernel: sd 9:0:0:0: [sdb] Attached SCSI disk Aug 31 19:36:57 host kernel: EXT4-fs (sdb1): mounted filesystem with ordered data mode lsub: Bus 002 Device 006: ID 152d:2336 JMicron Technology Corp. / JMicron USA Technology Corp. Hard Disk Drive Tomorrow I will get an e-sata cable and see if that way I can access the 3TB it has. Hi Natxo, I was looking through the list of special cases for broken usb devices and noticed JMicron has its own issues and quirks. This just might be a new device that hasn't been updated into the quirk table. On the kernel command line, can you add: usb-storage.quirks=152d:2338:ra I have never tried that but according to the kernel documentation that might work (it saves me from compiling a kernel and sending it to you). Let me know if that helps or not. Cheers, Don Hi Don, I have added that to the kernel line in /boot/grub/menu.lst and rebooted. Then I saw this: Sep 7 18:46:33 host kernel: usb 2-1: new high speed USB device using ehci_hcd and address 4 Sep 7 18:46:33 host kernel: usb 2-1: New USB device found, idVendor=1 52d, idProduct=2338 Sep 7 18:46:33 host kernel: usb 2-1: New USB device strings: Mfr=1, P roduct=2, SerialNumber=5 Sep 7 18:46:33 host kernel: usb 2-1: Product: USB to ATA/ATAPI bridge Sep 7 18:46:33 host kernel: usb 2-1: Manufacturer: JMicron Sep 7 18:46:33 host kernel: usb 2-1: SerialNumber: 000001D91CA1 Sep 7 18:46:33 host kernel: usb 2-1: configuration #1 chosen from 1 c hoice Sep 7 18:46:33 host kernel: usb-storage 2-1:1.0: Quirks match for vid 152d pid 2338: 8020 Sep 7 18:46:33 host kernel: scsi7 : SCSI emulation for USB Mass Storage devices Sep 7 18:46:38 host kernel: scsi 7:0:0:0: Direct-Access WDC WD30 EZRX-00MMMB0 PQ: 0 ANSI: 5 Sep 7 18:46:38 host kernel: sd 7:0:0:0: Attached scsi generic sg2 type 0 Sep 7 18:46:38 host kernel: sd 7:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16). Sep 7 18:46:38 host kernel: sd 7:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.72 TiB) Sep 7 18:46:38 host kernel: sd 7:0:0:0: [sdb] Write Protect is off Sep 7 18:46:38 host kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through Sep 7 18:46:38 host kernel: sd 7:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16). Sep 7 18:46:38 host kernel: sd 7:0:0:0: [sdb] Assuming drive cache: write through Sep 7 18:46:39 host kernel: sdb: Sep 7 18:46:39 host kernel: usb 2-1: reset high speed USB device using ehci_hcd and address 4 Sep 7 18:46:39 host kernel: usb 2-1: reset high speed USB device using ehci_hcd and address 4 Sep 7 18:46:39 host kernel: usb 2-1: reset high speed USB device using ehci_hcd and address 4 so the quirks change have made no difference, I am afraid. E-sata is working fine, by the way. I'll be gladly willing to donate the hardware to get it supported, by the way. This kind of cheap storage is really useful and it would be great to have it working in linux. Since RHEL 6.2 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. @Natxo Asenjo There is some information (actually, a discussion about quirks) in the kernel mailing lists: "JMicron 20337 (152d:2338) and 3TB" in: http://comments.gmane.org/gmane.linux.usb.general/62798 Somebody pointed this to me, are you aware of it? (IMPORTANT) http://bigacid.wordpress.com/2008/12/08/jm20337-read-data-corruption-solution/ I just saw there is activity on this item. I no longer use the usb interface but always the e-sata one. So as far as I'm concerned the bug may be closed Hello,
please reopen this bug, the usb-storage driver still has the same problem, and the driver still reports ~800GB for a 3TB size whether with the usb quirks kernel option or not. Windows sees the drive properly.
# /proc/cmdline includes:
usb-storage.quirks=152d:2336:ra
# lsusb:
Bus 001 Device 016: ID 152d:2336 JMicron Technology Corp. / JMicron USA Technology Corp. Hard Disk Drive
# lshw:
*-usb:0
description: Mass storage device
product: JM20336 SATA, USB Combo
vendor: JMicron
physical id: 1
bus info: usb@1:1
logical name: scsi3
version: 1.00
serial: DCC110616328
capabilities: usb-2.00 scsi emulated
configuration: driver=usb-storage maxpower=2mA speed=480Mbit/s
*-disk
description: SCSI Disk
product: EFRX-68AX9N0
vendor: WDC WD30
physical id: 0.0.0
bus info: scsi@3:0.0.0
logical name: /dev/sdb
size: 746GiB (801GB)
capabilities: gpt-1.00 partitioned partitioned:gpt
configuration: ansiversion=2 guid=e4915227-1c7f-4886-a21d-741941c2c893 logicalsectorsize=512 sectorsize=512
|