Answer the question
In order to leave comments, you need to log in
Why is the SAS SSD not visible in the old HP P400 controller?
Hello!
On the hp dl 360 g5 server, the hp p400 controller sees hdd sas and ssd sata
disks. ZEUS IOPS SSD disks were connected - SSD SAS 200 GB instead of HDD SAS - and they are not visible in the controller settings. Diodes burn both - orange and red on similar disks.
As far as I read the specs, these disks support SAS 3.0, and the controller 1/2 - but in theory the disks and controllers are compatible, everything should work, albeit not at full capacity. What's wrong? Update the controller (so that it is already being done).
Used seller SAS SSD disks say that they need to be formatted, but if they are not visible as physical disks in the config, no formatting will help them ...
Answer the question
In order to leave comments, you need to log in
10 disks were purchased, I inserted 4 into the server. And they all behave the same way. Really all dead... Read in an Internet, found out that these disks go on HP P9500
SHD Disks bind to vendor. I talked to another seller of similar disks, he says that it is necessary to flash, since they have a mode of operation for storage and for a server. I have no experience with this, I just don’t want to make claims out of ignorance.
Everything is formatted with the controller or HBA through the sg_format utility.
The whole problem is in sectors, a 520-byte sector block, for storage, such as it is more reliable to contain data for them, and the server needs 512 bytes. Here this utility this business also is formatted. Surprisingly, even low-level formatting does not help, does not give access to the device ...
If it is not visible at all - the disk is dead, let the huckster format it himself. If it is visible, but it has a yellow icon, remove the metadata from it (clear disk metadata), look in the configurator. After cleaning, it will be possible to include it in the array.
The stick can be two-edged - both the controller can have limitations and work only with "proprietary" disks (read - "with custom firmware from the storage manufacturer"), and the disks can only be designed for storages defined in one way or another.
The task of flashing disks (changing one firmware to another) varies in complexity depending on the "what is - what is needed" pair, but in most cases it ranges from "difficult" to "very difficult". Manufacturers, after all, like it when they buy discs only from them at not the lowest prices.
As a starting point, you can try checking drives with R.tester , it should see them rather than not, but that depends on the controller drivers.
Also, for the same purpose, you can try to connect the disks to a "general purpose controller" like LSI and try to make a test on it.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question