Suse 13.1 32 bit: usb disk not recognized after recommnded updates

To

**Message body**

Please report the following to https://en.opensuse.org/openSUSE:Submitting_bug_reports
The following bug report has been submitted:

Name: philippe bopp
Company: For Personal Use
Address: 21 rue du petit bois
Email: philippebopp@yahoo.com
Phone: 0556680270
Product:
Patch Level:
Defect: seagate usb drive not recognized after system update suse 13.1 32 bit
Other Software and Versions Being Used: none
Steps to Duplicate: the seagate drive that worked perfectly before the update is now neither recognized nor monted

dmesg
5679.108101] usb 2-3: new SuperSpeed USB device number 3 using xhci_hcd 5679.125026] usb 2-3: New USB device found, idVendor=0bc2, idProduct=2321 5679.125034] usb 2-3: New USB device strings: Mfr=2, Product=3, SerialNumber=1 5679.125038] usb 2-3: Product: Expansion 5679.125041] usb 2-3: Manufacturer: Seagate 5679.125044] usb 2-3: SerialNumber: NA4BKTY3

usb sticks are recognized and mounted correctly

the Seagate drive is recognzed and mounted correctly on Bio-linux, WINDOWS, and Macs

Other Scenarios: No
Environment Description: after a (recommned) update (which, as far as I can see, zypper) went OK
Problem Environment: Don’t know Testing Environment: Didn’t try that
Fix: no solution found
Additional: none

You are welcome here when you have technical problems/questions about openSUSE which you want to discuss with your fellow openSUSE users. But what is the meaning of the above?

that I would like to know

  • whether anybody experience similar problems after recent updates (4 or 5 days ago)
  • what can be done about it, e.g.
    – what mignt have gon wrong during the update
    – which library/component might be corrupted and need fixing/re-install/go back to earlier version
    – what other test(s) may be useful
    – anything that may help getting it to work like it did before

Philippe

I do not know if anybody but you experiences this. What I know is that the forums are not swamped by people having the same (as you can see for yourself).
In any case, I have an openSUSE 13.1, patched today, running KDE and connecting an USB mass-storage device works as expected (the pop-up apears and clicking on Open with Dolphin does open it with Dolphin).

We first have to find out what is wrong in your situation.

No idea. I assume you mean with update eitther using zypper patch or YaST > Software > Online update. As said above, no problems here.

Again, no idea without further investigation.

Use

dmesg -w

connect the device and look for the messages that appear. Post what is added following the connection here for interpretation.

With the device connected

lsusb

and check if you see the device there. Again, when you want people here to help you interpreting it, post it.

As you are new here, I take the liberty to point you to the way to post copied/pasted computer texts in a post:
Please use CODE tags around copied/pasted computer text in a post. It is the # button in the tool bar of the post editor. When applicable copy/paste complete, that is including the prompt, the command, the output and the next prompt.

thanks for your answer: here the output of the commands


dmesg -w

 about 900 lines of output omtted. I don't see a way to attach the full output as a file to this message

  207.430388] usb 2-4: new SuperSpeed USB device number 2 using xhci_hcd
  207.447253] usb 2-4: New USB device found, idVendor=0bc2, idProduct=2321
  207.447261] usb 2-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
  207.447265] usb 2-4: Product: Expansion
  207.447268] usb 2-4: Manufacturer: Seagate
  207.447270] usb 2-4: SerialNumber: NA4BKTY3
[32909.033547] perf samples too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[49832.125671] perf samples too long (5069 > 5000), lowering kernel.perf_event_max_sample_rate to 25000

no prompt, must be cntrl-c ed to end


I find similar message by GOOGLEing for fedora, nothing for Suse
https://bugzilla.redhat.com/show_bug.cgi?id=1013708
(and I don’t understand what they say)



linux-fyvj:/home/pab # lsusb
Bus 002 Device 002: ID 0bc2:2321 Seagate RSS LLC 
Bus 003 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 004 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 003: ID 138a:003d Validity Sensors, Inc. 
Bus 003 Device 004: ID 046d:c077 Logitech, Inc. 
Bus 003 Device 005: ID 1f75:0916 Innostor Technology Corporation 
Bus 004 Device 003: ID 0a5c:21e1 Broadcom Corp. HP Portable SoftSailing
linux-fyvj:/home/pab # 


so as ar as i understand it, it is there: Bus 002 Device 002

thanks

Philippe

Thanks, most useful.

I think the main thing we are missing here is a line like (this is from an example at my system):

 2886.889164] usb-storage 1-7:1.0: USB Mass Storage device detected

As long as the system does not detect this as a Mass Storage device, nothing will work (no device files created by udevd, etc. etc.).

The big question is now: why oh why?

Did you use this device earlier with success?

Do you have similar dervices (USB mass storage of any kind) which you can try?

When this had been a camera, I would have said to check if the camera is switched to mass storage because cameras also can be on PTP. but I assume that is nt the case here.

I typed my answers in bold in the Quote environment provided automatically
since I don’t know how to do it otherwise

Thank you very much

I doubt it is the size of te disk. As long as it is not seen as Mass Storage, things like partitioning, file systems and their size are very secundary.

BTW, a mouse is not realy Mass Storage ;).

BTW, did you see the line (and more lines following) in dmesg when you connect a device that is detected as Mass Storage. It will give you an idea on what it should look like.

The negative site of this is that I have no idea now where to look further. To recap::
Most Mass Storage devices are detected as such on your openSUSE 13.1.
This device isn’t now, but it was in the past (until about 5 days ago) and it is working in other operating systems.
You blame a patch that was installed about 5 days ago.

