Sabrent 2.5 hd to usb 3.00 - not detected now, working before - kde

On my desktop, I replaced a magnetic drive with SSD. The MD drive was having problems, not sure if it was failing. I bought the above installed the MD (1tb) drive inside the device. I plugged in the usb, noting the blue light was on Then, I did a low level format with error checking on the command line, ntfs. After, It was working fine, writes and reads. I stored it for use later. Now, it’s about 1 year+ later. It’s not showing up on the usb list in the window. So, I did some research and found this page and other websites.

Also, I have an extra 512gb internal drive, but I need an external to transport around and for backup.

Trimming out for privacy and to not run out of space on the topic

#fdisk -l
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Device       Start        End    Sectors  Size Type
/dev/sda1     2048    1050623    1048576  512M EFI System
/dev/sda2  1050624 1953525134 1952474511  931G Linux LVM

Disk /dev/nvme0n1: 476.94 GiB, 512110190592 bytes, 1000215216 sectors

Device         Start     End Sectors  Size Type
/dev/nvme0n1p1  2048 1050623 1048576  512M EFI System

Disk /dev/mapper/system-swap: 15.45 GiB, 16588472320 bytes, 32399360 sectors

Disk /dev/mapper/system-root: 915.56 GiB, 983073554432 bytes, 1920065536 sectors

No External usb drive.

# lsusb
Bus 002 Device 002: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c069 Logitech, Inc. M-U0007 [Corded Mouse M500]
Bus 001 Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth
Bus 001 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 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

# lsblk
NAME            MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sdb               8:16   0     0B  0 disk 
nvme0n1         259:0    0 476.9G  0 disk 
└─nvme0n1p1     259:1    0   512M  0 part
# cat /proc/scsi/usb-storage-0/0
cat: /proc/scsi/usb-storage-0/0: No such file or directory
# dmesg | grep usb
[    2.455157] usbcore: registered new interface driver usbfs
[    2.455161] usbcore: registered new interface driver hub
[    2.455169] usbcore: registered new device driver usb
[    2.559675] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14
[    2.559683] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.559688] usb usb1: Product: xHCI Host Controller
[    2.559692] usb usb1: Manufacturer: Linux 5.14.21-150500.55.31-default xhci-hcd
[    2.559696] usb usb1: SerialNumber: 0000:00:14.0
[    2.565153] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14
[    2.565162] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.565167] usb usb2: Product: xHCI Host Controller
[    2.565171] usb usb2: Manufacturer: Linux 5.14.21-150500.55.31-default xhci-hcd
[    2.565175] usb usb2: SerialNumber: 0000:00:14.0
[    2.568444] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.14
[    2.568452] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.568456] usb usb3: Product: xHCI Host Controller
[    2.568460] usb usb3: Manufacturer: Linux 5.14.21-150500.55.31-default xhci-hcd
[    2.568463] usb usb3: SerialNumber: 0000:01:00.2
[    2.570556] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[    2.570612] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.14
[    2.570618] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[    2.570623] usb usb4: Product: xHCI Host Controller
[    2.570627] usb usb4: Manufacturer: Linux 5.14.21-150500.55.31-default xhci-hcd
[    2.570631] usb usb4: SerialNumber: 0000:01:00.2
[    2.823855] usb 1-3: new low-speed USB device number 2 using xhci_hcd
[    2.981078] usb 1-3: New USB device found, idVendor=046d, idProduct=c069, bcdDevice=56.01
[    2.981083] usb 1-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    2.981084] usb 1-3: Product: USB Laser Mouse
[    2.981085] usb 1-3: Manufacturer: Logitech
[    3.104069] usb 2-5: new SuperSpeed USB device number 2 using xhci_hcd
[    3.125235] usb 2-5: New USB device found, idVendor=152d, idProduct=1561, bcdDevice= 2.04
[    3.125249] usb 2-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[    3.125254] usb 2-5: Product: SABRENT
[    3.125258] usb 2-5: Manufacturer: SABRENT
[    3.125261] usb 2-5: SerialNumber: DB9876543214E
[    3.255935] usb 1-14: new full-speed USB device number 3 using xhci_hcd
[    3.406590] usb 1-14: New USB device found, idVendor=8087, idProduct=0026, bcdDevice= 0.02
[    3.406605] usb 1-14: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[    3.415978] usbcore: registered new interface driver usbhid
[    3.415980] usbhid: USB HID core driver
[    3.417197] input: Logitech USB Laser Mouse as /devices/pci0000:00/0000:00:14.0/usb1/1-3/1-3:1.0/0003:046D:C069.0001/input/input9
[    3.417246] hid-generic 0003:046D:C069.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Laser Mouse] on usb-0000:00:14.0-3/input0
[    6.064059] usbcore: registered new interface driver usb-storage
[    6.067632] usbcore: registered new interface driver uas
[    6.084157] usbcore: registered new interface driver btusb

