[SOLVED] 4TB usb drive not recognized on Centos 7 but works on Centos 6
Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
4TB usb drive not recognized on Centos 7 but works on Centos 6
I have a 4 TB SATA drive plugged into a USB3 to Sata Converter , it is GPT with an ext4 File system on it, when I plug it into an Centos 6 machine it mounts and works fine.
I plug the same drive into any one of several Centos 7 Machines and they don't even recognize that something was plugged into the USB port. there are no new message on /var/log/messege or dmesg. yet if I take the same usb to Sata cable and plug a 1 TB drive into it and plug that into any ofthe Cantos 7 machine it works perfectly.
To me I'm thinking I am missing a driver , but not sure which one.
Maybe you can figure out what the driver is by looking at /var/log/messages, dmsg and dmidecode output on the CentOS6 machine after you attach the drive. You can then check your CentOS7 system to see if it has comparable.
It occurred to me as I was writing this that I have seen multipathd take control of USB drives when I haven't blacklisted them in multipath.conf. Do you buy any chance have multipathd running on the CentOS7 but not the CentOS6?
Maybe you can figure out what the driver is by looking at /var/log/messages, dmsg and dmidecode output on the CentOS6 machine after you attach the drive. You can then check your CentOS7 system to see if it has comparable.
here is the messages from when it attaches succesfully to the Centos 6 machine
Code:
May 17 10:29:45 boston kernel: usb 1-1.1: new high speed USB device number 18 using ehci_hcd
May 17 10:29:45 boston kernel: usb 1-1.1: New USB device found, idVendor=152d, idProduct=0578
May 17 10:29:45 boston kernel: usb 1-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
May 17 10:29:45 boston kernel: usb 1-1.1: Product: External Disk 3.0
May 17 10:29:45 boston kernel: usb 1-1.1: Manufacturer: JMicron
May 17 10:29:45 boston kernel: usb 1-1.1: SerialNumber: 0B136101779446
May 17 10:29:45 boston kernel: usb 1-1.1: configuration #1 chosen from 1 choice
May 17 10:29:45 boston kernel: scsi14 : SCSI emulation for USB Mass Storage devices
May 17 10:29:46 boston kernel: scsi 14:0:0:0: Direct-Access JMicron Tech 3202 PQ: 0 ANSI: 6
May 17 10:29:46 boston kernel: sd 14:0:0:0: Attached scsi generic sg3 type 0
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] 7814037168 512-byte logical blocks: (4.00 TB/3.63 TiB)
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] 4096-byte physical blocks
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] Write Protect is off
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] Assuming drive cache: write through
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] Assuming drive cache: write through
May 17 10:29:46 boston kernel: sdc: sdc1
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] Very big device. Trying to use READ CAPACITY(16).
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] Assuming drive cache: write through
May 17 10:29:46 boston kernel: sd 14:0:0:0: [sdc] Attached SCSI disk
May 17 10:29:46 boston ata_id[34692]: HDIO_GET_IDENTITY failed for '/dev/sdc'
May 17 10:29:46 boston ata_id[34704]: HDIO_GET_IDENTITY failed for '/dev/sdc'
It occurred to me as I was writing this that I have seen multipathd take control of USB drives when I haven't blacklisted them in multipath.conf. Do you buy any chance have multipathd running on the CentOS7 but not the CentOS6?
not sure if multipath is running on the centos machine how ever on the centos 7 machine it is in error
Code:
# systemctl status multipathd
\u25cf multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Mon 2018-07-09 13:04:55 EDT; 10 months 12 days ago
[root@blondie etc]# systemctl restart multipathd
[root@blondie etc]# systemctl status multipathd
\u25cf multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2019-05-22 15:55:39 EDT; 1s ago
ConditionPathExists=/etc/multipath.conf was not met
[root@blondie etc]# systemctl stop multipathd
[root@blondie etc]# systemctl start multipathd
[root@blondie etc]# systemctl status multipathd
\u25cf multipathd.service - Device-Mapper Multipath Device Controller
Loaded: loaded (/usr/lib/systemd/system/multipathd.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Condition: start condition failed at Wed 2019-05-22 16:15:41 EDT; 2s ago
ConditionPathExists=/etc/multipath.conf was not met
This post references yet another post that talks about loading a driver:
Quote:
drave40 wrote:
Just in case anyone still has this problem ( I did, that's how i landed here)
disconnect from USB
find jmicron driver. on my system it's called "pata_jmicron"
load it, "modprobe pata_jmicron"
connect to USB gain
dahdah everything is visible. well, it is here
cheers
On checking my RHEL7 workstation I see there is a driver for that pata_jmicron.ko in the path for each of my kernel versions. Since it is there on RHEL7 it is likely there on CentOS7 which is a binary compile of RHEL7 source. Running "find /usr/lib/modules -name pata_jmicron.ko" should show you same. The subdirectories represent kernel versions and you'd want to try the one that matches your running kernel as reported by "uname -a". No idea if it will work because I don't have a Jmicron device.
On plugging in a WD MyBook 3 TB to my RHEL7 it found the drive so this may be a limitation for that Jmicron.
Last edited by MensaWater; 05-22-2019 at 03:42 PM.
This post references yet another post that talks about loading a driver:
On checking my RHEL7 workstation I see there is a driver for that pata_jmicron.ko in the path for each of my kernel versions. Since it is there on RHEL7 it is likely there on CentOS7 which is a binary compile of RHEL7 source. Running "find /usr/lib/modules -name pata_jmicron.ko" should show you same. The subdirectories represent kernel versions and you'd want to try the one that matches your running kernel as reported by "uname -a". No idea if it will work because I don't have a Jmicron device.
On plugging in a WD MyBook 3 TB to my RHEL7 it found the drive so this may be a limitation for that Jmicron.
It apperar that the jmicron controller is the issue. I picked up a different USB to Sata controller over the weekend , and it works like a charm !
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
