What is Reddit's opinion of ORICO SATA to USB 3.0 External Hard Drive Lay-Flat Docking Station for 2.5" or 3.5" HDD/SSD - Supports up to 8TB Drive?

From 3.5 billion Reddit comments

I've just started playing with my new Raspberry Pi 4 B / 2GB and I'm facing an issue that I don't know how to solve. I have connected HDD rack, powered one (Orico 6518US3) with a 1TB HDD from Toshiba.

The issue I have is when I reboot/shutdown, Raspberry Pi doesn't seem to see it at all, used command: sudo fdisk -l

Link to the rack - https://www.amazon.com/ORICO-External-Lay-Flat-Docking-Station/dp/B00CBPB4PM

It doesn't show on the list, it only shows the SD card.

I must say while it's not seen by the system, I hear the HDD still running so it's not a power problem. The rack has an On/Off button. If I turn the rack off and back on, the system sees it and also auto mounts it.

To me it looks like when I reboot/shutdown, the system doesn't tell the HDD to stop or something like that and when system boots again, HDD is stuck somehow until I turn rack off and back on.

Has anyone had this issue? Is there a way to fix?

The HDD is formatted as Ext4. Previously was in NTFS, but I reformatted it to get better speed. If I recall correctly, I didn't has this issue before reformatting it and previously was connected directly to my Asus WRT-AC66U router's USB 3.0 which also had no problem seeing it even after reboot.

Here's the relevant bit from dmesg:

[Oct 1 20:57] usb 1-1.2: USB disconnect, device number 4 [ +0.019460] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ +0.000052] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 02 6c 5e 90 00 00 f0 00 [ +0.000018] blk_update_request: I/O error, dev sda, sector 40656528 [ +0.000163] sd 0:0:0:0: [sda] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x01 driverbyte=0x00 [ +0.000041] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 02 6c 5f 80 00 00 10 00 [ +0.000026] blk_update_request: I/O error, dev sda, sector 40656768 [ +0.101707] Buffer I/O error on dev sda1, logical block 5081810, async page read [ +0.003409] Buffer I/O error on dev sda1, logical block 5081810, async page read [ +0.002885] Buffer I/O error on dev sda1, logical block 5081811, async page read [ +0.002089] Buffer I/O error on dev sda1, logical block 5081812, async page read [ +0.001972] Buffer I/O error on dev sda1, logical block 5081813, async page read [ +0.002254] Buffer I/O error on dev sda1, logical block 5081814, async page read [ +0.005511] Buffer I/O error on dev sda1, logical block 5081815, async page read [ +0.002082] Buffer I/O error on dev sda1, logical block 5081816, async page read [ +0.002858] Buffer I/O error on dev sda1, logical block 5081817, async page read [ +0.001375] Buffer I/O error on dev sda1, logical block 5084949, async page read [ +0.253391] usb 1-1.2: new high-speed USB device number 5 using dwc_otg [ +0.100717] usb 1-1.2: New USB device found, idVendor=2537, idProduct=1066 [ +0.000011] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ +0.000006] usb 1-1.2: Product: NS1066 [ +0.000006] usb 1-1.2: Manufacturer: Norelsys [ +0.000006] usb 1-1.2: SerialNumber: 0123456789ABCDE [ +0.000537] usb-storage 1-1.2:1.0: USB Mass Storage device detected [ +0.000185] scsi host1: usb-storage 1-1.2:1.0 [ +1.528712] scsi 1:0:0:0: Direct-Access NORELSYS 106X B550 PQ: 0 ANSI: 6 [ +0.001285] sd 1:0:0:0: Attached scsi generic sg0 type 0 [ +0.000062] sd 1:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/466 GiB) [ +0.000634] sd 1:0:0:0: [sdb] Write Protect is off [ +0.000022] sd 1:0:0:0: [sdb] Mode Sense: 43 00 00 00 [ +0.000515] sd 1:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [ +0.323464] sdb: sdb1 [ +0.002273] sd 1:0:0:0: [sdb] Attached SCSI disk

Based on this, it looks like the device got disconnected as a result of a bad block error (though the drive is brand new and has been verified to have no bad blocks). Then it redetects it as USB device #5 rather than USB device #4. After this output, the video stream stops buffering and the player (VLC, Plex etc) will report that it cannot find the file. lsblk now reports the device as sdb1. Could it be the SATA to USB/power adapter I'm using, perhaps? It's this one.