DL360 Gen9 SSD not recognized as HPE

[vimak]

Hello,

Smart Array does not recognize the two HP SSD, but identifies them as HGST and does not allow me to configure the raid.

Why?

Thank you

[Moderator edit: Erased the confidential info.]

[TVVJ]

Hello,

The screen shot indicates that the the drive in question is SSD. 

Array creation is allowed only between same type of drives, meaning all drives in the RAID array should either be SAS or  SATA or SSDs.

Try creating arrays using only the SSDs.

Regards,

[Arnaud Delaloy]

hello,

   actually, this SSD CANNOT be used on Proliants, because it is low-level formatted with a 520-byte sector (as seen on a sticker and written in SSA screenshot), whereas SmartArray cards expect 512-byte devices.

520-byte sectored disks are usually for SAN systems;  and according to partsurfer.hpe.com  with the model number,  these two comes from a 3PAR array model 10000.

[vimak]

It is not possible to create raids with the two SSDs, says "not supported for the RAID configuration"

HDD is recognized as HP and with those you can create raids. Why are SSDs not recognized as HP but only with the HGST manufacturer brand?

[vimak]

Yes, I bought them on a 4 HP tray

"HP SAS-SSD 4x 480 GB SAS 6G 2,5" 3PAR 10000 E7W56B"

I had no idea that they had a different formatting, are there no solutions to be able to use them?

[Arnaud Delaloy · Accepted solution]

I haven't done it personnaly, but there are possibilities to perform a 520-byte low-level format it on a physical Linux server, with the command

sg_format

but there are extra steps ( first reformat it in 520-byte to erase it , then you'll be able to reformat it in 512 bytes...)

according to this blog post  https://forum.level1techs.com/t/how-to-reformat-520-byte-drives-to-512-bytes-usually/133021

[vimak]

Tonight I try, thanks

[sushil_P]

YES, you need to reformate 512 and use it on proliant servers.

you can use linux tool sg_format   for this purpose.

[vimak]

Successful operation, thank you all

[Sunitha_Mod]

Hello @vimak,

That's Awesome! 

We are extremely glad to know the issue has been resolved.