A drive can match the part number and still be rejected by the array. NetApp, Dell EMC and HPE validate drive firmware, and non-OEM disks are often flagged or refused even when the base model is identical. This guide explains why it happens and how to specify drives that will actually be accepted.
1. Why arrays check firmware
Enterprise arrays treat drives as part of a validated configuration. The controller expects a specific firmware revision, sector format and sometimes a vendor-specific identity block. When a drive does not match, the array may:
- Refuse to bring the drive into the aggregate or pool.
- Accept it but raise persistent alerts or mark it as unsupported.
- Block firmware updates or failover behaviour that depends on the drive model.
- Invalidate support for the shelf or the array.
This is a policy decision by the array vendor, not a defect in the drive. A perfectly healthy drive with the wrong firmware can be unusable in a branded array and perfectly usable in a standard server.
2. Same model, different part number suffix
The clearest example is the suffix. The same physical SSD or HDD ships in several variants that differ only in firmware and identity: a generic OEM version and an array-specific version can look identical on the label except for the suffix. Buying the generic version to save cost frequently ends in returned stock.
When a customer sends a part number, we check the suffix and the array model rather than substituting a similar drive. If the exact variant is unavailable, we say so instead of shipping a drive that will be flagged.
3. What to send with the request
- Array or shelf model — for example a NetApp shelf, a Dell EMC PowerVault, or an HPE D-series enclosure.
- The current drive part number — read from the label or the array’s inventory, including the full suffix.
- Firmware revision — if the array reports it, include it.
- Quantity and destination country — for stock and freight.
With those four items we can match the OEM firmware revision rather than guessing from capacity and interface.
4. When the array is not branded
Standard servers and JBOD shelves generally accept any drive that matches the interface and form factor. In that case the checks are different: interface (SATA/SAS/NVMe), recording technology (CMR vs SMR), workload rating, and power/heat. A drive that is rejected by a branded array is usually fine in a plain server — but the reverse is not true.
5. Refurbished and new-pull stock in arrays
Refurbished drives are common for array maintenance, where the model is out of production. Two things matter beyond health: the firmware variant must match, and the drive must be tested for the array’s sector format. Ask for per-serial SMART and a surface scan; a batch-level claim is not enough for a production array.
6. Procurement checklist
| Check | What to confirm |
|---|---|
| Array model | NetApp / Dell EMC / HPE or generic server |
| Part number | Full suffix, not just capacity and interface |
| Firmware | OEM revision matching the array |
| Sector format | 512e / 4Kn as required by the platform |
| Condition | New, new-pull or refurbished, stated per line |
| Evidence | SMART dump + surface scan per serial |
7. How we quote
Send the array model, the part number you need and the destination country. If the exact OEM variant is unavailable, we will tell you rather than substitute a drive that the array will reject. Where a compatible variant exists, the quotation states the firmware variant and the condition.
Related