Drives not found after many issues

I received my quad kit and following the directions to build the kit and do the install of OMV, OMV failed.
Advice from someone at OMV said to install it without the hat and drives and that worked. I installed Raspian Buster lite, the Quad hat drivers and then OMV. That worked. I can get into OMV but there are no drives, of which I have 4 1tb Seagate hybrid drives.

systemctl status rockpi-sata.service :

0;1;32m●e[0m rockpi-sata.service - Rockpi SATA Hate[m
Loaded: loaded (/lib/systemd/system/rockpi-sata.service; enabled; vendor preset: enabled)e[m
Active: e[0;1;32mactive (running)e[0m since Sat 2020-06-20 01:51:34 PDT; 25s agoe[m
Main PID: 1570 (python3)e[m
Tasks: 7 (limit: 4915)e[m
Memory: 13.1Me[m
CGroup: /system.slice/rockpi-sata.servicee[m
├─1570 /usr/bin/python3 /usr/bin/rockpi-sata/main.py one[m
├─1785 /usr/bin/python3 /usr/bin/rockpi-sata/main.py one[m
├─1786 /usr/bin/python3 /usr/bin/rockpi-sata/main.py one[m
├─1787 /usr/bin/python3 /usr/bin/rockpi-sata/main.py one[m
└─1788 /usr/bin/python3 /usr/bin/rockpi-sata/main.py one[m

lsusb:

Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04a0:9005 Digital Equipment Corp.
Bus 001 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsblk :

NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 14.9G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 14.6G 0 part /

dmesg has no sd* section at all so ls /dev/sd* returnes nothing
The firmware update for the jms561 fails.

I have seated and unseated the hat and it makes no difference.

The top hat seems to be working fine. it reports temps, ip etc… and the blue leds for each drive are lit.

Any help?

Which version of the HAT is this? Is it the one powered by USB-C or the later rev with the barrel jack?

I could understand this happening if you were running USB-C with insufficient amperage.

In my case the 4port USB Bridge is very particular about how it connects. I have had to plug it in then out slightly to get the drives to show. Seem the connections are not too accurate and I’ll need to shutdown and reseat a couple times to get all drives to appear.

I gave up. 5 days trying to get it to work with OMV and 2 days trying to just make a PI4 NAS. Every time I got close, the drives would disappear or the hat would stop working. $400 failed experiment now in the top of my closet.

Thank you for input.

I have the barrel ended power supply.

I think you can try the following:

Use a clean Rasp image sd card.

First, just install the hat and the usb adapter, power on the pi and check lsusb if the hat is detected. If yes, then install the disks, run some test on the disks with following command:

sudo dmesg -c
sudo dd if=/dev/sda of=/dev/null bs=1M count=4096&
sudo dd if=/dev/sdb of=/dev/null bs=1M count=4096&
sudo dd if=/dev/sdc of=/dev/null bs=1M count=4096&
sudo dd if=/dev/sdd of=/dev/null bs=1M count=4096

wait for last command finish

sudo dmesg -c

If there is error, send the output of second demsg -c here.
If everything works, no disk loss, then you can start to install OMV. For disks do not appear on OMV, you can follow the link on wiki:

https://wiki.radxa.com/Dual_Quad_SATA_HAT#OpenMediaVault

I’m sorry for not replying you in time. Last time I saw your reply, I thought it was a problem with the connector. I thought the problem was solved by forcing the connector tightly.

So I took it down and followed these steps:

Used Seatool and Windows diskmanage to make sure the 4 drives work

Fresh 32gb SD card
used 2020-05-27-raspios-buster-lite-armhf.img
sudo apt-get update
sudo apt-get upgrade -y
curl -sL https://rock.sh/get-rockpi-sata | sudo -E bash -
shutdown -h now

installed hat

systemctl status rockpi-sata.service
rockpi-sata.service - Rockpi SATA Hat
Loaded: loaded (/lib/systemd/system/rockpi-sata.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2020-07-07 08:44:03 BST; 7min ago
Main PID: 448 (python3)
Tasks: 6 (limit: 4915)
Memory: 23.1M
CGroup: /system.slice/rockpi-sata.service
├─448 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on
├─793 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on
├─794 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on
├─795 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on
└─796 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on

lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 04a0:9005 Digital Equipment Corp.
Bus 001 Device 003: ID 046d:c408 Logitech, Inc. Marble Mouse (4-button)
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 28.7G 0 part /

and the hat has blue red blue red blue red leds from left to right facing the led end of the board.

I also added the

Fix Quad SATA HAT disk serial number

KERNEL==“sd*”, ATTRS{idVendor}==“1058”, ATTRS{idProduct}==“0a10”, SUBSYSTEMS==“usb”, PROGRAM="/root/serial.sh %k", ENV{ID_SERIAL}=“USB-%c”, ENV{ID_SERIAL_SHORT}="%c"

and /root/serial.sh

This changed the led pattern from a red/blue on each end to the pattern listed above.

dmesg -c

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2020.07.07 01:14:38 =~=~=~=~=~=~=~=~=~=~=~=
dmesg -c
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 4.19.118-v7l+ (dom@buildbot) (gcc version 4.9.3 (crosstool-NG crosstool-ng-1.22.0-88-g8460611)) #1311 SMP Mon Apr 27 14:26:42 BST 2020
[ 0.000000] CPU: ARMv7 Processor [410fd083] revision 3 (ARMv7), cr=30c5383d
[ 0.000000] CPU: div instructions available: patching division code
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
[ 0.000000] OF: fdt: Machine model: Raspberry Pi 4 Model B Rev 1.2
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] cma: Reserved 256 MiB at 0x000000001ec00000
[ 0.000000] On node 0 totalpages: 1012736
[ 0.000000] DMA zone: 1728 pages used for memmap
[ 0.000000] DMA zone: 0 pages reserved
[ 0.000000] DMA zone: 196608 pages, LIFO batch:63
[ 0.000000] HighMem zone: 816128 pages, LIFO batch:63
[ 0.000000] random: get_random_bytes called from start_kernel+0xc0/0x4e8 with crng_init=0
[ 0.000000] percpu: Embedded 17 pages/cpu s36928 r8192 d24512 u69632
[ 0.000000] pcpu-alloc: s36928 r8192 d24512 u69632 alloc=17*4096
[ 0.000000] pcpu-alloc: [0] 0 [0] 1 [0] 2 [0] 3
[ 0.000000] Built 1 zonelists, mobility grouping on. Total pages: 1011008
[ 0.000000] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 cma=64M snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_headphones=1 cma=256M video=HDMI-A-1:1920x1080M@60,margin_left=48,margin_right=48,margin_top=48,margin_bottom=48 smsc95xx.macaddr=DC:A6:32:67:82:B8 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=bcde2535-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait
[ 0.000000] Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
[ 0.000000] Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
[ 0.000000] Memory: 3735552K/4050944K available (8192K kernel code, 690K rwdata, 2420K rodata, 2048K init, 860K bss, 53248K reserved, 262144K cma-reserved, 3264512K highmem)
[ 0.000000] Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xffc00000 - 0xfff00000 (3072 kB)
vmalloc : 0xf0800000 - 0xff800000 ( 240 MB)
lowmem : 0xc0000000 - 0xf0000000 ( 768 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.text : 0x(ptrval) - 0x(ptrval) (10208 kB)
.init : 0x(ptrval) - 0x(ptrval) (2048 kB)
.data : 0x(ptrval) - 0x(ptrval) ( 691 kB)
.bss : 0x(ptrval) - 0x(ptrval) ( 861 kB)
[ 0.000000] SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=4, Nodes=1
[ 0.000000] ftrace: allocating 28928 entries in 85 pages
[ 0.000000] rcu: Hierarchical RCU implementation.
[ 0.000000] NR_IRQS: 16, nr_irqs: 16, preallocated irqs: 16
[ 0.000000] GIC: Using split EOI/Deactivate mode
[ 0.000000] arch_timer: cp15 timer(s) running at 54.00MHz (phys).
[ 0.000000] clocksource: arch_sys_counter: mask: 0xffffffffffffff max_cycles: 0xc743ce346, max_idle_ns: 440795203123 ns
[ 0.000005] sched_clock: 56 bits at 54MHz, resolution 18ns, wraps every 4398046511102ns
[ 0.000021] Switching to timer-based delay loop, resolution 18ns
[ 0.000264] Console: colour dummy device 80x30
[ 0.000742] console [tty1] enabled
[ 0.000801] Calibrating delay loop (skipped), value calculated using timer frequency… 108.00 BogoMIPS (lpj=540000)
[ 0.000837] pid_max: default: 32768 minimum: 301
[ 0.001128] Mount-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001162] Mountpoint-cache hash table entries: 2048 (order: 1, 8192 bytes)
[ 0.001954] CPU: Testing write buffer coherency: ok
[ 0.002379] CPU0: thread -1, cpu 0, socket 0, mpidr 80000000
[ 0.003030] Setting up static identity map for 0x200000 - 0x20003c
[ 0.003207] rcu: Hierarchical SRCU implementation.
[ 0.004091] smp: Bringing up secondary CPUs …
[ 0.004952] CPU1: thread -1, cpu 1, socket 0, mpidr 80000001
[ 0.005906] CPU2: thread -1, cpu 2, socket 0, mpidr 80000002
[ 0.006812] CPU3: thread -1, cpu 3, socket 0, mpidr 80000003
[ 0.006932] smp: Brought up 1 node, 4 CPUs
[ 0.006999] SMP: Total of 4 processors activated (432.00 BogoMIPS).
[ 0.007022] CPU: All CPU(s) started in HYP mode.
[ 0.007043] CPU: Virtualization extensions available.
[ 0.007896] devtmpfs: initialized
[ 0.018733] VFP support v0.3: implementor 41 architecture 3 part 40 variant 8 rev 0
[ 0.018958] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
[ 0.019000] futex hash table entries: 1024 (order: 4, 65536 bytes)
[ 0.026400] pinctrl core: initialized pinctrl subsystem
[ 0.027355] NET: Registered protocol family 16
[ 0.030543] DMA: preallocated 1024 KiB pool for atomic coherent allocations
[ 0.032087] hw-breakpoint: found 5 (+1 reserved) breakpoint and 4 watchpoint registers.
[ 0.032119] hw-breakpoint: maximum watchpoint size is 8 bytes.
[ 0.032344] Serial: AMBA PL011 UART driver
[ 0.035620] bcm2835-mbox fe00b880.mailbox: mailbox enabled
[ 0.050029] raspberrypi-firmware soc:firmware: Attached to firmware from 2020-06-01 13:23, variant start
[ 0.060046] raspberrypi-firmware soc:firmware: Firmware hash is 6379679d1ec6a8c746d7e77e015f5b56b939976f
[ 0.102986] bcm2835-dma fe007000.dma: DMA legacy API manager at (ptrval), dmachans=0x1
[ 0.106167] vgaarb: loaded
[ 0.106552] SCSI subsystem initialized
[ 0.106770] usbcore: registered new interface driver usbfs
[ 0.106841] usbcore: registered new interface driver hub
[ 0.106925] usbcore: registered new device driver usb
[ 0.108345] clocksource: Switched to clocksource arch_sys_counter
[ 0.187365] VFS: Disk quotas dquot_6.6.0
[ 0.187474] VFS: Dquot-cache hash table entries: 1024 (order 0, 4096 bytes)
[ 0.187669] FS-Cache: Loaded
[ 0.187875] CacheFiles: Loaded
[ 0.188551] simple-framebuffer 3e4e0000.framebuffer: framebuffer at 0x3e4e0000, 0x6e7000 bytes, mapped to 0x(ptrval)
[ 0.188590] simple-framebuffer 3e4e0000.framebuffer: format=a8r8g8b8, mode=1824x984x32, linelength=7296
[ 0.198421] Console: switching to colour frame buffer device 228x61
[ 0.207114] simple-framebuffer 3e4e0000.framebuffer: fb0: simplefb registered!
[ 0.216343] NET: Registered protocol family 2
[ 0.217075] tcp_listen_portaddr_hash hash table entries: 512 (order: 0, 6144 bytes)
[ 0.217183] TCP established hash table entries: 8192 (order: 3, 32768 bytes)
[ 0.217322] TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
[ 0.217461] TCP: Hash tables configured (established 8192 bind 8192)
[ 0.217654] UDP hash table entries: 512 (order: 2, 16384 bytes)
[ 0.217748] UDP-Lite hash table entries: 512 (order: 2, 16384 bytes)
[ 0.218024] NET: Registered protocol family 1
[ 0.218676] RPC: Registered named UNIX socket transport module.
[ 0.218747] RPC: Registered udp transport module.
[ 0.218804] RPC: Registered tcp transport module.
[ 0.218860] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.218935] PCI: CLS 0 bytes, default 64
[ 0.220761] hw perfevents: enabled with armv7_cortex_a15 PMU driver, 7 counters available
[ 0.223031] Initialise system trusted keyrings
[ 0.223283] workingset: timestamp_bits=14 max_order=20 bucket_order=6
[ 0.232662] FS-Cache: Netfs ‘nfs’ registered for caching
[ 0.233252] NFS: Registering the id_resolver key type
[ 0.233333] Key type id_resolver registered
[ 0.233389] Key type id_legacy registered
[ 0.233453] nfs4filelayout_init: NFSv4 File Layout Driver Registering…
[ 0.238097] Key type asymmetric registered
[ 0.238160] Asymmetric key parser ‘x509’ registered
[ 0.238323] bounce: pool size: 64 pages
[ 0.238489] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 250)
[ 0.238735] io scheduler noop registered
[ 0.241380] io scheduler deadline registered (default)
[ 0.244156] io scheduler cfq registered
[ 0.246753] io scheduler mq-deadline registered (default)
[ 0.249385] io scheduler kyber registered
[ 0.285314] brcm-pcie fd500000.pcie: dmabounce: initialised - 32768 kB, threshold 0x00000000c0000000
[ 0.287864] brcm-pcie fd500000.pcie: could not get clock
[ 0.290540] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges:
[ 0.293141] brcm-pcie fd500000.pcie: MEM 0x600000000…0x603ffffff -> 0xf8000000
[ 0.348368] brcm-pcie fd500000.pcie: link up, 5.0 Gbps x1 (!SSC)
[ 0.351220] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00
[ 0.353631] pci_bus 0000:00: root bus resource [bus 00-01]
[ 0.356148] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff])
[ 0.358776] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400
[ 0.358919] pci 0000:00:00.0: PME# supported from D0 D3hot
[ 0.361704] PCI: bus0: Fast back to back transfers disabled
[ 0.364225] pci 0000:00:00.0: bridge configuration invalid ([bus 00-00]), reconfiguring
[ 0.366948] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330
[ 0.367072] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit]
[ 0.367390] pci 0000:01:00.0: PME# supported from D0 D3cold
[ 0.370168] PCI: bus1: Fast back to back transfers disabled
[ 0.372735] pci_bus 0000:01: busn_res: [bus 01] end is updated to 01
[ 0.372785] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff]
[ 0.375376] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit]
[ 0.378008] pci 0000:00:00.0: PCI bridge to [bus 01]
[ 0.380624] pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff]
[ 0.383452] pcieport 0000:00:00.0: enabling device (0140 -> 0142)
[ 0.386151] pcieport 0000:00:00.0: Signaling PME with IRQ 53
[ 0.388891] pcieport 0000:00:00.0: AER enabled with IRQ 53
[ 0.391623] pci 0000:01:00.0: enabling device (0140 -> 0142)
[ 0.398477] iproc-rng200 fe104000.rng: hwrng registered
[ 0.401288] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB)
[ 0.404298] vc-sm: Videocore shared memory driver
[ 0.407274] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000
[ 0.420254] brd: module loaded
[ 0.432822] loop: module loaded
[ 0.436083] Loading iSCSI transport class v2.0-870.
[ 0.440353] libphy: Fixed MDIO Bus: probed
[ 0.443288] bcmgenet fd580000.genet: failed to get enet clock
[ 0.445794] bcmgenet fd580000.genet: GENET 5.0 EPHY: 0x0000
[ 0.448265] bcmgenet fd580000.genet: failed to get enet-wol clock
[ 0.450777] bcmgenet fd580000.genet: failed to get enet-eee clock
[ 0.453118] bcmgenet: Skipping UMAC reset
[ 0.455728] unimac-mdio unimac-mdio.-19: DMA mask not set
[ 0.468377] libphy: bcmgenet MII bus: probed
[ 0.508939] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus at 0x(ptrval)
[ 0.512325] usbcore: registered new interface driver r8152
[ 0.514837] usbcore: registered new interface driver lan78xx
[ 0.517325] usbcore: registered new interface driver smsc95xx
[ 0.519995] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 0.522410] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1
[ 0.527037] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000001000000890
[ 0.529808] genirq: irq_chip Brcm_MSI did not update eff. affinity mask of irq 54
[ 0.533110] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19
[ 0.535530] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.537914] usb usb1: Product: xHCI Host Controller
[ 0.540403] usb usb1: Manufacturer: Linux 4.19.118-v7l+ xhci-hcd
[ 0.542873] usb usb1: SerialNumber: 0000:01:00.0
[ 0.545833] hub 1-0:1.0: USB hub found
[ 0.548378] hub 1-0:1.0: 1 port detected
[ 0.551265] xhci_hcd 0000:01:00.0: xHCI Host Controller
[ 0.553572] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2
[ 0.556015] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed
[ 0.558874] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19
[ 0.561347] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 0.563815] usb usb2: Product: xHCI Host Controller
[ 0.566289] usb usb2: Manufacturer: Linux 4.19.118-v7l+ xhci-hcd
[ 0.568723] usb usb2: SerialNumber: 0000:01:00.0
[ 0.571570] hub 2-0:1.0: USB hub found
[ 0.574030] hub 2-0:1.0: 4 ports detected
[ 0.577661] dwc_otg: version 3.00a 10-AUG-2012 (platform bus)
[ 0.580289] dwc_otg: FIQ enabled
[ 0.580298] dwc_otg: NAK holdoff enabled
[ 0.580307] dwc_otg: FIQ split-transaction FSM enabled
[ 0.580319] Module dwc_common_port init
[ 0.580564] usbcore: registered new interface driver uas
[ 0.583079] usbcore: registered new interface driver usb-storage
[ 0.585610] mousedev: PS/2 mouse device common for all mice
[ 0.589155] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer
[ 0.593188] sdhci: Secure Digital Host Controller Interface driver
[ 0.595539] sdhci: Copyright© Pierre Ossman
[ 0.598259] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe
[ 0.601066] sdhci-pltfm: SDHCI platform and OF driver helper
[ 0.606359] ledtrig-cpu: registered to indicate activity on CPUs
[ 0.608934] hidraw: raw HID events driver © Jiri Kosina
[ 0.611454] usbcore: registered new interface driver usbhid
[ 0.613808] usbhid: USB HID core driver
[ 0.616931] vchiq: vchiq_init_state: slot_zero = (ptrval), is_master = 0
[ 0.621109] [vc_sm_connected_init]: start
[ 0.631327] [vc_sm_connected_init]: end - returning 0
[ 0.634858] Initializing XFRM netlink socket
[ 0.637103] NET: Registered protocol family 17
[ 0.639547] Key type dns_resolver registered
[ 0.642229] Registering SWP/SWPB emulation handler
[ 0.645140] registered taskstats version 1
[ 0.647429] Loading compiled-in X.509 certificates
[ 0.656729] uart-pl011 fe201000.serial: cts_event_workaround enabled
[ 0.659162] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 34, base_baud = 0) is a PL011 rev2
[ 0.666664] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver
[ 0.669539] brcmstb_thermal fd5d2200.thermal: registered AVS TMON of-sensor driver
[ 0.672576] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0
[ 0.675040] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated
[ 0.701556] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.3
[ 0.703978] sdhci-iproc fe340000.emmc2: Linked as a consumer to regulator.4
[ 0.724785] mmc1: queuing unknown CIS tuple 0x80 (2 bytes)
[ 0.728957] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 0.732914] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 0.738107] mmc1: queuing unknown CIS tuple 0x80 (7 bytes)
[ 0.740507] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA
[ 0.744298] mmc1: queuing unknown CIS tuple 0x80 (3 bytes)
[ 0.745251] of_cfs_init
[ 0.749209] of_cfs_init: OK
[ 0.752132] Waiting for root device PARTUUID=bcde2535-02…
[ 0.796863] random: fast init done
[ 0.842805] mmc1: new high speed SDIO card at address 0001
[ 0.851020] mmc0: new ultra high speed DDR50 SDHC card at address 0007
[ 0.854387] mmcblk0: mmc0:0007 SD32G 29.0 GiB
[ 0.858146] mmcblk0: p1 p2
[ 0.879769] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null)
[ 0.882211] VFS: Mounted root (ext4 filesystem) readonly on device 179:2.
[ 0.890049] devtmpfs: mounted
[ 0.899827] Freeing unused kernel memory: 2048K
[ 0.918391] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 0.920848] Run /sbin/init as init process
[ 1.101061] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21
[ 1.103399] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.105781] usb 1-1: Product: USB2.0 Hub
[ 1.110340] hub 1-1:1.0: USB hub found
[ 1.113051] hub 1-1:1.0: 4 ports detected
[ 1.438393] usb 1-1.3: new low-speed USB device number 3 using xhci_hcd
[ 1.450983] systemd[1]: System time before build time, advancing clock.
[ 1.557664] NET: Registered protocol family 10
[ 1.561417] Segment Routing with IPv6
[ 1.576393] usb 1-1.3: New USB device found, idVendor=046d, idProduct=c408, bcdDevice=14.00
[ 1.578952] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.581427] usb 1-1.3: Product: USB Trackball
[ 1.583851] usb 1-1.3: Manufacturer: Logitech
[ 1.596699] input: Logitech USB Trackball as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.3/1-1.3:1.0/0003:046D:C408.0001/input/input0
[ 1.599664] hid-generic 0003:046D:C408.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB Trackball] on usb-0000:01:00.0-1.3/input0
[ 1.608616] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 1.615201] systemd[1]: Detected architecture arm.
[ 1.638152] systemd[1]: Set hostname to .
[ 1.698429] usb 1-1.4: new low-speed USB device number 4 using xhci_hcd
[ 1.837176] usb 1-1.4: New USB device found, idVendor=04a0, idProduct=9005, bcdDevice= 1.10
[ 1.840116] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 1.842943] usb 1-1.4: Product: USB Keyboard
[ 1.845754] usb 1-1.4: Manufacturer: SONiX
[ 1.861159] input: SONiX USB Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.0/0003:04A0:9005.0002/input/input1
[ 1.929167] hid-generic 0003:04A0:9005.0002: input,hidraw1: USB HID v1.11 Keyboard [SONiX USB Keyboard] on usb-0000:01:00.0-1.4/input0
[ 1.942174] input: SONiX USB Keyboard Consumer Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:04A0:9005.0003/input/input2
[ 2.008581] input: SONiX USB Keyboard System Control as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:04A0:9005.0003/input/input3
[ 2.011996] input: SONiX USB Keyboard Keyboard as /devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.4/1-1.4:1.1/0003:04A0:9005.0003/input/input4
[ 2.015425] hid-generic 0003:04A0:9005.0003: input,hidraw2: USB HID v1.11 Keyboard [SONiX USB Keyboard] on usb-0000:01:00.0-1.4/input1
[ 2.300750] random: systemd: uninitialized urandom read (16 bytes read)
[ 2.312080] random: systemd: uninitialized urandom read (16 bytes read)
[ 2.315820] systemd[1]: Listening on udev Kernel Socket.
[ 2.323767] random: systemd: uninitialized urandom read (16 bytes read)
[ 2.327399] systemd[1]: Listening on initctl Compatibility Named Pipe.
[ 2.335623] systemd[1]: Listening on fsck to fsckd communication Socket.
[ 2.348906] systemd[1]: Created slice system-getty.slice.
[ 2.363889] systemd[1]: Listening on Syslog Socket.
[ 2.372249] systemd[1]: Started Dispatch Password Requests to Console Directory Watch.
[ 2.380758] systemd[1]: Listening on udev Control Socket.
[ 3.170846] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null)
[ 3.301296] systemd-journald[122]: Received request to flush runtime journal from PID 1
[ 3.806372] Driver for 1-wire Dallas network protocol.
[ 3.813904] media: Linux media interface: v0.10
[ 3.814585] gpio-4 (onewire@0): enforced open drain please flag it properly in DT/ACPI DSDT/board file
[ 3.816052] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned.
[ 3.818179] bcm2835_vc_sm_cma_probe: Videocore shared memory driver
[ 3.818195] [vc_sm_connected_init]: start
[ 3.821175] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x0000ffff
[ 3.824873] [vc_sm_connected_init]: installed successfully
[ 3.825510] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00000fff
[ 3.826551] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x0000ffff
[ 3.827029] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x0000ffff
[ 3.843042] videodev: Linux video capture interface: v2.00
[ 3.940932] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 3.942880] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned.
[ 3.961636] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[ 3.973588] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.002305] bcm2835-codec bcm2835-codec: Device registered as /dev/video10
[ 4.002339] bcm2835-codec bcm2835-codec: Loaded V4L2 decode
[ 4.018557] bcm2835-codec bcm2835-codec: Device registered as /dev/video11
[ 4.018595] bcm2835-codec bcm2835-codec: Loaded V4L2 encode
[ 4.030380] bcm2835-codec bcm2835-codec: Device registered as /dev/video12
[ 4.030431] bcm2835-codec bcm2835-codec: Loaded V4L2 isp
[ 4.031838] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 4.063238] bcm2835_audio soc:audio: card created with 4 channels
[ 4.066553] bcm2835_audio soc:audio: card created with 4 channels
[ 4.148050] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 4.220010] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
[ 4.243423] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0
[ 4.310198] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 4.327725] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 4.328661] usbcore: registered new interface driver brcmfmac
[ 4.342874] vc4-drm soc:gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4])
[ 4.342894] checking generic (3e4e0000 6e7000) vs hw (0 ffffffffffffffff)
[ 4.342904] fb: switching to vc4drmfb from simple
[ 4.343171] Console: switching to colour dummy device 80x30
[ 4.352664] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1
[ 4.352679] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 4.352688] [drm] No driver support for vblank timestamp query.
[ 4.352711] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL
[ 4.573063] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 4.589807] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 2 2020 23:30:41 version 7.45.202 (r724630 CY) FWID 01-72f6ece2
[ 4.593352] Console: switching to colour frame buffer device 240x67
[ 4.630048] vc4-drm soc:gpu: fb0: DRM emulated frame buffer device
[ 5.938510] Under-voltage detected! (0x00050005)
[ 6.384633] random: crng init done
[ 6.384646] random: 7 urandom warning(s) missed due to ratelimiting
[ 6.530452] uart-pl011 fe201000.serial: no DMA platform data
[ 6.623420] 8021q: 802.1Q VLAN Support v1.8
[ 6.865040] Adding 102396k swap on /var/swap. Priority:-2 extents:1 across:102396k SSFS
[ 7.338619] bcmgenet: Skipping UMAC reset
[ 7.449337] bcmgenet fd580000.genet: configuring instance for external RGMII (no delay)
[ 7.450218] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 8.079253] i2c /dev entries driver
[ 8.488589] bcmgenet fd580000.genet eth0: Link is Down
[ 12.648628] bcmgenet fd580000.genet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 12.648675] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 14.455137] Bluetooth: Core ver 2.22
[ 14.455221] NET: Registered protocol family 31
[ 14.455231] Bluetooth: HCI device and connection manager initialized
[ 14.455254] Bluetooth: HCI socket layer initialized
[ 14.455269] Bluetooth: L2CAP socket layer initialized
[ 14.455317] Bluetooth: SCO socket layer initialized
[ 14.473766] Bluetooth: HCI UART driver ver 2.3
[ 14.473781] Bluetooth: HCI UART protocol H4 registered
[ 14.473873] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 14.474117] Bluetooth: HCI UART protocol Broadcom registered
[ 14.777569] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.777583] Bluetooth: BNEP filters: protocol multicast
[ 14.777606] Bluetooth: BNEP socket layer initialized
dmesg: read kernel buffer failed: Operation not permitted
pi@raspberrypi:~ $

