[SOLVED] uas module fails when trying to access external harddrive

powerOfSilence · 2017-05-23 08:59:14

I am trying to recover some data from an external harddrive. I'm using the SABRENT sata to usb 3.0 adapter.

When i plug in the adapter with the hdd, it doesn't show using

 lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0 465.8G  0 disk 
├─sda1   8:1    0 228.9G  0 part /
├─sda2   8:2    0     8G  0 part [SWAP]
└─sda3   8:3    0 228.9G  0 part /home

, however only on

lsusb
Bus 003 Device 002: ID 8087:8000 Intel Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 012: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. 
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 13d3:5652 IMC Networks 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

. JMicron Technology is the target. I've searched around here and stack exchange, but to no avail.

My dmesg shows:

[ 3040.788681] xhci_hcd 0000:00:14.0: Cannot set link state.
[ 3040.788687] usb usb2-port1: cannot disable (err = -32)
[ 3040.788692] usb 2-1: USB disconnect, device number 11
[ 3041.872066] usb 2-1: new SuperSpeed USB device number 12 using xhci_hcd
[ 3041.893238] scsi host4: uas
[ 3041.894121] scsi 4:0:0:0: Direct-Access     SABRENT                   0204 PQ: 0 ANSI: 6
[ 3044.365931] Dropped: IN=wlp7s0 OUT= MAC=ff:ff:ff:ff:ff:ff:78:0c:b8:5c:b9:b7:08:00 SRC=192.168.1.9 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=10744 PROTO=UDP SPT=137 DPT=137 LEN=58 
[ 3045.184840] Dropped: IN=wlp7s0 OUT= MAC=ff:ff:ff:ff:ff:ff:78:0c:b8:5c:b9:b7:08:00 SRC=192.168.1.9 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=10745 PROTO=UDP SPT=137 DPT=137 LEN=58 
[ 3045.799163] Dropped: IN=wlp7s0 OUT= MAC=ff:ff:ff:ff:ff:ff:78:0c:b8:5c:b9:b7:08:00 SRC=192.168.1.9 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=10746 PROTO=UDP SPT=137 DPT=137 LEN=58 
[ 3047.872229] sd 4:0:0:0: [sdb] Unit Not Ready
[ 3047.872232] sd 4:0:0:0: [sdb] Sense Key : 0x4 [current] 
[ 3047.872234] sd 4:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
[ 3047.872769] sd 4:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
[ 3047.872772] sd 4:0:0:0: [sdb] Sense Key : 0x4 [current] 
[ 3047.872773] sd 4:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
[ 3047.873146] sd 4:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
[ 3047.873148] sd 4:0:0:0: [sdb] Sense Key : 0x4 [current] 
[ 3047.873149] sd 4:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
[ 3047.873520] sd 4:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
[ 3047.873521] sd 4:0:0:0: [sdb] 0-byte physical blocks
[ 3047.873878] sd 4:0:0:0: [sdb] Test WP failed, assume Write Enabled
[ 3047.873998] sd 4:0:0:0: [sdb] Asking for cache data failed
[ 3047.874001] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 3047.874804] sd 4:0:0:0: [sdb] Unit Not Ready
[ 3047.874806] sd 4:0:0:0: [sdb] Sense Key : 0x4 [current] 
[ 3047.874807] sd 4:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
[ 3047.875758] sd 4:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08
[ 3047.875764] sd 4:0:0:0: [sdb] Sense Key : 0x4 [current] 
[ 3047.875767] sd 4:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
[ 3047.876192] sd 4:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=0x00 driverbyte=0x08
[ 3047.876194] sd 4:0:0:0: [sdb] Sense Key : 0x4 [current] 
[ 3047.876195] sd 4:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
[ 3047.877422] sd 4:0:0:0: [sdb] Attached SCSI disk

Ignore the dropped packets, that is just my firewall. I've tried to disable uas using

modprobe -rf uas

but it always keeps reloading. What am i doing wrong?

UPDATE 1:
After taking into account all the replies, i put the external hdd into one of my desktops and lo and behold, boots into Windows Xp. I have a few others i will need to try, some of which are also ide. So does this mean i won't be able to access these same hdd using a sata to usb adapter? I was really hoping to use my Arch since it will be easier to carry around (laptop).

SOLUTION: Based from answers below and new experience, cannot use an adapter for external harddrives to connect to computer when using internal harddrives.

Last edited by powerOfSilence (2017-10-15 03:57:14)

tom.ty89 · 2017-05-23 11:14:33

See if disabling UAS for that device can be a workaround:

options usb-storage quirks=152d:1561:u

Put that in a conf under /etc/modprobe.d

IIRC, there's no way you can "globally" disable UAS, as long as UAS support is included when the kernel was built (even if it is built as module). I recall asking that on linux-usb mailing list as well.

Last edited by tom.ty89 (2017-05-23 11:15:46)

R00KIE · 2017-05-23 14:50:43

I suspect your problem here is not uas, you mention data recovery, have you tried connecting the disk directly to a sata port?

Was the disk at least being recognized by the equipment it was connected to before or was it inside an external enclosure that died? If you provide more details (such as disk type, if it was working before or if it works when connected somewhere else, smart status if you manage to get it) we might be able to point you in the right direction, otherwise we'll be here playing a 20 questions game until we find the right answer.

powerOfSilence · 2017-05-23 17:43:33

The hdd i am trying to access is a Seagate from a desktop, and i am currently using a sata to usb adapter to connect from my laptop. I don't see a way to connect directly to my laptops sata port. The external hdd was not being seen by it's original hardware because of other hardware failures, so i wanted to see if the hdd was salvagable. So if i can see the hdd in my lsusb, does'nt that mean it should be accessable?