No usb (sdb)’ on ‘# parted -l’ or ‘# blkid -o list’

Changed usb ports, nothing changed.

Need help…

Show activity in journal:

erlangen:~ # journalctl -b0 _KERNEL_SUBSYSTEM=scsi
...
Oct 24 08:31:40 erlangen kernel: scsi host12: usb-storage 2-4:1.0
Oct 24 08:31:41 erlangen kernel: scsi 12:0:0:0: Direct-Access     Generic  STORAGE DEVICE   0828 PQ: 0 ANSI: 6
Oct 24 08:31:41 erlangen kernel: sd 12:0:0:0: Attached scsi generic sg2 type 0
Oct 24 08:31:41 erlangen kernel: sd 12:0:0:0: [sdb] 63272960 512-byte logical blocks: (32.4 GB/30.2 GiB)
Oct 24 08:31:41 erlangen kernel: sd 12:0:0:0: [sdb] Write Protect is off
Oct 24 08:31:41 erlangen kernel: sd 12:0:0:0: [sdb] Mode Sense: 23 00 00 00
Oct 24 08:31:41 erlangen kernel: sd 12:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
Oct 24 08:31:41 erlangen kernel: sd 12:0:0:0: [sdb] Attached SCSI removable disk
erlangen:~ # 

Note, one of the solutions was to update the firmware. I have the windows download.

Plugin USB drive
turn on power - sabrent

# journalctl -b0 _KERNEL_SUBSYSTEM=scsi
localhost:~ #

Rebooting with power and connection. (cont)

# journalctl -b0 _KERNEL_SUBSYSTEM=scsi
Oct 24 00:25:17 localhost kernel: scsi host0: ahci
Oct 24 00:25:17 localhost kernel: scsi host1: ahci
Oct 24 00:25:17 localhost kernel: scsi host2: ahci
Oct 24 00:25:17 localhost kernel: scsi host3: ahci
Oct 24 00:25:17 localhost kernel: scsi host4: ahci
Oct 24 00:25:17 localhost kernel: scsi 4:0:0:0: Direct-Access     ATA      Samsung SSD 850  1B6Q PQ: 0 ANSI: 5
Oct 24 00:25:17 localhost kernel: scsi 4:0:0:0: Attached scsi generic sg0 type 0
Oct 24 00:25:17 localhost kernel: sd 4:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Oct 24 00:25:17 localhost kernel: sd 4:0:0:0: [sda] Write Protect is off
Oct 24 00:25:17 localhost kernel: sd 4:0:0:0: [sda] Mode Sense: 00 3a 00 00
Oct 24 00:25:17 localhost kernel: sd 4:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support>
Oct 24 00:25:17 localhost kernel: sd 4:0:0:0: [sda] Preferred minimum I/O size 512 bytes
Oct 24 00:25:17 localhost kernel: sd 4:0:0:0: [sda] supports TCG Opal
Oct 24 00:25:17 localhost kernel: sd 4:0:0:0: [sda] Attached SCSI disk
Oct 24 00:25:20 localhost.localdomain kernel: scsi host5: uas
Oct 24 00:25:20 localhost.localdomain kernel: scsi 5:0:0:0: Direct-Access     SABRENT                   0204 P>
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: Attached scsi generic sg1 type 0
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Unit Not Ready
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current] 
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Read Capacity(16) failed: Result: hostbyte=DID>
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current] 
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Read Capacity(10) failed: Result: hostbyte=DID>
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Sense Key : Hardware Error [current] 
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] ASC=0x44 <<vendor>>ASCQ=0x81 
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] 0 512-byte logical blocks: (0 B/0 B)
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] 0-byte physical blocks
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Test WP failed, assume Write Enabled
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Asking for cache data failed
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Assuming drive cache: write through
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Preferred minimum I/O size 4096 bytes not a mu>
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Optimal transfer size 33553920 bytes not a mul>
Oct 24 00:25:20 localhost.localdomain kernel: sd 5:0:0:0: [sdb] Attached SCSI disk

Hmm, HD not working or sabrent converter not working?

Yawn, tomorrow (my timezone) I will return.

I’ll just comment on my experience.

I have a similar SABRENT box, except it is for 3.5 inch drives. It is working well.

