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

English Hardware
1

this is reposted from 2016, please seee below

The following bug report has been submitted:

Name: philippe bopp
Company: For Personal Use
Address: 21 rue du petit bois
Email: do not post e-mails in the open
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

see for details:
https://forums.opensuse.org/showthread.php/516848-Suse-13-1-32-bit-usb-disk-not-recognized-after-recommnded-updates
https://forums.opensuse.org/showthread.php/516848-Suse-13-1-32-bit-usb-disk-not-recognized-after-recommnded-updates/page2

New text:

This problem was kindly solved in spring 2016, I think by Mr van Velden recommending to edit
some file that controls the recognition/mounting process for this particular disk.
I followed the recommendation and everything worked perfectly well until I had to reinstall the system.

Now I realize that I cannot find again (e-mail, this forum) what this recommendation was. (stupid of me, I may just have bookmarked it)
I also cannot find the bugreport, which I filed at the time (and which may contain the answer)

If Mr van Velden (or anybody) can briefly look at this thread and recall/find/ what the recommendation was, or may have been
(edit this file such and such)
I would be very grateful if you’ld let me know

Philippe

2

As I said in the other thread:

What happened there is that a newer kernel version did not detect the device as being mass-storage (an older kernel did that correct). My advice was to create a bug report. I do not know if that was done, but there is no link to a bug report published in the thread.

I nowhere see that I advised any edit to (presumably) /etc/fstab. That would have been pointless, because there was no mass storage device detected, let alone that anything from it could be mounted ny any means.

So, I am still alive and kicking, but I have no idea what happened three years ago, apart from what I see in the thread. :frowning:

To make it short:

  1. there is no mentioning of any file to be edited in the thread;
  2. I do use the PM feature of the forums, but only as a mod to inform members about forum usage, like CODE tags *), never for technical information because that should be in threads that everyone can read, thus there was no PM about this problem;
  3. I never use (or even know) the e-mail addresses of any member, thus there can not be an e-mail from me about this problem (mark: you published your e-mail address above, that is an invitation to spam, following forum conventions I have removed it);
  4. it now shows this is about openSUSE 13.1 which is long out of support and not many members here will have one available to even try if they can reproduce your problem oe see what certain configuration files contain.

Your almost unreadable dmesg copy (again *)), does not contain any phrase that this is a mass storage device. Thus we are at the same point as in the 1916 thread.
When a bug report was filed in 1916, try to find it, because it may contain what you need.
When there was no bug report filed in 1916, then the possibility to do that has gone forever, because you can not file a bug report any more against openSUSE 13.1.

The best thing is to go for openSUSE 15.1 asap.

================
*)
There is an important, but not easy to find feature on the forums.

Please in the future 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.

An example is here: Using CODE tags Around your paste.

3

OP’s bug report describes editing to be done.

Surely this would not still be necessary in 15.1.

4

Briliant you found the bug report.