Hi All
I have a Seagate 1TB externall HDD that is USB3 enabled The plug into the hdd is a USB3 plug the otherside an ordinary usb2 plug
On Windows XP it works
But 12.3 does not see it. I did add ntfs to
kdesu /usr/bin/kwrite /etc/filesystems
So what do I do next?
thanks
JAndre
On Wed, 01 May 2013 16:26:04 +0000, ClrScr wrote:
> So what do I do next?
With the drive plugged in, what’s the output of “lsusb”? (Please post in
code tags, “#” button in the advanced editor)
After plugging the drive in, what are the last dozen lines or so of the
output from “dmesg”?
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
You could try plugging it in to a different USB port.
Also ensure you do not have an entry in your /etc/fstab which is preventing this from working.
jandre@linux-azzt:~> lsusb
Bus 001 Device 003: ID 03f0:2b17 Hewlett-Packard LaserJet 1020
Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
and the dmesg
[27362.248622] scsi354 : usb-storage 1-3:1.0
[27362.501148] usb 1-3: USB disconnect, device number 45
[27421.424038] usb 1-3: new high-speed USB device number 46 using ehci_hcd
[27421.595371] usb 1-3: New USB device found, idVendor=0bc2, idProduct=2330
[27421.595378] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27421.595382] usb 1-3: Product: Raptor 2.5" USB 3.0
[27421.595384] usb 1-3: Manufacturer: Seagate
[27421.595387] usb 1-3: SerialNumber: 2HC015KJ
[27421.596737] scsi355 : usb-storage 1-3:1.0
[27421.844815] usb 1-3: USB disconnect, device number 46
[27480.768032] usb 1-3: new high-speed USB device number 47 using ehci_hcd
[27481.008681] usb 1-3: New USB device found, idVendor=0bc2, idProduct=2330
[27481.008689] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27481.008693] usb 1-3: Product: Raptor 2.5" USB 3.0
[27481.008696] usb 1-3: Manufacturer: Seagate
[27481.008699] usb 1-3: SerialNumber: 2HC015KJ
[27481.009308] scsi356 : usb-storage 1-3:1.0
[27481.166854] usb 1-3: USB disconnect, device number 47
[27540.092034] usb 1-3: new high-speed USB device number 48 using ehci_hcd
[27540.227324] usb 1-3: New USB device found, idVendor=0bc2, idProduct=2330
[27540.227331] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27540.227334] usb 1-3: Product: Raptor 2.5" USB 3.0
[27540.227337] usb 1-3: Manufacturer: Seagate
[27540.227340] usb 1-3: SerialNumber: 2HC015KJ
[27540.228669] scsi357 : usb-storage 1-3:1.0
[27540.500659] usb 1-3: USB disconnect, device number 48
[27599.424033] usb 1-3: new high-speed USB device number 49 using ehci_hcd
[27599.595498] usb 1-3: New USB device found, idVendor=0bc2, idProduct=2330
[27599.595505] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27599.595509] usb 1-3: Product: Raptor 2.5" USB 3.0
[27599.595511] usb 1-3: Manufacturer: Seagate
[27599.595514] usb 1-3: SerialNumber: 2HC015KJ
[27599.598586] scsi358 : usb-storage 1-3:1.0
[27599.818691] usb 1-3: USB disconnect, device number 49
[27658.744031] usb 1-3: new high-speed USB device number 50 using ehci_hcd
[27658.915410] usb 1-3: New USB device found, idVendor=0bc2, idProduct=2330
[27658.915417] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27658.915421] usb 1-3: Product: Raptor 2.5" USB 3.0
[27658.915424] usb 1-3: Manufacturer: Seagate
[27658.915427] usb 1-3: SerialNumber: 2HC015KJ
[27658.916824] scsi359 : usb-storage 1-3:1.0
[27659.146474] usb 1-3: USB disconnect, device number 50
[27758.648084] usb 1-3: new high-speed USB device number 51 using ehci_hcd
[27758.857246] usb 1-3: New USB device found, idVendor=0bc2, idProduct=2330
[27758.857253] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[27758.857257] usb 1-3: Product: Raptor 2.5" USB 3.0
[27758.857260] usb 1-3: Manufacturer: Seagate
[27758.857263] usb 1-3: SerialNumber: 2HC015KJ
[27758.860949] scsi360 : usb-storage 1-3:1.0
[27759.102464] usb 1-3: USB disconnect, device number 51
Thanks Jim, I hope this helps
J
For general information for comparison purposes - here is the dmesg of a different USB3 external HDD that works (when connected to a USB-2.0 port)
[38519.828193] usb 9-2: new high-speed USB device number 2 using xhci_hcd
[38519.844050] usb 9-2: New USB device found, idVendor=152d, idProduct=0539
[38519.844055] usb 9-2: New USB device strings: Mfr=1, Product=11, SerialNumber=3
[38519.844059] usb 9-2: Product: USB3.0 Device
[38519.844061] usb 9-2: Manufacturer: JMicron
[38519.844064] usb 9-2: SerialNumber: BBA0000001C6
[38519.875520] Initializing USB Mass Storage driver...
[38519.875883] scsi8 : usb-storage 9-2:1.0
[38519.875960] usbcore: registered new interface driver usb-storage
[38519.875961] USB Mass Storage support registered.
[38520.877713] scsi 8:0:0:0: Direct-Access Generic USB3.0 PQ: 0 ANSI: 2 CCS
[38520.878011] sd 8:0:0:0: Attached scsi generic sg3 type 0
[38520.878528] sd 8:0:0:0: [sdb] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB)
[38520.879403] sd 8:0:0:0: [sdb] Write Protect is off
[38520.879410] sd 8:0:0:0: [sdb] Mode Sense: 28 00 00 00
[38520.880218] sd 8:0:0:0: [sdb] No Caching mode page present
[38520.880222] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[38520.882407] sd 8:0:0:0: [sdb] No Caching mode page present
[38520.882412] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[38521.162008] sdb: sdb1
[38521.164531] sd 8:0:0:0: [sdb] No Caching mode page present
[38521.164535] sd 8:0:0:0: [sdb] Assuming drive cache: write through
[38521.164538] sd 8:0:0:0: [sdb] Attached SCSI disk
HEre is a copy of my etc/fstab
I have tried another usb port will try others as well
thanks
J
/dev/disk/by-id/ata-ST3160021A_5MT0CAGJ-part3 swap swap defaults 0 0
/dev/disk/by-id/ata-ST3160021A_5MT0CAGJ-part6 / ext4 acl,user_xattr 1 1
/dev/disk/by-id/ata-ST3160021A_5MT0CAGJ-part4 /home ext4 defaults 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/disk/by-id/ata-ST3160021A_5MT0CAGJ-part5 /home/jandre/windows/Audiovideo ntfs-3g defaults 0 0
/dev/disk/by-id/ata-SAMSUNG_HD155UI_S2KRJ1PB401795-part3 /home/jandre/windows/Data ntfs-3g defaults 0 0
/dev/disk/by-id/ata-SAMSUNG_HD155UI_S2KRJ1PB401795-part4 /home/jandre/windows/Data2 ntfs-3g defaults 0 0
/dev/disk/by-id/ata-SAMSUNG_HD155UI_S2KRJ1PB401795-part1 /home/jandre/windows/Downloads ntfs-3g defaults 0 0
/dev/disk/by-id/ata-SAMSUNG_HD155UI_S2KRJ1PB401795-part2 /home/jandre/windows/MyDocs ntfs-3g defaults 0 0
/dev/disk/by-id/ata-ST3160021A_5MT0CAGJ-part1 /home/jandre/windows/Windows1 ntfs-3g defaults 0 0
What is this samsung entry ? Is that your external USB drive ?
If so, it is interfering with the hot plug auto mounting of your external drive and by removing you should be able to automatically mount the drive.
IF that is your external drive, remove it, reboot, and then try plugging in your external US drive.
The other method is to boot with the external USB drive already plugged in and powered.
No the smasung uin an internal windows drive I have dualbooting system
I have booted with the external usb in place but it still does not see it!
thanks
With your external drive plugged in, is it seen if you type with root permissions:
fdisk -l
… but having typed that, with this lsusb output that you posted :
Bus 001 Device 003: ID 03f0:2b17 Hewlett-Packard LaserJet 1020
Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
it makes me think it will not be seen by the fdisk command (as I do not see the 0bc2:2330 code in that lsusb output).
Was the external drive plugged in and switched ON when you sent the ‘lsusb’ command ?
Before plugging in the external drive (after switching it on) how long did you wait. On my 1.5 TB external drives, I need to wait about 10 seconds for the drives to spin up before I plug them in.
Another possibility is that there is an inconsistency (I am unsure of correct terminology) on the NTFS external drive and you need to run a chkdsk on it : CHKDSK - Wikipedia, the free encyclopedia The ntfs-3g fuse application can have difficulty with drives that are in such an uncorrected state. Typically in such a case it will be mounted as ‘read only’ … but I have seen cases where it will not mount at all. Although having typed that, typically the ‘lsusb’ command will show the drive.
I did a Google search on the 0bc2:2330 code of the drive, but the only GNU/Linux hits I came up with where this openSUSE thread.
Its possible udev tuning is needed to make the drive visible, and if that is the case then that likely exceeds my knowledge. In such a case if no one else on the forum can provide guidance, you could write a bug report on openSUSE not recognizing / mounting the drive. That will bring this to the attention of the SuSE-GmbH packagers , who have more detailed knowledge here and they may be able to provide the necessary edits to your GNU/Linux PC’s configuration files. The advantage of a bug report is other GNU/Lniux distributions will also benefit if the SuSE-GmbH packagers find a fix, as they are fairly good at sending their fixes upstream.
I have read for other GNU/Linux distributions, of cases where the external drive did not show up with ‘lsusb’.
In one case the ‘usb_storage’ kernel module was not loaded. What was done successfully in one such case, was to unconnect the externel drive. Then with root permissions send the command:
modprobe usb_storage
and then switch on the drive and reconnect the external drive. My suspicion is that will not work, but you could try it.
But all other USB devices work. This is the only device I have that is USB3 enabled/ready.
Then how on oearth do I write a Bug report! Would I even know what to include?
thanks again!
Why do you say “but” ??? < puzzled > … Hey, I can’t see your PC. Nor can I type the commands on it. So I can only ask ? What YOU have me do ? Completely ignore the possibility and not suggest the possibility ?? < puzzled >
There is guidance for bug reports here :
https://en.opensuse.org/openSUSE:Submitting_bug_reports
Raise the bug report on the ‘kernel’ in openSUSE-12.3.
Boot your PC, plug in the USB drive, then copy the entire output of the ‘dmesg’ into a text file and copy that text file to the bug report. Also include the output of lsusb in the bug report. Also note in the bug report that your fstab correctly makes no mention of the external USB drive.
You can use your openSUSE forum user name and password when logging in to the openSUSE bugzilla.
oldcpu, I think that there is a misunderstanding! The but is not supposed to be an objection, rather, I was trying to point out that all the other usb “products” function fine and therefore trying to ask how it will make a difference? I am not against your suggestion just trying to obtain some clarification!
Thanks for the explanation regards the bug report!
J
On Thu, 02 May 2013 15:26:01 +0000, ClrScr wrote:
> But all other USB devices work. This is the only device I have that is
> USB3 enabled/ready.
What other USB devices are you talking about here?
Is the usb_storage module loaded already? (run “lsmod | grep usb_storage”
to find out)
What’s the model on the drive that’s not working?
From the lsusb output, it seems it’s not there, and from the dmesg
output, it looks like it’s being disconnected for some reason. Like
oldcpu, I don’t know that making sure the module is loaded first will
prevent that, but it couldn’t hurt to try.
Jim
–
Jim Henderson
openSUSE Forums Administrator
Forum Use Terms & Conditions at http://tinyurl.com/openSUSE-T-C
I note you posted about these USB devices:
Bus 001 Device 003: ID 03f0:2b17 Hewlett-Packard LaserJet 1020
Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
One appears to be a printer. The either appears to be a a mouse. Neither is a usb_storage device. There kernel model noted in the reference I quoted was for usb_storage devices.
Now if you are also plugging in other USB storage devices and they are working fine, then that is valuable information to post.
If you type:
lsmod | grep storage
and it lists ‘usb_storage’ kernel module then there is no need to try the ‘modprobe usb_storage’.
Jim, thanks
jandre@linux-azzt:~> lsmod | grep usb_storage
usb_storage 47841 0
usbcore 200347 5 usb_storage,usblp,usbhid,uhci_hcd,ehci_hcd
And especially for oldcpu
jandre@linux-azzt:~> lsusb
Bus 001 Device 003: ID 03f0:2b17 Hewlett-Packard LaserJet 1020
Bus 001 Device 052: ID 04a9:31f1 Canon, Inc. PowerShot A3100 IS / PowerShot A3150 IS
Bus 001 Device 051: ID 0951:1642 Kingston Technology DT101 G2
Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
The other devices : hp1020 printer
memory sticks 1GB, 2GB, 8GB
camera
cellphone
SO if I understand correct the module is loaded
The device
Seagate 1TB
Serial Number 2GHHC159
Thanks
J
usbcore ?
I don’t get that. Clearly there are differences in our PCs. For my USB3 all I get is:
oldcpu@corei7-920:~> lsmod | grep storage
usb_storage 57401 1
and
oldcpu@corei7-920:~> lsusb
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 002 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 002 Device 003: ID 046d:0821 Logitech, Inc. HD Webcam C910
**Bus 009 Device 004: ID 152d:0539 JMicron Technology Corp. / JMicron USA Technology Corp. **
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 004: ID 0557:2213 ATEN International Co., Ltd CS682 2-Port USB 2.0 DVI KVM Switch
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
where my usb3 storage device is highlighted in red.
Your best efforts may be best spent either on a bug report, or following up any custom udev tuning leads that may be passed your way.
Is usbcore associated with initrd ? Has that been replaced by systemd ?
When I look at my system I see this:
oldcpu@corei7-920:~> dmesg | grep usbcore
0.410886] usbcore: registered new interface driver usbfs
0.410895] usbcore: registered new interface driver hub
0.410909] usbcore: registered new device driver usb
0.803287] usbcore: registered new interface driver usbhid
12.580413] usbcore: registered new interface driver snd-usb-audio
12.593306] usbcore: registered new interface driver uvcvideo
[38519.875960] usbcore: registered new interface driver usb-storage
(the last entry is me plugging in my usb-storage device)
But I have no kernel module called usbcore.