Taking work now — the first look is freeServer and RAID drives posted in from anywhere in the UK, or handed in at ten drop-off pointsQuicker still, give us a ring:0800 6890668
RDDRAID Drive Data Recovery 0800 6890668 Price my job
RDD / Whatever it is saying now / HPE logical drive failed or predictive failure

Smart Array P420, P440, P816i-a · iLO · SSA · logical drive failed · predictive failure · SmartDrive amber

HPE says the logical drive failed, or a drive is predictive. Smart Array's two verdicts, and only one of them means the night is over.

An HPE Smart Array calls its RAID volumes logical drives and reports two things worth stopping for. Predictive failure means a physical drive has crossed the thresholds HPE sets for reallocated sectors, spin retries and the rest, and is still reading; on a healthy logical drive it is a replacement, and on a degraded one it is the second failure announced. Logical drive failed means too many physical drives are gone and the volume is offline. Around them sit the messages that are not faults: drive not authenticated and unsupported drive, which mean a drive without HPE firmware in an HPE carrier, and the amber LED on a SmartDrive carrier, which means fault or predictive by its pattern. And beneath all of it, on Gen8 and Gen9 servers, the two firmware clocks that killed SAS SSDs at 32,768 and 40,000 hours. One member imaged is £300 + VAT after the free look, fixed in writing, 3–4 days at the bench.

Free first lookOne fixed figure in writingNo data, no bill on most jobsReturn postage paid

Rather talk it through? An engineer answers the bench line
0800 6890668

Power down. Label every slot before a drive comes out. Do not rebuild while a second drive is flagged. Do not clear or import a foreign configuration. Do not initialise, reformat or PSID-revert anything. A rebuild reads every sector of every surviving member, and on a set whose drives were bought together it is where the second failure is found. Nothing on the drives gets worse while the server is off.

What Smart Array is watching, and where its advice stops.

Smart Array firmware polls every physical drive for its SMART or SAS log pages and compares them with HPE's thresholds. A drive that crosses one is flagged Predictive failure, and HPE's guidance is to replace it under warranty; on a logical drive that is otherwise Optimal, that is sound, because the rebuild onto the replacement reads survivors that are healthy. On a logical drive that is already degraded, the same rebuild reads a predictive-failure survivor from end to end, and the error that crossed the threshold is the error that stops the rebuild.

Logical drive failed is the end of that road: the controller has lost more members than the RAID level tolerates, and the volume is offline. The physical drives it dropped are usually still readable on a bench prepared to wait, and the one dropped first still holds every stripe written before it dropped. Every member is imaged and the array reassembled in software from the images, with the controller's metadata on the drives giving the layout; that is the array site's work, done on this bench.

The clocks are the HPE-specific case. Bulletin a00092491, from November 2019, named SAS SSDs on firmware before HPD8 that fail at 32,768 power-on hours; a00097382, from March 2020, named another line failing at 40,000 hours before HPD7. HPE's own words were that after the failure neither the SSD nor the data can be recovered, and that drives put into service together will fail nearly simultaneously. Some of those drives answer at controller level on the bench and some do not; the first look is honest about which.

What it says, and what it means.

Describe yours to us →
What you see The usual reason Where that leaves you
Predictive failure; logical drive OKOne drive crossed its thresholdsReplace under warranty, or image first if it holds anything unique
Predictive failure; logical drive degradedThe second failure, announcedPower down; image the weak drives before rebuilding
Logical drive failedToo many members goneEvery member imaged; array reassembled from images
Drive not authenticated / unsupportedNo HPE firmware in the carrierA warning; the data is unaffected
Several SSDs failed togetherThe 32,768 or 40,000-hour clockStop; check the survivors' hours; assessed honestly
Amber LED, flashingFault or predictive, by patternPhotograph it; power down

From the parcel arriving to your files going back.

Work we have closed →
01

Logged the day it lands, and the first look costs nothing Free

A case number goes on the parcel and a number on every drive the day it is opened, matched to the slot you wrote on it. An engineer settles what has actually happened before anything spins: the interface, the sector format, the firmware, the security state, and what the controller was saying when it stopped. Back to you come two things together: a straight note of what is liftable and what is not, plus one figure, fixed and written down. Accept it, or decline and owe us nothing.

