An HPE ProLiant DL380 Gen9 owner faced two storage questions that are often treated separately: whether to enable SSD Smart Path or use Smart Array controller cache, and why Smart Storage Administrator reported only OK instead of a remaining-life percentage for 3.84 TB SSDs identified as AREA3840S5xnNTRI.
The drive identifier changes the answer. HPE’s own support material lists AREA3840S5xnNTRI as a 3PAR StoreServ drive model, not as a general ProLiant SmartDrive option. Before benchmarking cache modes or trusting an OK status, verify that the controller, carrier, firmware, and drive are supported together in the DL380 Gen9.
First Identify the Entire Storage Chain
Record each layer rather than relying on the capacity displayed in SSA:
- DL380 Gen9 chassis and drive-cage type.
- Smart Array controller model, such as P440ar, P440, or P840.
- Controller firmware and cache-module/battery or capacitor health.
- Logical-drive RAID level, stripe size, and current cache policy.
- Physical drive model, HPE spare/option number, firmware, interface, and carrier.
- Operating system or ESXi version and Smart Array driver.
HPE’s Gen9 UEFI documentation recommends supported controllers with current firmware and points administrators to an offline Service Pack for ProLiant workflow. “The controller detects the drive” is not equivalent to a supported configuration.
The Reported SSD Is a 3PAR Drive
HPE’s 3PAR spare transition notice identifies AREA3840S5xnNTRI as a 3.84 TB drive used in 3PAR StoreServ systems. HPE PartSurfer associates it with spare numbers such as 879391-001 and specific 3PAR families.
That corrects a tempting but unsafe assumption: an HPE-branded 12 Gb/s SAS SSD is not automatically certified for every HPE server and Smart Array controller. Enterprise storage platforms can use platform-specific firmware, qualification, telemetry, carriers, and replacement policies.
For a repurposed drive:
- Read the physical label and record the complete spare and assembly numbers.
- Compare them with the current DL380 Gen9 QuickSpecs and Smart Array compatibility material.
- Check the drive firmware reported by SSA or the controller CLI.
- Ask HPE support or an authorized parts channel to confirm the exact controller/drive combination.
- Do not apply 3PAR drive firmware through a ProLiant workflow or vice versa.
If the combination is unsupported, SSA may expose only generic health, firmware maintenance may be unavailable, and predictive-failure behavior may differ. The correct production decision may be to replace the drives with supported ProLiant SmartDrives, not to search for a hidden wear gauge.
What SSD Smart Path Does
HPE describes SSD Smart Path as an optimized I/O path selected by the Smart Array driver. Its current controller references say that it accelerates reads for RAID levels and can accelerate RAID 0 writes by avoiding portions of the traditional controller path.
Smart Path is most attractive when:
- The workload is read-intensive.
- Latency and IOPS are constrained by the controller path.
- The controller, driver, firmware, RAID level, and SSDs are explicitly supported.
- Benchmarking with the real workload shows an improvement.
It is not a generic “SSD mode,” and it does not make controller cache irrelevant. HPE’s P840 product reference lists both SSD Smart Path and 4 GB flash-backed write cache as distinct controller capabilities.
What Controller Cache Does
Flash-backed write cache acknowledges writes after protecting them in controller cache and later commits them to the array. Read-ahead cache may help predictable sequential workloads, while random reads from SSDs often benefit less.
Controller cache is valuable when:
- The workload includes meaningful writes.
- RAID 1, RAID 10, RAID 5, or RAID 6 write behavior benefits from protected coalescing.
- The cache protection module is healthy.
- The operating policy favors consistent write latency and recovery behavior.
Cache policy should never be chosen from a generic table alone. Database transactions, VM datastores, backup streams, and read-mostly file repositories issue very different I/O.
A Current HPE Advisory Changes the Risk Calculation
HPE’s revised Smart Array advisory on SSD RAID 1/10 says that an inconsistent stripe can be reported after an ungraceful shutdown when Smart Path is enabled and controller write cache is disabled. The advisory covers Gen8 and Gen9 Smart Array controllers, including P440 and P840 families.
HPE recommends preventing ungraceful shutdowns with a UPS. Where the risk is a concern, it also directs administrators to disable Smart Path and enable controller write cache on the logical drive.
That means “Smart Path is always best for enterprise SSDs” is not a defensible rule. For a RAID 1 or RAID 10 VM datastore with write activity, protected controller cache may be the safer default, subject to HPE support guidance and workload testing.
Practical Decision Matrix
| Workload | Starting policy | Reason to test the alternative |
|---|---|---|
| Read-mostly repository | Smart Path if fully supported | Cache may help predictable read-ahead or mixed activity |
| ESXi VM datastore on RAID 10 | Protected controller cache | Smart Path may improve reads, but review HPE’s ungraceful-shutdown advisory |
| Transactional database | Controller write-back cache | Test Smart Path only with supported drives, power protection, backups, and measured benefit |
| Backup target with large sequential writes | Controller cache | Workload may be throughput- rather than latency-limited |
| RAID 0 disposable scratch | Smart Path can be relevant | Data protection is already outside the array |
| Unsupported or repurposed SSD | Neither as a production assumption | Resolve compatibility before tuning |
Use the same RAID layout and dataset for every comparison. Warm the workload, record latency percentiles and throughput, and test both steady state and recovery after a controlled reboot. Never simulate an ungraceful shutdown on production data.
Why SSA May Show Only “OK”
The normal SSA device page can summarize current health without displaying endurance as a percentage. HPE documents a separate SmartSSD Wear Gauge Report. Its Intelligent Provisioning guide describes the report as the place to view SSD usage and estimated lifetime.
Open the report through the SSA diagnostic or reporting interface rather than expecting the percentage on the status dashboard. HPE’s SSA product material also distinguishes the dashboard from detailed configuration and diagnostic reports.
If the wear report still omits the value:
- Confirm that the installed SSA version supports the controller and OS.
- Update the supported controller driver and firmware together.
- Generate a full SSA diagnostic report.
- Check iLO’s Integrated Management Log and storage events.
- Confirm whether the exact drive exposes HPE SmartSSD telemetry through that Smart Array controller.
- Treat unsupported drive firmware as a likely reason for incomplete management data.
Do not infer “100% life remaining” from Status: OK. It means that the controller is not currently reporting a failing state through that view.
Firmware and Offline ISO Troubleshooting
The same server also had difficulty booting an SSA Offline ISO through iLO Virtual Media and sometimes paused at Starting drivers. Keep that problem separate from the cache decision.
Use a controlled boot checklist:
- Verify the ISO checksum against HPE’s download information.
- Confirm iLO firmware and remote-console stability.
- Match UEFI or Legacy boot mode to the boot image’s supported method.
- Select the iLO virtual CD/DVD explicitly from the one-time boot menu.
- Test a current HPE-supported SSA/SPP image for Gen9.
- Record the exact firmware and any Red Screen or Illegal Opcode event.
- Remove unnecessary PCIe devices only under a documented maintenance plan.
An intermittent pre-boot crash can originate in firmware, virtual media, a controller option ROM, or attached hardware. Do not label it a known bug without matching an HPE advisory to the exact firmware and hardware inventory.
A Safe Configuration Procedure
- Back up every VM or dataset and test a restore.
- Export the SSA configuration and diagnostic report.
- Confirm drive compatibility and firmware provenance.
- Verify the UPS and Smart Array cache-protection status.
- Update the supported firmware/driver stack in an approved order.
- Choose one policy change: Smart Path or controller cache.
- Benchmark a representative read/write workload.
- Monitor latency, controller events, medium errors, wear data, and consistency scans.
- Document the result and rollback setting.
RAID is not a backup, an OK badge is not an endurance measurement, and a benchmark is not a compatibility certificate.
Conclusion
On a DL380 Gen9, the right choice between SSD Smart Path and Smart Array cache depends on the workload, RAID level, power-loss design, and—first of all—the supported drive/controller combination. HPE’s current advisory gives a concrete reason to favor protected controller cache for some SSD RAID 1/10 workloads.
The AREA3840S5xnNTRI identifier deserves special attention because HPE documents it as a 3PAR StoreServ drive. Resolve that compatibility question before trusting generic health data or optimizing the I/O path. Then use the SmartSSD Wear Gauge report, current diagnostics, and repeatable workload measurements to make the storage decision.