On my previous desktop, it was unreliable. After booting, it worked, but if the computer had been up for a while, it stopped working. The basic problem was the previous desktop would often see a USB3 port as just a USB2 port. I guess I bought that computer in the early days of USB3, and something in the hardware or BIOS didn’t fully support it.

I have a quite old Sabrent made for 3.5" using both USB and eSATA. With SATA it is reliable only with SATA. With USB, both PATA and SATA work as expected.

On mswin10, file transfers are 100-120 m/s. On every version past and present of opensuse on my laptop and desktop, it happens at about 5-25 m/s.

So, maybe the kernel has a bug with transfers. On the sabrent, the USB 3.00 is being seen as USB 2.00 and the sabrent won’t work.

This was working on a past version of opensuse. What do you think?

This Sabrent uses a sata connection.

How long is the cable? Is it v3 rated? Is the port v3 rated?

It has blue part on the interior. So, it’s USB v3.00 cable. I think it’s the one that came with it.

It’s possible the cable is bad. My audio cables went bad one day and I got a replacement, they then worked.

3’ cable. (foot)

When you wrote:

I took it to mean the connection to the PC, not to its storage disk. Thus I was referring to SATA v3 and eSATA cable. eSATA has a much shorter cable length limitation than does USB3, and higher cable quality requirement. I have yet to find a 3’ eSATA cable I could make work.

lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 10000M
    |__ Port 5: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

lsusb -t | egrep -i "storage" -B1
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 10000M
    |__ Port 5: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M

Note, if I read this correctly: 1 512gb - 2 1tb

lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/4p, 10000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/2p, 480M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 10000M
    |__ Port 5: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M
    |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 14: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 14: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M

lsusb -t | egrep -i "storage" -B1
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/8p, 10000M
    |__ Port 5: Dev 2, If 0, Class=Mass Storage, Driver=uas, 5000M

Note, if I read this correctly: 1 512gb - 2 1tb

When I compared the two hard drives shown in my question, I recognized that they are using different jumper configurations. Thus, I did some research on this and found the documentation about the jumper settings. I realized that the working hard drive was configured like in setting 3 for Reduced Power Spinup (RPS) enabled. I thought this might be interesting for me despite the fact that the spinup of my drive seemed to work correctly. I also found a datasheet about the RPS itself which is available here.

After changing the jumper settings for my not working disk to the one of my working disk I tried the 3 different enclosures again but could not get any working configuration. However, I hope that it at least helps some of you out there!

WIn10 drive needs to be formatted.

Backup to HDD on infamous host erlangen

The ST8000VN 004-2M2101 is either inserted into:

  1. a 5.25" trayless caddy or
  2. a USB-C Hard Drive Enclosure.

Both options are reliable and performant:

erlangen:~ # fdisk -l /dev/sdb
Disk /dev/sdb: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors
Disk model: 004-2M2101      
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 397AD234-1085-4808-8700-C070FD523831

Device     Start         End     Sectors  Size Type
/dev/sdb1   2048 15628053134 15628051087  7.3T Linux filesystem
erlangen:~ # 
erlangen:/HDD # findmnt /HDD 
TARGET
     SOURCE    FSTYPE OPTIONS
/HDD systemd-1 autofs rw,relatime,fd=58,pgrp=1,timeout=10,minproto=5,maxproto=5,direct,pipe_ino=30087
/HDD /dev/sdb1 btrfs  rw,nosuid,nodev,noexec,relatime,space_cache=v2,subvolid=5,subvol=/
erlangen:/HDD # 
erlangen:~ # journalctl -b -u btrbk-HDD.service 
Oct 25 07:49:36 erlangen systemd[1]: Starting btrbk backup of /home to HDD...
Oct 25 07:50:25 erlangen btrbk[4957]: --------------------------------------------------------------------------------
Oct 25 07:50:25 erlangen btrbk[4957]: Backup Summary (btrbk command line client, version 0.32.6)
Oct 25 07:50:25 erlangen btrbk[4957]:     Date:   Wed Oct 25 07:49:36 2023
Oct 25 07:50:25 erlangen btrbk[4957]:     Config: /etc/btrbk/btrbk-HDD.conf
Oct 25 07:50:25 erlangen btrbk[4957]: Legend:
Oct 25 07:50:25 erlangen btrbk[4957]:     ===  up-to-date subvolume (source snapshot)
Oct 25 07:50:25 erlangen btrbk[4957]:     +++  created subvolume (source snapshot)
Oct 25 07:50:25 erlangen btrbk[4957]:     ---  deleted subvolume
Oct 25 07:50:25 erlangen btrbk[4957]:     ***  received subvolume (non-incremental)
Oct 25 07:50:25 erlangen btrbk[4957]:     >>>  received subvolume (incremental)
Oct 25 07:50:25 erlangen btrbk[4957]: --------------------------------------------------------------------------------
Oct 25 07:50:25 erlangen btrbk[4957]: /
Oct 25 07:50:25 erlangen btrbk[4957]: +++ /Btrbk/btrbk_snapshots/HDD/ROOT.20231025T0749
Oct 25 07:50:25 erlangen btrbk[4957]: >>> /HDD/btrbk_snapshots/HDD/ROOT.20231025T0749
Oct 25 07:50:25 erlangen btrbk[4957]: /home
Oct 25 07:50:25 erlangen btrbk[4957]: +++ /Btrbk/btrbk_snapshots/HDD/home.20231025T0749
Oct 25 07:50:25 erlangen btrbk[4957]: >>> /HDD/btrbk_snapshots/HDD/home.20231025T0749
Oct 25 07:50:25 erlangen systemd[1]: btrbk-HDD.service: Deactivated successfully.
Oct 25 07:50:25 erlangen systemd[1]: Finished btrbk backup of /home to HDD.
Oct 25 07:50:25 erlangen systemd[1]: btrbk-HDD.service: Consumed 9.382s CPU time.
erlangen:~ # 

