RPI4 Quad says hat

Loosecannon · Apr 23rd 2020

good evening, i am currently stuck.... and could do with a little assistance....

i have purchased the quad sata hat kit from ALLNET and received it, set it up so it detects the hard drives, and installed OMV5 on my RPI4 4GB.... when typing in LSBLK it registers all the hard drives i have installed, 2x500gb, 1x250gb and 1x120gb sda sdb sdd sdc

Also purchased a laptop 65w USB c power brick so I know the power isn't a problem.

when i go to config omv5 in the disks section i am unable to see all the hard drives, only 2 sdc & sdd

is there anything i do or code to apply to gain access to all of the drives in omv so i can configure and start to use?

cheers.

ryecoaaron · Apr 23rd 2020

Mine is on its way. I can help once I get one.

Loosecannon · Apr 23rd 2020

Brilliant!! When did you order?? I only got mine y'day but ordered in the 2nd week of January ?

ryecoaaron · Apr 23rd 2020

Quote from Loosecannon

When did you order??

December 10th. Got an email a week ago that it was shipped.

cabi · Apr 24th 2020

Same problem.

https://forum.radxa.com/t/quad…ult-5-raspberry-pi-4/3193

macom · Apr 24th 2020

Picture in the link shows identical serial numbers for two different drives.

There are some threads in the forum about this causing issues.

geaves · Apr 24th 2020

I had bookmarked this thread as I was interested in one of these, and the the information that macom is referring too is here from this post down.

votdev · Apr 24th 2020

In the troubleshooting section there are some hints related to JMicron controllers, maybe that helps.

latimeria · Apr 24th 2020

Hi,

in my case (JMicron JM20337 USB PATA/SATA bridge on Orangepi PC2 with OMV5) the generic env ENV{ID_VENDOR}=="JMicron" in the troubleshooting sectiondid not work and I had to change the rule as follows:

Code

KERNEL=="sd*", ATTRS{idVendor}=="152d", ATTRS{idProduct}=="2338", SUBSYSTEMS=="usb", PROGRAM="/root/serial.sh %k", ENV{ID_SERIAL}="USB-%c", ENV{ID_SERIAL_SHORT}="%c"

where idVendor and idProduct are simply coming from lsusb command output