Let us wait if others here have suggestions. I think we gathered some hard information to begin with.

thank you

yes, this summarizes the situation precisely.

I saw the lines from dmesg for the other usb devices (essentially 5 different usb sticks) I don’t really understand them, tried to google, up to now to no avail.

I can’t exlain all of those lines to the last detail either, but they all point to actions that belong to mass storage/disk handling. The key message is the one with the words Mass Storage in it. When that fails all fails :frowning:

And it is strange, because the fact that it is Mss Storage is not something magicaly invented by the system, it is something that the device sends back over the USB when requested for it’s details.

as annecdotal evidence that something went wrong during the update: the Asian fonts for my web browser
have disappeared as I just realized when I went to a Korean site .
Thanks for your help

Please create a new thread for your problem. You post only confuses the thread here.

Hallo,
I have got the same Problem. Everything worked before hand.
I think the the recommended update to vmlinuz-3.12.53-40-desktop on 26 february
caused the problem.
I have still a bootable Suse 12.1 on the same computer, which sees
the external disk without problem.

As I need that disk, I’d like to try the saved kernel - any advice ?

thanks in advance

Gerhard

dmesg -w

[10827.357484] usb 1-6: new high-speed USB device number 2 using ehci-pci
[10827.475729] usb 1-6: New USB device found, idVendor=174c, idProduct=55aa
[10827.475741] usb 1-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[10827.475748] usb 1-6: Product: MEDION HDDrive2GO
[10827.475754] usb 1-6: Manufacturer: MEDION
[10827.475759] usb 1-6: SerialNumber: 31700000000000006802

lsusb

Bus 001 Device 002: ID 174c:55aa ASMedia Technology Inc. ASMedia 2105 SATA bridge
Bus 002 Device 002: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
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

Hello,

when booting with advanced options, I can choose the older kernel
vmlinux-3.11.10-34-desktop (64 bit).
Now I can use my usb - disk again.
Below the are messages for the successfull detection of my usb disk.

kernel:   211.726895] usb 1-6: USB disconnect, device number 2
 kernel:   211.731152] sd 6:0:0:0: [sdb] Synchronizing SCSI cache
 kernel:   211.731243] sd 6:0:0:0: [sdb] 
 kernel:   211.731249] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
 kernel:   224.662186] usb 1-6: new high-speed USB device number 3 using ehci-pci
 kernel:   224.780421] usb 1-6: New USB device found, idVendor=174c, idProduct=55aa
 kernel:   224.780433] usb 1-6: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 kernel:   224.780440] usb 1-6: Product: MEDION HDDrive2GO
 kernel:   224.780446] usb 1-6: Manufacturer: MEDION
 kernel:   224.780451] usb 1-6: SerialNumber: 31700000000000006802
 kernel:   224.780865] usb-storage 1-6:1.0: USB Mass Storage device detected
 kernel:   224.781756] usb-storage 1-6:1.0: Quirks match for vid 174c pid 55aa: 400000
 kernel:   224.781778] scsi8 : usb-storage 1-6:1.0
 mtp-probe: checking bus 1, device 3: "/sys/devices/pci0000:00/0000:00:12.2/usb1/1-6"
 mtp-probe: bus: 1, device: 3 was not an MTP device

Well, when you can prove as hard as this that it worled in the earlier kernel, it could be time to file a bug at https://bugzilla.opensuse.org/index.cgi
(you can use the same username/password as here on the forums).

Please post a link to the bug report here, so others can follow what happens and add their comments.

I tried to do that, but I don’t understandd 50% of the questions/stuff it asks. I hope what I did makes any sense

going back from kernel 3.12.53-40-default to 3.11.10-29-default solved this problem,
the disk is now recognized normally

Thus you can now add two sequences of dmesg lines generated during connection (one can still be copied from the earlier post here), to illustrate your bug. That is strong evidence. Only the kernel didders, hardware and rest of the system the same.


Suse:/home/pab> dmesg
   61.311438] usb 2-4: new SuperSpeed USB device number 4 using xhci_hcd
   61.328189] usb 2-4: New USB device found, idVendor=0bc2, idProduct=2321
   61.328192] usb 2-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
   61.328194] usb 2-4: Product: Expansion
   61.328195] usb 2-4: Manufacturer: Seagate
   61.328196] usb 2-4: SerialNumber: NA4BKTY3
   61.356651] usb-storage 2-4:1.0: USB Mass Storage device detected
   61.356758] scsi6 : usb-storage 2-4:1.0
   61.357064] usbcore: registered new interface driver usb-storage
   62.356863] scsi 6:0:0:0: Direct-Access     Seagate  Expansion        0502 PQ: 0 ANSI: 6
   62.357044] sd 6:0:0:0: Attached scsi generic sg2 type 0
   62.360315] sd 6:0:0:0: [sdb] Spinning up disk...
   63.364797] ...ready
Suse:/home/pab>

the old one (copied from above) was



  207.430388] usb 2-4: new SuperSpeed USB device number 2 using xhci_hcd
  207.447253] usb 2-4: New USB device found, idVendor=0bc2, idProduct=2321
  207.447261] usb 2-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
  207.447265] usb 2-4: Product: Expansion
  207.447268] usb 2-4: Manufacturer: Seagate
  207.447270] usb 2-4: SerialNumber: NA4BKTY3
[32909.033547] perf samples too long (2508 > 2500), lowering kernel.perf_event_max_sample_rate to 50000
[49832.125671] perf samples too long (5069 > 5000), lowering kernel.perf_event_max_sample_rate to 25000

It is fine to post that here, but I hope you did that also in your bug report.