hp proliant not recognizing emc sas drives

5,414

Solution 1

You can make this work with some effort. Normally, I'd be all like, "Use HP drives", but the fact that you're using a G7 ProLiant means that many of the firmware restrictions don't apply from either side.

Gen8 ProLiant servers are a totally different story.

So, in this case, it's just a formatting issue. The AX4 disks are formatted in 520-byte sectors, versus the 512-byte sectors you'd get on normal PC or server-class drives.

You'll want to attach the drives to a SAS HBA (not the HP Smart Array controller), and if you have access to a Linux system or Live CD, the sg3_utils package contains the tools to do this properly. An example of the process is here.

sg_format –format –size=512 /dev/sdX 
# Where sdX is the drive identified in the output of sg_scan -i

Is this worth the effort?

  • HP G6/G7 SAS disks are cheap on the used market.
  • This process takes 10-20 minutes per drive, depending on the size. What's your time worth?
  • The EMC disks may be worth more to someone who needs EMC disks, as it's not possible to format normal drives for EMC use.

Solution 2

is there something we are missing or is this hopeless?

They're not supported, HP puts a specific firmware on their disks that provides a lot of additional diagnostic data over an off-the-shelf disk. This site is built for professional sysadmins, we like to build supportable solutions so I'd avoid trying to do what you're attempting.

Solution 3

Having worked with HP servers since G2 days I just thought I'd throw my two pence worth in.

I have done a lot of unusual things with HP servers for Dev and training purposes. A HP SAS crontroller (especially the P400-800 series) will work with any SAS or SATA disk type, it does not have to have any special HP firmware on. The array configuration tool will even let you config and monitor the disks too.

I have filled a G5 with OCZ solid state disks just to see how many VMs we could host in our training lab, I've also attached the MSA trays filled with disks off ebuyer to create a giant NAS for Backing up Dev environments and VM images.

This is not hacking, non of the HP firmware or code was changed, and as previously mentioned the controllers support these disks on stock HP firmware.

If someone has a load of old hardware they could make something useful out of then fair play, I found this as I now have a couple of trays of 2TB EMC disks that I was going to dispose of.

This would be unsupported by HP. This is not something that you would do with your live environment without accepting the significant risk (it may be ok for static data that you have a regular backup of, like a DML or Media server). It is also worth noting here that a second hand disk off eBay is probably worse than a new disk that has been purchased and put in a HP caddy as you don't know the history of the disk.

Solution 4

Unlikely to work, HP puts its own software onto the disks to keep people coming back to them for legit parts.

Share:
5,414

Related videos on Youtube

sivann
Author by

sivann

Updated on September 18, 2022

Comments

  • sivann
    sivann over 1 year

    We have lots of 2.5'' SAS drives from a decomissioned EMC AX4 array (Seagate Savvio 10k.3), and would like to install on HP Proliant 360pG7. Proliant does not detect those drives, is there something we are missing or is this hopeless?

    Let me clarify: we don't want an HP supported solution, we would like to know if it is possible for the disks to work. These servers are for dev/testing.

    • sivann
      sivann over 8 years
      Why the vote down, this is a valid tech question.
    • Jenny D
      Jenny D over 8 years
      It's voted down because this community does not handle unsupported hardware.
    • sivann
      sivann over 8 years
      @JennyD I strongly disagree This shouldn't be a community for rich companies with big budgets. Some of us work with big retraints. Moreover since when a hack is by definition a bad thing? If buisiness risks are taken into account, using tech in an "unsupported by the vendor" way, is a perfectly valid option that one should consider. After all this is a technology forum, not a presales one :-) Unsupported does not mean unauthorized.
    • Jenny D
      Jenny D over 8 years
      If you disagree with the current rules for what is on-topic and not, please post on Meta Server Fault with a suggestion for change. But as long as there is a specific close-reason for unsupported systems, people will keep using it.
    • sivann
      sivann over 8 years
      @JennyD thank you for your input, where is the clause that this forum is not about unsupported systems? I can only find a clause about unauthorized (i.e. illegal) which makes perfect sense.
    • sivann
      sivann over 8 years
      Now I'm confused, your own answer says that it is on-topic: meta.serverfault.com/questions/5414/…
    • Jenny D
      Jenny D over 8 years
      1. That was about legacy systems, not about using unsupported hardware combinations. 2. That was also two years ago. Even if that answer had been applicable, the site consensus changes over time.
    • Jenny D
      Jenny D over 8 years
      You should also be aware that I am not a moderator on this site, nor am I responsible for the help center's on-topic/off-topic page. But you asked why your question was downvoted; I showed you the courtesy of explaining the most likely reason.
  • Dan
    Dan over 8 years
    More specifically what Chopper3 said.
  • HBruijn
    HBruijn over 8 years
    And the reverse possibly also holds true: EMC loading custom firmware on the drives they ship, which may prevent them from being usable in other systems.
  • sivann
    sivann over 8 years
    @Chopper3 These are servers used for testing so we don't want a support contract for them and that is a business decision not a technical one. I am not your client, I just asked a tech question please don't offer generic policy wisdom. My question is about weather we can make it work, not if it is supported by HP.
  • Hartmut
    Hartmut over 8 years
    As far as I am concerned this question is also interesting to me, as solutions are sometimes not supported and sometimes you need to do workarounds. Although there seems to be no solution, the above answerers helped to understand this topic better.
  • sivann
    sivann over 8 years
    @Chopper3 this is a valid business question since it originated from a valid business need. It is perfectly supportable for our use (the servers also have HP boot drives in them) and I find it suitable for this site. Not supported by the vendor does not mean misuse. If I wanted a vendor-sanctioned answer I would open a ticket to HP, not here :-) Anyway thank you for the tech part of your input.
  • Dan
    Dan over 8 years
    Its a valid question, and i agree that its not always possible or desirable to work within the strictures of a support contract, especially in this case as nobody like paying for Lab environments
  • EEAA
    EEAA over 8 years
    @sivann Forget about the HP support aspect and concentrate on what Chopper said about firmware. Both OEMs put custom firmware on the drives. It's not going to work for you.
  • Chopper3
    Chopper3 over 8 years
    Plus they'd have to buy HP disk caddies too of course.
  • ewwhite
    ewwhite over 8 years
    Oh, this can work, but may not be worth the effort as HP disks can be found readily on the used market at low prices. See my answer for the process to force these drives to work, though.
  • sivann
    sivann over 8 years
    Thank you for this info. We have a SAS HBA but I agree it may indeed not worth the effort.
  • tomohulk
    tomohulk almost 7 years
    just thought i'd add, i found an sg_format.exe for windows, so i am actually formatting the entire shelf in tandem with powershell jobs: (1..25) | %{ Start-Job -ScriptBlock { C:\sg_format.exe --format --size=512 --six -v "PD$($args[0])" } -ArgumentList $_ }
  • tomohulk
    tomohulk almost 7 years
    Last comment, i swear, you can check the status of the jobs with .\sg_format PD1 -v the verbose output will tell you the current status of the formating.