The USB connector may be broken, please contact Allnet to replace it. Or test it first with two A-A cables.

Hell R_Xmas,
could you solve the problem?

I have the same problem now. Using:
Raspbian GNU/Linux 11 (bullseye)
OMV6 (6.0.15)
SanDisk SSD 3D Ultra 2TB.

Can also not even see the drive in the terminal.

Did your controllers get connected?

If you enter the command ‘dmesg | grep -i jmicron’, you should see something like:

dmesg | grep -i Jmicron

[ 24.838105] usb 2-2: Manufacturer: JMicron
[ 25.488360] usb 2-1: Manufacturer: JMicron
[ 25.917043] scsi 0:0:0:0: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6
[ 26.556995] scsi 1:0:0:0: Direct-Access JMicron Tech 8136 PQ: 0 ANSI: 6

If not then the controllers were not found, either as noted in previous entries because the USB3.0 bridge is not well connected, which could mean not really well seated, or that the controllers are not being enabled through the GPIO signals from the Pi.

Two GPIO pins on the 40-pin connector are used to enable the controllers (pin 37 (GPIO_RST/bcm26) - reset SATA 3/4 and pin 22 (GPIO_RST1/bcm25) - reset SATA1/2). They are set high in /usr/bin/rockpi-sata/misc.py in the function ‘def disk_turn_on()’. Until this occurs, and the gpio signals physically go high the controllers are not seen on USB.