Nothing to pay for lookingA single figure, put in writingNo rebuilds, no imports, no resets
02

The drive on its own bench

A member drive is read on the equipment its interface needs: a SAS imager for SAS and NL-SAS, a SATA imager for enterprise SATA, a terminated SCSI or Fibre Channel controller for the legacy drives, a PCIe adaptor for NVMe. It is never put back in a server, and never in a controller that will try to rebuild. Drives that answer at full speed are imaged; drives with weak or failed heads go to the clean bench, where matched donors are fitted and the service area repaired before a sector is read.

Read at its native interfaceFailing heads to the clean bench
03

Imaged once, at its native sector size

Every drive is imaged sector by sector, head by head where it needs it, with the bad areas last. Drives with 520- or 528-byte sectors are imaged as they are and the extra bytes stripped from the image, never the drive. Self-encrypting drives are unlocked on the imager with the key you supply. From then on the originals are not touched again.

Head by head, weak areas lastNative sector size preserved
04

The image, and the set

Where the set is healthy and one member was the job, the image goes back to you on a fresh drive, sector-identical, ready to rebuild from. Where the set is the job, every member is imaged and the array reassembled in software from the images: order, chunk size, parity rotation and the reshape point read from the drives' own metadata, the file system repaired on the virtual volume, never on the originals. The array work is covered in full on our RAID array site, and it happens on the same bench.

One member: a sector-identical image on fresh mediaA set: reassembled in software from the images
05

You see the file list before you pay

What was recovered is listed for you first, and only then does a bill exist. Approve the list and it is invoiced; turn it down and it is not — and where nothing has come back, most jobs carry no charge at all. Recovered data travels home on fresh media bought in for your job, with the postage at our end. Your case is not closed until you have opened the files on a machine of your own.

No charge until you accept the figureFresh media, supplied with the job3–4 days at the bench

From the bench

  • Export the SSA diagnostic report or the iLO log before the server is touched. It records what failed when, and which firmware each drive is on.
  • Predictive on a degraded logical drive is the stop signal. Do not let the rebuild read it.
  • The do-not-remove light means what it says on a SmartDrive carrier; a drive pulled while it is lit can take a rebuild with it.
  • Check the firmware revision and the hours on every SAS SSD in a Gen8 or Gen9 when one fails; the clocks are exact.

One job, followed all the way through.

UK · RDD-2026-0561JOB LOGGED ✓

A DL380 Gen9 in RAID 5 with one drive failed and a second predictive, an engineer booked with a replacement, and a logical drive nobody had backed up

The owner asked the engineer to wait and sent both drives here in their carriers. The failed drive had a head swap on the clean bench and was imaged on the SAS imager; the predictive one was imaged with its weak areas last. Both images went back on fresh drives, and the engineer's replacements went into a logical drive that had already been made whole.

100% of both members recovered5 days here, and back by post
Illustrative example — replace with a genuine case

What helps, and what harms.

Do this much first

  • Export the SSA report or the iLO log
  • Power down and label the slots
  • Send the failed and predictive drives in their carriers
  • Tell us the Smart Array model, the RAID level and the firmware revisions

What sets us back

  • Rebuilding with a predictive-failure survivor
  • Pulling a drive whose do-not-remove light is on
  • Updating firmware on failed SSDs
  • Handing the failed drive to the courier before you have its data

Questions answered before you commit.

HPE says predictive failure. Do I need data recovery?

On a healthy logical drive, no: replace it under warranty. On a degraded one, yes: the rebuild will read the predictive drive from end to end and stop where it fails.

Logical drive failed. Is the data gone?

Usually not. Every member is imaged and the array reassembled in software from the images.

What does drive not authenticated mean?

That the drive lacks HPE firmware. It is a warning about support, not a fault with the data.

What does it cost?

£300 + VAT for one drive after the free look; sets of two to four from £500 + VAT; larger sets from £1,250 + VAT.

How long does it take?

3–4 days at the bench for one drive; 5–10 days at the bench for a set.

Nothing gets worse while it is powered down.

Looking at it is free. Back comes a list of what opened and what did not, together with a single price to finish, set down in writing while you are still free to say no. Until that list reaches you, leave the server off and the drives in their slots.

0800 6890668