R00KIE · 2017-05-23 18:21:57

What you see in the output of lsusb is the bridge chip not your disk, I suspect that you would still see it even if there is no disk attached. From your incomplete dmesg output I see "Read Capacity(16) failed: Result: hostbyte=0x00 driverbyte=0x08" and the messages that come before seem to indicate that the disk is not responding for some reason. The last message does say "Attached SCSI disk" but the output does not list any partitions, which I suspect is not what you are expecting.

It might be just some incompatibility between the bridge chip and the disk (not very likely but possible) or maybe the disk is taking longer to respond because it is not 100% ok, that is why I suggested that you connect it directly to a sata port (obviously only if you have easy access to one) so that you cut out the middle man. On the other hand there is nothing stopping you from testing tom.ty89's suggestion and see if it helps.

powerOfSilence · 2017-05-23 18:39:01

@tom.ty89 I added the modprobe.conf with the exact code, and double checked on the hexes, rebooted, and my dmesg says:

[ 2574.336442] usb 2-3: new high-speed USB device number 6 using xhci_hcd
[ 2574.541265] usb 2-3: UAS is blacklisted for this device, using usb-storage instead
[ 2574.541270] usb-storage 2-3:1.0: USB Mass Storage device detected
[ 2574.541436] usb-storage 2-3:1.0: Quirks match for vid 152d pid 1561: 800000
[ 2574.542053] scsi host4: usb-storage 2-3:1.0
[ 2575.554003] scsi 4:0:0:0: Direct-Access     SABRENT                   0204 PQ: 0 ANSI: 6
[ 2576.820476] Dropped: IN=wlp7s0 OUT= MAC=ff:ff:ff:ff:ff:ff:78:0c:b8:7b:e0:12:08:00 SRC=192.168.1.11 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32477 PROTO=UDP SPT=137 DPT=137 LEN=58 
[ 2577.434701] Dropped: IN=wlp7s0 OUT= MAC=ff:ff:ff:ff:ff:ff:78:0c:b8:7b:e0:12:08:00 SRC=192.168.1.11 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32478 PROTO=UDP SPT=137 DPT=137 LEN=58 
[ 2578.253910] Dropped: IN=wlp7s0 OUT= MAC=ff:ff:ff:ff:ff:ff:78:0c:b8:7b:e0:12:08:00 SRC=192.168.1.11 DST=192.168.1.255 LEN=78 TOS=0x00 PREC=0x00 TTL=128 ID=32479 PROTO=UDP SPT=137 DPT=137 LEN=58 
[ 2581.505765] sd 4:0:0:0: [sdb] Unit Not Ready
[ 2581.505771] sd 4:0:0:0: [sdb] Sense Key : 0x4 [current] 
[ 2581.505775] sd 4:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81

ignore the Dropped packets. So i didn't get any error about not being able to read disk and such from uas, then it still doesn't show. From what @R00kie was saying, i'll see if i can take apart my other desktop server and put in the external hdd that way.

powerOfSilence · 2017-05-23 20:43:28

You know what, im such an airhead. The adapter says 2.5 inch sata hdd to usb. It works on the hdd i took out of a laptop, which is 2.5. The desktop hdd, even though they can fit the sata port, is not 2.5 inch, but 3 or 3.5. I guess i was just hoping to abuse the adapter and use it for anything that had the same ports. Thank you for all the input!

Slithery · 2017-05-23 20:46:45

That shouldn't make any difference, the adapter should work just as well with a 3.5" drive.

Last edited by Slithery (2017-05-23 20:47:15)

tom.ty89 · 2017-05-24 07:10:48

Well, can you feel the 3.5" HDD spinning when it is attached to the adapter? Also, do the same errors show up if the adapter is connected to the computer _without_ a HDD attached to it?

IIRC some JMicron bridges have broken firmware that they cannot really be connected to a computer with no disk attached (i.e. no/broken hot plug support on the SATA end). If it cannot power up the 3.5" HDD, then it's equivalent to "no disk attached" I suppose.

@slithery, I beg to differ. SATA/USB adapter for 2.5" HDD/SDD usually does not allow external power, and an adapter like that cannot power up 3.5" HDD AFAIK. (not just the current requirement but also 12v rail thing or so)

R00KIE · 2017-05-24 10:47:42

If the adapter is trying to power the 3.5'' disk then it is no wonder that things are not working.

Arch Linux

#1 2017-05-23 08:59:14

[SOLVED] uas module fails when trying to access external harddrive

#2 2017-05-23 11:14:33

Re: [SOLVED] uas module fails when trying to access external harddrive

#3 2017-05-23 14:50:43

Re: [SOLVED] uas module fails when trying to access external harddrive

#4 2017-05-23 17:43:33

Re: [SOLVED] uas module fails when trying to access external harddrive

#5 2017-05-23 18:21:57

Re: [SOLVED] uas module fails when trying to access external harddrive

#6 2017-05-23 18:39:01

Re: [SOLVED] uas module fails when trying to access external harddrive

#7 2017-05-23 20:43:28

Re: [SOLVED] uas module fails when trying to access external harddrive

#8 2017-05-23 20:46:45

Re: [SOLVED] uas module fails when trying to access external harddrive

#9 2017-05-24 07:10:48

Re: [SOLVED] uas module fails when trying to access external harddrive

#10 2017-05-24 10:47:42

Re: [SOLVED] uas module fails when trying to access external harddrive

Board footer