This requires the rockpi-sata.service to run and to be able to set these signals high, which is why the log snippet above notes that the controllers are not seen until 24 seconds into the boot.

You will still see the blue lights, but nobody is home til the controllers are both enabled and USB3.0 sees them.

You might be able to test these signals, if you have a voltmeter and a scope. Pinout information can be seen in: https://wiki.radxa.com/Dual_Quad_SATA_HAT#PINOUT .

The log snippet from the ‘systemctl status rockpi-sata.service’ shown in a previous entry shows that for that user the service did indeed startup without errors, so the GPIO being low is unlikely, but may still possible.

Thank you oket for your reply!

pi@raspberrypi:~ $ dmesg | grep -i Jmicron
pi@raspberrypi:~ $

As you can see above the result after the command ‘dmesg | grep -i Jmicron’ is nothing.
I tried a lot with moving the USB-bridge as well as with a USB A-A cable. So I don’t think this is the reason but more likely, as you wrote, the controllers.

On GPIO I measured with a digital multimeter (no oscilloscope) 3,3V on pin 22 (GPIO_RST1/bcm25 - reset SATA1/2) as well as on pin 37 (GPIO_RST/bcm26 - reset SATA 3/4).
Would have expected 5V, but maybe 3,3V is the right logic level!?

Run the command 'systemctl status rockpi-sata.service’ gives:

