Tumbelweed kernel cannot recognize USB portable disk

Hi I have a USB portable drive that is suddenly not recognised by openSUSE. Gparted won’t see it, fdisk won’t see it, the KDE Notifier in the systray won’t see it. It’s an NTFS filesystem. It was recognised yesterday.

If I plug it into a windows machine it auto opens immediately. If I boot the openSUSE computer from a live CD (Knoppix) the USB drive is recognised in the boot process, works fine in Knoppix on the same computer.

If I plug a different USB drive into the computer’s USB socket in openSUSE computer, that drive is recognised.

Any ideas on how to get openSUE to see this particular USB drive again?

Thanks

As usual, look with dmesg when you connect it.

But most cases when this happens is when the NTFS file system is not properly closed on a Windows system. Thus first be sure you do a remove sabely (or different wording, I do not use Windows) before you connect it to any Linux system.

On 2014-06-17 12:26, hcvv wrote:
>
> As usual, look with dmesg when you connect it.

I concur.

> But most cases when this happens is when the NTFS file system is not
> properly closed on a Windows system. Thus first be sure you do a remove
> sabely (or different wording, I do not use Windows) before you connect
> it to any Linux system.

Right, but in those cases fdisk or gparted would see it, and he says
they don’t. :-?


Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

What happens if you boot from an openSUSE Live medium, then insert the stick?

It’s OK for the windows check, passed that test.
It works fine in windows. And it woks fine in Linux. It works fine in 5 computers in my house. It just doesn’t work fine in this one installation of openSUSE.

Thanks for the dmesg tip. So I plugged it in and ran dmesg. Here’s the return:

opensuse131:/home/john # dmesg 
[12967.619021] usb 1-2: new high-speed USB device number 12 using ehci-pci
[12967.736861] usb 1-2: New USB device found, idVendor=0bc2, idProduct=2320
[12967.736865] usb 1-2: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[12967.736867] usb 1-2: Product: Expansion
[12967.736869] usb 1-2: Manufacturer: Seagate
[12967.736871] usb 1-2: SerialNumber: NA47M0BF


So openSUSE recognises it as a Seagate USB device. But from there on it ignores it. The same computer with the same USB device, if I leave it plugged to the same USB port and boot to Knoppix, it just bursts with access. It leaps open straight away and say “Hi look at my files”. But in openSUSE no interest. What’s happened is that openSUSE has decided to ignore this specific device. It’s a problem in openSUSE, not in the USB drive.

Any thoughts? I’m beginning to think I need to re-install openSUSE.

I can not cite out of my head whaa exactly should follow in dmesg, but normaly it should detect it is mass-storage. And that does not happen.

Check the difference with the dmesg on a linux were it works as expected.

Additional information about what information the system got out of the device can be seen through lsusb. First use it to find out on which bus/address it is and then use the the address and the -v option to get the info.

I’m typing into Iceweasel in Knoppix. Same computer. I insert the 1tb USB drive. I hear a whirring (of the Knoppix CD) Than all is quiet. I open the file browser [PCmanFM]. I look in the left panel. There I see “seagate expansion drive”. I click it and Voila! there are my files.

Here’s a well behaved 500Gb USB drive being plugged in:

opensuse131:/home/john # dmesg
   96.913050] usb 1-3: new high-speed USB device number 3 using ehci-pci
   97.043913] usb 1-3: New USB device found, idVendor=059f, idProduct=102a
   97.043918] usb 1-3: New USB device strings: Mfr=10, Product=11, SerialNumber=5
   97.043920] usb 1-3: Product: LaCie Device
   97.043923] usb 1-3: Manufacturer: LaCie
   97.043925] usb 1-3: SerialNumber: 100329B40017
   97.082409] usb-storage 1-3:1.0: USB Mass Storage device detected
   97.082516] scsi6 : usb-storage 1-3:1.0
   97.082629] usbcore: registered new interface driver usb-storage
   98.126437] scsi 6:0:0:0: Direct-Access     Hitachi  HTS545050B9A300       PQ: 0 ANSI: 2 CCS
   98.126707] sd 6:0:0:0: Attached scsi generic sg2 type 0
   98.128793] sd 6:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
   98.129793] sd 6:0:0:0: [sdb] Write Protect is off
   98.129798] sd 6:0:0:0: [sdb] Mode Sense: 28 00 00 00
   98.130792] sd 6:0:0:0: [sdb] No Caching mode page found
   98.130795] sd 6:0:0:0: [sdb] Assuming drive cache: write through
   98.156307]  sdb: sdb1
   98.159669] sd 6:0:0:0: [sdb] Attached SCSI disk

Here’s the dodgy drive being plugged in:

opensuse131:/home/john # dmesg
  358.540025] usb 1-3: new high-speed USB device number 4 using ehci-pci
  358.657830] usb 1-3: New USB device found, idVendor=0bc2, idProduct=2320
  358.657836] usb 1-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1
  358.657839] usb 1-3: Product: Expansion
  358.657841] usb 1-3: Manufacturer: Seagate
  358.657844] usb 1-3: SerialNumber: NA47M0BF

Here’s ls usb -v

opensuse131:/home/john # lsusb -v

