Opensuse 13.1 - Unable to mount USB Drive

The device is a Seagate Backup Plus 4TB USB 3.0 Portable HDD STDR4000300.

Intended use is as backup drive for a server running Opensuse 13.1 KDE.

The device auto-mounts normally under Opensuse 42.2 KDE but not under Opensuse 13.1 KDE.

The following diagnostic output obtained under Opensuse 13.1 may assist:

# dmesg | tail 1549.784989] usb 2-1.8: Product: BUP BK
 1549.784991] usb 2-1.8: Manufacturer: Seagate
 1549.784994] usb 2-1.8: SerialNumber: NA7P0T05
 2026.847263] usb 2-1.8: USB disconnect, device number 11
 5602.798382] usb 2-1.8: new high-speed USB device number 12 using ehci-pci
 5602.943812] usb 2-1.8: New USB device found, idVendor=0bc2, idProduct=ab28
 5602.943818] usb 2-1.8: New USB device strings: Mfr=2, Product=3, SerialNumber=1
 5602.943821] usb 2-1.8: Product: BUP BK
 5602.943823] usb 2-1.8: Manufacturer: Seagate
 5602.943826] usb 2-1.8: SerialNumber: NA7P0T05


# lsmod |grep usb 
usb_storage            62302  0 
dvb_usb_dib0700       144311  7 
dib7000p               38420  3 dvb_usb_dib0700
dib0090                38185  1 dvb_usb_dib0700
dib7000m               22858  1 dvb_usb_dib0700
dib0070                18232  3 dvb_usb_dib0700
dvb_usb                28311  1 dvb_usb_dib0700
dib8000                61498  1 dvb_usb_dib0700
dvb_core              125658  3 dib7000p,dvb_usb,dib8000
dib3000mc              23239  1 dvb_usb_dib0700
rc_core                32171  4 rc_dib0700_rc5,dvb_usb_dib0700,dvb_usb
dibx000_common         18752  5 dvb_usb_dib0700,dib7000p,dib7000m,dib8000,dib3000mc
snd_usb_audio         159188  1 
snd_usbmidi_lib        25137  1 snd_usb_audio
snd_rawmidi            35110  1 snd_usbmidi_lib
snd_hwdep              13602  2 snd_usb_audio,snd_hda_codec
snd_pcm               110211  6 snd_usb_audio,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_pcm_oss
snd                    87596  27 snd_usb_audio,snd_usbmidi_lib,snd_rawmidi,snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm_oss,snd_pcm,snd_seq,snd_seq_device,snd_timer,snd_mixer_oss


# lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 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:0002 Linux Foundation 2.0 root hub                                                                                                                          
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub                                                                                                                          
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub                                                                                                                          
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub                                                                                                                          
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub                                                                                                                          
Bus 002 Device 003: ID 0ac8:c315 Z-Star Microelectronics Corp.                                                                                                                          
Bus 002 Device 004: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB                                                                                                                 
Bus 002 Device 005: ID 1415:0003 Nam Tai E&E Products Ltd. or OmniVision Technologies, Inc.                                                                                             
Bus 002 Device 006: ID 045e:0039 Microsoft Corp. IntelliMouse Optical                                                                                                                   
Bus 002 Device 012: ID 0bc2:ab28 Seagate RSS LLC  

The device is not listed by fdisk -l and not shown by Yast Partitioner.

How can I mount this device under Opensuse 13.1 KDE?

[Sorry, can’t fix error in subject line.]

Leap is using a much later kernel, so if you really wanted to stay with openSUSE 13.1 you’d need to upgrade the kernel. You should be aware that 13.1 is well past EOL though…

https://en.opensuse.org/Lifetime

Thanks. I’m very grateful for the Evergreen team’s support for 13.1 [patches and updates are still being uploaded to main repos] and I’m a bit lazy to rebuild the server until I have to. I would like to know more about kernel upgrade options if you would point me to relevant resources.

The Evergreen support will end within a few days (if not already), so you should reconsider your lazyness. :wink:

Also trying to move to a new kernel on 13.1 might not be easier (and certainly a dead alley) compared to upgrading to Leap 42.2.

Looks like a common sense consensus is building among respected responders, and I agree. I am running 42.2 on my main desktop but also dealing with lots of little annoyances (too minor to raise here) that don’t arise with oldschool 13.1.

In this case the older 13.1 kernel version seems be causing the problem. I have since tested with a laptop running 13.1 KDE (no automount, no /dev tree entry) and another system running windows 7 with service pack 1 (full automount service there, thank-you Microsoft).

I had hoped there may be a simple solution with some fs, usb or udev library missing from this old system. Seems it is not to be.

I am ever grateful for ‘down to earth’ support from all quarters of the globe on this wonderful forum.

Solution is simple:

As root, issue this command:

modprobe -v uas

If your external drive suddenly appears, it is because of a previous bug (now fixed) in uas.

As a result of the bug, then unresolvable, uas was blacklisted.

If the above command works, then edit /etc/modprobe.d/50-blacklist.conf and remark out the line (put a # & space at the front of the line):

blacklist uas

This mostly effects external HDs 3TB and larger.

… However, I still advise – as others here have – that you LEAP forward into the future.:wink:

I guess it’s worth a shot. I recall that bug, not sure that using uas is wise though (depending on kernel version)

Another option mentioned there that might also work…

  1. Keep uas blacklisted and allow usb-storage to be used for your UAS
    capable device. This can be achieved by adding line like

options usb-storage quirks=0xVVVV:0xPPPP:u

with VVVV and PPPP replaced by USB vendor and product id of your device
(these can be found in lsusb output on system where the device works) to
file /etc/modprobe.d/99-local.conf Again, run “mkinitrd -f” and reboot.

The bug was fixed and the patch brought down about a year ago. I have been using uas flawlessly on multiple external drives for almost that long, now. Throughput is (relatively) blazingly fast and passes all integrity checks.:wink:

For Evergreen? Good to know if that’s the case. The vast majority of us have moved on anyway :slight_smile:

Yep. One of our own members pulled it down to 13.1 back then.

Sounds like it will buy some procrastination time for our OP then :slight_smile:

… well … for me, too.lol!

Besides, as I outlined in a post awhile back, I will keep running 13.1 with kde4 for the multiple desktops with different widgets, panels, and backgrounds – and the beauty of “The Cube” – on my main working machine until (if, when) that function or very similar function is returned to kde5+. I just will keep that machine isolated in its own subnet.

Oh, yes, and for the ability to format times and dates, and a few other things, the way I like them – problem upstream from KDE to the QT peoples.

Thanks for the solution FB, and thanks also to DF for linking the relevant mail-list report.

Trust this is helpful for other openSUSE 13.1 KDE4 procrastinators. Perhaps a kindly mod could correct the OP subject line error if time permits.

Done (but only the main title, not the intermediate replies).