pi@raspberrypi:~ $ systemctl status rockpi-sata.service
● rockpi-sata.service - Rockpi SATA Hat
Loaded: loaded (/lib/systemd/system/rockpi-sata.service; enabled; vendor preset: enabled)
Active: active (running) since Sat 2022-03-05 22:14:39 CET; 24min ago
Main PID: 790 (python3)
Tasks: 6 (limit: 3720)
CPU: 3.521s
CGroup: /system.slice/rockpi-sata.service
├─ 790 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on
├─1282 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on
├─1283 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on
└─1285 /usr/bin/python3 /usr/bin/rockpi-sata/main.py on
pi@raspberrypi:~ $

Looks good - doesn’t it!?

It shows no logged errors, and it looks like your machine has turned on the controllers, so I think you only have the USB connector and the HAT itself.

I’d go with setq’s suggestion to contact allnet and see about a new connector and hat board.
I found on mine that the connector was somewhat touchy and I had times when it looked like it was fully in, but had not really connected until it was very firmly pushed down.

I suspect that with your experiences that you have firmly pushed it down, if only out of frustration.

The price for the board is pretty low (https://shop.allnetchina.cn/collections/sata-hat/products/dual-sata-hat-open-frame-for-raspberry-pi-4) though I think that you could make a case for a free replacement.
What you will probably get is a V1.2 hat board, which has the 12V barrel connector. If your existing one is a V1.1 (Type-C connector) you would have to get a 12V power supply and drill the case over the socket to use the hat. I had replaced my V1.1 board a while ago since I thought I may have damaged it with a low-power type-c supply, and I got a V1.2.

I pushed the USB-bridge a bit extra in - could feel a bit of extra movemement. After that I saw the blue LED blinking a few times. So I checked it again in the terminal:

pi@raspberrypi:~ $ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 152d:0561 JMicron Technology Corp. / JMicron USA Technology Corp. JMS551 - Sharkoon SATA QuickPort Duo
Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
pi@raspberrypi:~ $ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sda 8:0 0 1.8T 0 disk
├─sda1 8:1 0 488.3G 0 part
├─sda2 8:2 0 488.3G 0 part
├─sda3 8:3 0 488.3G 0 part
└─sda4 8:4 0 398.2G 0 part
mmcblk0 179:0 0 14.5G 0 disk
├─mmcblk0p1 179:1 0 256M 0 part /boot
└─mmcblk0p2 179:2 0 14.2G 0 part /

Heureka! :smiley:
I was sure I pushed it in completely the very first times… obviously not.
Can also see it in OMV6 now.

Just to complete it: I have the V1.2 with barrel connection for 12V.
Tests with A-A USB-cable: either I pushed it not far enough in as well, or it is to short.

Thanks for all the help! :slightly_smiling_face: :+1:

My congratulations, hope it will all work well for you. Guess you might not have been frustrated enough :wink:

Thx - yes I hope so too! Now I will install more drives and connect it as back-up to an existing NAS. There will be for sure some more challenges. But often it is a “layer 8 problem” :joy: