Quad Hat - Disks immediately ejecting - Quad Hat - Raspberry Pi 4B

Hi,
I have set up a Quad Hat with a 65W power supply with my Raspberry Pi on Raspbian and 1x 3.5" HDD.
When starting the Radxa service the drive gets mounted, but then 1-2 seconds later are dismounted and I get an “Error mounting /dev/sda2 at /media/pi/[name]: Unknow error when mounting /dev/sda2” message.

I have tested using different power supplies, using 4 drives, using 1 drive.
If I am very quick I am able to open the drive before it ejects and the folders are there.

Any ideas on what to check next?

Results from dmesg:

[ 2058.807112] usb 2-2: new SuperSpeed Gen 1 USB device number 3 using xhci_hcd
[ 2058.838558] usb 2-2: New USB device found, idVendor=152d, idProduct=0561, bcdDevice=81.36
[ 2058.838578] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=5
[ 2058.838594] usb 2-2: Product: External Disk 3.0
[ 2058.838609] usb 2-2: Manufacturer: JMicron
[ 2058.838624] usb 2-2: SerialNumber: RANDOM__3F4917AD758C
[ 2058.848802] scsi host0: uas
[ 2058.850293] scsi 0:0:0:0: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
[ 2058.852120] sd 0:0:0:0: Attached scsi generic sg0 type 0
[ 2058.853399] sd 0:0:0:0: [sda] 35156656128 512-byte logical blocks: (18.0 TB/16.4 TiB)
[ 2058.853680] sd 0:0:0:0: [sda] Write Protect is off
[ 2058.853698] sd 0:0:0:0: [sda] Mode Sense: 67 00 10 08
[ 2058.854268] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, supports DPO and FUA
[ 2058.855112] sd 0:0:0:0: [sda] Optimal transfer size 33553920 bytes
[ 2058.942995] Alternate GPT is invalid, using primary GPT.
[ 2058.943045] sda: sda1 sda2
[ 2058.947167] sd 0:0:0:0: [sda] Attached SCSI disk
[ 2067.158438] usb 2-2: USB disconnect, device number 3
[ 2067.237894] blk_update_request: I/O error, dev sda, sector 28160002344 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
[ 2067.238045] blk_update_request: I/O error, dev sda, sector 28160002344 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238070] Buffer I/O error on dev sda2, logical block 296, async page read
[ 2067.238145] blk_update_request: I/O error, dev sda, sector 28160002345 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238166] Buffer I/O error on dev sda2, logical block 297, async page read
[ 2067.238235] blk_update_request: I/O error, dev sda, sector 28160002346 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238254] Buffer I/O error on dev sda2, logical block 298, async page read
[ 2067.238330] blk_update_request: I/O error, dev sda, sector 28160002347 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238350] Buffer I/O error on dev sda2, logical block 299, async page read
[ 2067.238417] blk_update_request: I/O error, dev sda, sector 28160002348 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238436] Buffer I/O error on dev sda2, logical block 300, async page read
[ 2067.238506] blk_update_request: I/O error, dev sda, sector 28160002349 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238526] Buffer I/O error on dev sda2, logical block 301, async page read
[ 2067.238592] blk_update_request: I/O error, dev sda, sector 28160002350 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238612] Buffer I/O error on dev sda2, logical block 302, async page read
[ 2067.238683] blk_update_request: I/O error, dev sda, sector 28160002351 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238702] Buffer I/O error on dev sda2, logical block 303, async page read
[ 2067.238820] blk_update_request: I/O error, dev sda, sector 28160002344 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
[ 2067.238840] Buffer I/O error on dev sda2, logical block 296, async page read
[ 2067.238912] Buffer I/O error on dev sda2, logical block 297, async page read
[ 2067.296648] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 2067.928065] sd 0:0:0:0: [sda] Synchronize Cache(10) failed: Result: hostbyte=0x07 driverbyte=0x00

Edit:
lsusb

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Edit: The same happens when trying to mount a single SSD (so very unlikely to be power supply).

Hi, Hatter

Please check if the USB bridge is plugged in tightly. In addition, you can find a portable hard drive to test the USB interface of the Raspberry Pi.

Is a replacement USB bridge available?

Also could I use 2 male-male USB cables to connect the ports. Could that work?

The tolerance for the bridge when the case is on are very tight. Try for a while with the case off so you can fully seat the bridge. If you still have the problem then it will be the bridge or the connection on the pin or the board.

If it does work then you may be able to adjust the screws on the pi.,the board and the case.

Be really nice to have a few more millimetres on the bridge plugs so fully seated it would be impossible for the case to get in the way.

I am testing it without the case and have carefully aligned the usb ports to no avail.

Sorry to hear that. Other threads talk about the cables to use to try that kind of connection. I haven’t done it myself but I think that the cable is not a straight through.

@setq indicates in “ssd not visible in OMV6 neither in the terminal”.

Do you have an A-A cable? You can use to connect a computer to the hat or the raspberry pi to the hat.

I have no cable at the moment. Has anyone done it succesfully?