SAS is not initialized. Causes?

Question

Hard disks

Hello. We inherited 4 sas constellation ES st32000444ss 2tb.
When you try to initialize, the controller says that the devices are in the spin-up state, the leds themselves in the bays where the disks are inserted blink constantly. By timeout, loading into the OS occurs and further research by the same Victoria indicates that the disks have invalid geometry, which leads me to believe that the controller on the disk itself cannot receive information about the state of the disk itself (the disk vibrates to the touch as during normal operation ).
What could be the reason for this condition? Is it possible that the firmware has crashed or is there some kind of lock (ala cryptoprotection) on the disk?
The controller is working (HBA), the disks are 100% working, incl. with bad smart. I tried to connect to the raid controller, he does not see it at all.
Thanks in advance.

Answer 1

It is quite possible that the disks have vendor firmware (customized for specific storages).
Accordingly, the opposite is also possible - that your hardware is also designed to work only with specific part numbers of disks.
Unfortunately, bypassing such restrictions (depending on the combination of "what firmware is / what needs to be flashed") can be a very non-trivial task.

Answer 2

possibly non-standard firmware on the disks. where are they from? where did you work before?