Bus 001 Device 004: ID 0bc2:2320 Seagate RSS LLC USB 3.0 bridge [Portable Expansion Drive]
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.10
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0        64
  idVendor           0x0bc2 Seagate RSS LLC
  idProduct          0x2320 USB 3.0 bridge [Portable Expansion Drive]
  bcdDevice            1.00
  iManufacturer           2 Seagate
  iProduct                3 Expansion
  iSerial                 1 NA47M0BF
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           85
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)                                                                                                                                                                
    MaxPower              100mA                                                                                                                                                    
    Interface Descriptor:                                                                                                                                                          
      bLength                 9                                                                                                                                                    
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           4
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     98 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        Data-in pipe (0x03)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        Data-out pipe (0x04)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        Status pipe (0x02)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               0
        Command pipe (0x01)
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength           22
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000002
      Link Power Management (LPM) Supported
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000e
      Device can operate at Full Speed (12Mbps)
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   1
      Lowest fully-functional device speed is Full Speed (12Mbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat        2047 micro seconds
Device Status:     0x0000

Very strange. As you see the detection stops where the other one goes on seeing Mass storage device.

And at the same time in the lsusb we see

bInterfaceClass         8 Mass Storage

Not that I know exactly where the term Mass Storage must be mentioned/found, but it is at least somewhere on the device.

I had a similar problem, around a year ago. An 80G external drive was being recognized as 4G. And there was nothing that I was able to do to fix it. However, the drive looked fine on another computer (same opensuse version).

After reboot, it was again seen as 80G. So I think some wrong information was being buffered somewhere and not updated.

I see some usb 3 in the logs, perhaps you can try to use a cheap usb hub, i had the same issue not so long ago and it took me weeks to figure out why my usb install is not booting :(. It is a bug with usb3 and most probably with the suse kernel iirc. Any ways just a suggestion it may or may not be a solution ;).

I wish I’d seen this half an hour ago.

Instead: I take the occasional image of the root partition. I took one 2 days ago. So I wrote that one back to the root partition just now. When I rebooted the correct behavior was restored. I can now mount the USB3 hard drive and access the files.

But thank you jetchisel, I have a cheap hub standing by for next time.

And all you other folk, thank you as well.

Moving to Tumbleweed in 10 minutes time

I’m a bit slow with getting into Tumbleweed swing, and I posted this originally in Hardware, but I see it now as a Tw problem. The wretched thing again stopped working. It stopped auto-displaying its presence in my KDE systray Device Notifier and so I cannot click-to-mount it again. In fact I cannot mount it at all, again. This happened after a kernel upgrade today via zypper dup.

If I follow jetchisel’s advice and connect the usb3 drive via a cheap usb hub, even that doesn’t help, although it did help with an earlier kernel, the one just replaced by the “zypper dup” process.

Any suggestions hot to get my storage drive back in service?.

Only just seen this thread since it moved to Tw, and I had not used my portable USB 3 HDD on Tw recently until today, although it has worked in the past on Tw.

It stopped auto-displaying its presence in my KDE systray Device Notifier and so I cannot click-to-mount it again. In fact I cannot mount it at all, again. This happened after a kernel upgrade today via zypper dup.

So I’m testing my device on Tw after a significant upgrade yesterday evening (GMT), including these changes: kernel-desktop, KDE 4.12 to 4.13, the usual nine gnome/gtk packages changing vendor (requiring 2nd zypper dup to revert), and Packman stuff. I expected problems (e.g. KDE 4.13), but so far not bad.

If I follow jetchisel’s advice and connect the usb3 drive via a cheap usb hub, even that doesn’t help, although it did help with an earlier kernel, the one just replaced by the “zypper dup” process.

Can’t really comment on that, except to state that I hot-plug my portable disk directly into a lenovo ThinkPad supporting with USB 2 (not 3).

I’m now on KDE 4.13.2 with my portable USB disk connected and working normally. The system tray thingy saw it, I selected to open in File Manager, Dolphin sees it and correctly reports capacity, used and available.

Assuming you are running with no priority changes to the main openSUSE repos and the Tumbleweed repo, I can only suggest you make sure to run that second zypper dup if you haven’t already, or in the case where you have reverted any individual packages back to standard openSUSE sources.

Yep I’ve got the full install plus another dup 12 hours later and just now. KDE like yours and kernel 3.15.1-34.gee8dd2b-desktop and re-dups for the reversions. And the USB3 portable just won’t work. I just now copied all of its contents to a 1Tb USB2 portable drive that I had formatted specially to ext4 so it won’t drift around the house to other ppl’s computers. That filesystem and USB version works of course, so problem is not solved but it is avoided.

When I put a USB3 SanDisk thumb drive into the same USB socket as the faulty (?) USB3 drive, well the SanDisk leaps into action, no problem.

So that lead me to think maybe the big USB drive is dodgy. So I changed the volume name in my windows box so Linux might perhaps see it differently.OpenSUSE 13.1 still doesn’t see it. So in my windows box I deleted the partition and then reconstructed it (NTFS again). openSUSE 13.1 can’t see it.

So I’m putting it in the back of a desk where I can’t see it either.

Sounds like we are in step at this point. :slight_smile:

So that lead me to think maybe the big USB drive is dodgy. So I changed the volume name in my windows box so Linux might perhaps see it differently.OpenSUSE 13.1 still doesn’t see it. So in my windows box I deleted the partition and then reconstructed it (NTFS again). openSUSE 13.1 can’t see it.

So I’m putting it in the back of a desk where I can’t see it either.

So it works on a different Windows box? Using the same USB connecting lead? I guess you would be familiar with all that stuff anyway. Puzzling but out of site then. :smiley:

I forget to mention my portable disk is still NTFS, as originally supplied, and also used ok on Win7.

It even works on the openSUSE box if I revert openSUSE all the way back from Tumbleweed to openSUSE 13.1 (I have an image from before my first Tw zipper dup). It also works on other boxes belonging to my family if I boot into Knoppicx live CD on those boxes.

In conclusion: it’s probably a kernel bug with USB3 as suggestedjames
to me earlier.