Dealing with shaky solutions isn’t worth the hassle.

Bus 002 Device 002: ID 152d:1561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS561U two ports SATA 6Gb/s bridge
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               3.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         9
  idVendor           0x152d JMicron Technology Corp. / JMicron USA Technology Corp.
  idProduct          0x1561 JMS561U two ports SATA 6Gb/s bridge
  bcdDevice            2.04
  iManufacturer           1 SABRENT
  iProduct                2 SABRENT
  iSerial                 3 DB9876543214E
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0079
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0x80
      (Bus Powered)
    MaxPower              896mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     80 Bulk-Only
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst              15
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst              15
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       1
      bNumEndpoints           4
      bInterfaceClass         8 Mass Storage
      bInterfaceSubClass      6 SCSI
      bInterfaceProtocol     98 
      iInterface              0 
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               0
        Command pipe (0x01)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               0
        MaxStreams             32
        Status pipe (0x02)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst              15
        MaxStreams             32
        Data-in pipe (0x03)
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x04  EP 4 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0400  1x 1024 bytes
        bInterval               0
        bMaxBurst               7
        MaxStreams             32
        Data-out pipe (0x04)
Binary Object Store Descriptor:
  bLength                 5
  bDescriptorType        15
  wTotalLength       0x0016
  bNumDeviceCaps          2
  USB 2.0 Extension Device Capability:
    bLength                 7
    bDescriptorType        16
    bDevCapabilityType      2
    bmAttributes   0x00000f0e
      BESL Link Power Management (LPM) Supported
    BESL value     3840 us 
  SuperSpeed USB Device Capability:
    bLength                10
    bDescriptorType        16
    bDevCapabilityType      3
    bmAttributes         0x00
    wSpeedsSupported   0x000e
      Device can operate at Full Speed (12Mbps)
      Device can operate at High Speed (480Mbps)
      Device can operate at SuperSpeed (5Gbps)
    bFunctionalitySupport   1
      Lowest fully-functional device speed is Full Speed (12Mbps)
    bU1DevExitLat          10 micro seconds
    bU2DevExitLat          32 micro seconds
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x000c
  (Bus Powered)
  U1 Enabled
  U2 Enabled
modprobe usb-storage

Null

It’s tough problem to solve… enough said. :wink:

Try and attach the drive to the motherboard.

I believe I have sata cables and room for another power connection. I’ve read that the unit may have stopped working.

Also, I’m going to be late responding, long work days.

I’ll try connecting on w10, ‘drive needs to be formatted’. I’ll try formatting it.

Also, It said the drive is write protected. So, I tested for read only. I got in a bad sector test (can’t recall the command). It reported a mismatch in free sectors and free sectors counted by it.

Blackhat advice: https://www.youtube.com/watch?v=KsYC4JOQAuw

There are two drivers - usb-storage and uas. You may test the other one, if it behaves better. Try booting with kernel parameter:

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

which should prevent using uas driver for this device.

Notes, I booted to windows10. Tried installing the sabrent firmware update. It worked two times in a row. That means the cable and the firmware/hardware works.

Two possible problems, the connection between the sata and HD is not working. The MD has failed.

I don’t hear the drive spinning up. It’s was at a low level, but I could hear it last time.

Drive will not format, “hardware error”.

How do i change the kernel parm?

(cont)