Seagate Maxtor M3 USB external hdd.

English Hardware
1

Hi,

I have an old Opensuse 13.1 installed machine with all lattest updates and I was plugging a new Seagate Maxtor M3 external USB 4TB hard drive.
The drive showed up on lsub as:

Bus 003 Device 005: ID 0bc2:61b7 Seagate RSS LLC

but it did not show up on /dev.It was not possible to mount the drive.
fdisk -l did also of course not show any partitition or drive.
The loggin of the system did gave me some hints on what is going on.

 # tail -f /var/log/messages
2016-07-19T01:30:07.497169+01:00 cstark mtp-probe: bus: 2, device: 11 was not an MTP device
2016-07-19T01:32:24.644396+01:00 cstark kernel: [58666.469944] usb 2-1.7: USB disconnect, device number 11
2016-07-19T01:32:37.516382+01:00 cstark kernel: [58679.329237] usb 3-4: new high-speed USB device number 5 using xhci_hcd
2016-07-19T01:32:37.681180+01:00 cstark kernel: [58679.494729] usb 3-4: New USB device found, idVendor=0bc2, idProduct=61b7
2016-07-19T01:32:37.681192+01:00 cstark kernel: [58679.494732] usb 3-4: New USB device strings: Mfr=2, Product=3, SerialNumber=1
2016-07-19T01:32:37.681192+01:00 cstark kernel: [58679.494733] usb 3-4: Product: M3 Portable
2016-07-19T01:32:37.681193+01:00 cstark kernel: [58679.494735] usb 3-4: Manufacturer: Seagate
2016-07-19T01:32:37.681193+01:00 cstark kernel: [58679.494736] usb 3-4: SerialNumber: NA83M67A
2016-07-19T01:32:37.682747+01:00 cstark mtp-probe: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:14.0/usb3/3-4"
2016-07-19T01:32:37.682993+01:00 cstark mtp-probe: bus: 3, device: 5 was not an MTP device

The problem was the MPT …
As I have seen a lot of people on the searches I’ve made with the exact same problem on Seagate USB drives mainly I’ve found a quick solution for this problem in this link.

https://forums.mageia.org/en/viewtopic.php?f=41&t=9835

post #6, Simply load the uas Kernel module.

# modprobe uas

as soon as the module was loaded i got the popup windows to mount the drive.
I hope this helps people with the same problem I had.

Regards

2

Check the file

/etc/modprobe.d/50-blacklist.conf

In it, you will probably find the line

blacklist uas

Remark it out is probably a better choice than delete it, just in case:

# blacklist uas

If uas then gives you any problems, you would simply just remove the “#” from the line.

Now you should not have to run

modprobe uas

(which really ought to be

modprobe -v uas

anyway)

3

Hi,

Thanks for the tip I did not noticed that one.
Indeed it is blacklisted.

:slight_smile: and the comment is frightening …


# uas has been confirmed to be hopelessly broken
# Bug bnc#770301
# blacklist uas

There is also another option that many discuss about the same problem but in another Kernel version:
https://forums.opensuse.org/showthread.php/500377-Kernel-regression-Seagate-USB-HDD-doesn-t-work-since-kernel-3-15?p=2660340#post2660340

I did not try that one since simply enabling the uas Kernel module makes the disk work fine so far.

About the drive itself …well it is kinda slow writing but for those who need a compact storage device it’s ok.
At this moment I’ve already wrote on the all drive encrypted data like this:

openssl enc -aes-256-ctr -pass pass:"$(dd if=/dev/urandom bs=128 count=1 2>/dev/null | base64)" -nosalt < /dev/zero | pv -pterb > /dev/sdX

writing with /dev/urandom would take 8 days … and with /dev/random … I don’t want to even know :slight_smile:
Tip from:
http://serverfault.com/questions/6440/is-there-an-alternative-to-dev-urandom

And it took about 9 hours.
Now I’m formating the drive and it is going to take another 10H+ (checking for bad blocks)

In case the USB interface gives me problems I can simply open/dismantle the case and use it with another one I have that works fine (very cheap).
I can also use it as internal storage it costs less then any 3.5’ 4TB drive at the moment.

Regards.

4

AFAIK that bug has been patched in openSUSE and one of our Community members pulled the patch down to Evergreen (13.1) last March or April.

5

[quote="“Fraser_Bell,post:4,topic:120055”]

that’s why I love OpenSuSE for all these years … and Evergreen Rocks!

Regards.

6

… only for awhile longer, then Evergreen version 13.1 hits EOL. Personally, I am hoping the Evergreen team votes to extend the lifespan for awhile longer.:wink:

7

I wouldn’t count on it, since we now have Leap.

8

:slight_smile: Ummm …I think with the new Leap roadmap that will not happen sadly.
I also Wish that was the case …a bit more extending … but that I’m not sure will happen.
I also think Leap is a great idea. It was missing from OpenSuSE … a Stable long lasting version and then Tumbleweed for those who like the latest and greatest .
It saves some development effort for the developers and makes a stable version last longer that is a double win.
IMHO I think OpenSuSE and SuSE made a great move by sharing the server base on Leap.
For those like me that want a Stable long lasting Desktop for programming without going full SuSE enterprise type of deal this is indeed a very smart move.
Also off-topic … I also think SuSE would gain a Lot, like someone mentioned last year on the OpenSuSE conference, by having a …ouch … warning: bold proposal coming:
Centos Like Distro …
There. … :slight_smile: I’ve said it.
I understand Server Distros are way too different on purpose and perspective from our Desktop versions.
But for those who simply want to deploy a VM on a remote server or those services that offer hosting … having a Centos Like SLED would be a Big opportunity for future SLED contracts … imho …

Regards.

9

Hee, hee. I wasn’t.:wink:

… and, anyway, as far as I see it, the problem is not Leap, nor openSUSE, but the KDE group.