The lab is taking new cases · 9am–5:30pm, Mon–Fri Urgent? Ring 0800 6890668
SDR Southampton Data Recovery 0800 6890668 Open a case
SDR / Harder cases / Data recovery for servers

Specialist · recovery from servers

Server data recovery, Southampton. Replacing the hardware is easy. Replacing the data isn’t.

In our experience, failed platters are rarely the reason. It is usually the state of the system: a card that no longer trusts its own disks, an array that is just one prompt away from disaster, or writes still stuck in cache. We rebuild from images, so the original card is not needed. And then we hand you back the volumes, virtual machines and databases your business runs on.

Only pay if we recover your data, on most jobs Free diagnosis & quote in writing Postal intake across all of Hampshire

Speak to an engineer about it
0800 6890668

What server errors actually mean.

Not listed? Try the fault finder →
The complaintWhat that tells youFirst step
Dell PERC: Foreign Configuration FoundThe disks have recorded information that contradicts what the card remembers (it has halted as a precaution, not because any data has been lost)Pick neither option
1786 — Drive Array Recovery Needed (HP)A rebuild is either outstanding, or it was interrupted before completion.Switch off; take images before anything else
Orange bay lights following a power cutSome half-finished writes and possible cache issues; the disks still contain the layout of where everything was located.Resist forcing any disk back online
It boots normally; however, the volume is no longer listedDamage to the card state or the file system, above data that is untouchedGood chances of recovery
The RAID card itself has failedLayout, including RAID 5 parity rotation, resides on the disks.An identical card is unnecessary
Guests or databases do not mount after the "recovery"Recovering the files is not enough; they must also be consistent.Our VMware and database pages cover this
Posting it: first, get a price quotation from us, by phone or with the form. Then send your item to us via tracked, fully insured post to our secure intake laboratory where it will be processed (we pay for return postage). Alternatively, you may also bring it to our Guildford intake laboratory Monday to Friday, 9am to 5:30pm, no appointment needed. Ring us and we would be happy to assist you with packaging, and there are postage details available on the postal details webpage.

Where a server array hides its own layout.

MegaRAID & Dell PERCBoth stamp DDF-format metadata, based on the SNIA industry standard, into the last sectors of every member disk, and this is why the array can be reassembled here from images alone, without needing a PERC.
HP Smart ArrayHP went their own way on purpose: a proprietary RIS block at the head of each disk, and parity shifted by a stripe. Give this array to some generic "RAID recovery" preset and what comes out will be rubbish.
The two-button choiceNeither the Import nor the Clear button is safe at the wrong moment. If there's still live data in your stripes, pressing Import may force old metadata onto them. Pressing Clear will delete the map completely. Therefore, nobody should push either of these buttons until all disks have been imaged.
The unflushed cacheWrites the host was told had completed, held in the card's memory with a battery (or supercapacitor) as an energy source. If the system loses power during flushing, the corruption can be completely invisible; therefore "it only lost power" means imaging, not optimism.

How the recovery runs, step by step.

01

Logged in, checked at no cost Free

Your item will have a unique case number assigned to it immediately after we receive it. An engineer will diagnose the issue, tell you what can genuinely be recovered and then provide you with one fixed price in writing. The diagnosis itself is completely at no cost to you. You are under no obligation to allow us to do any work that would incur a charge.

No-cost diagnosisQuote fixed in writingNothing to commit to
02

Preserve it exactly

Shut down, note which bay held each disk, and answer no prompts. Each member of the array is imaged individually on dedicated hardware, all members flagged as failed included, before anything is interpreted.

All members imagedFaulty drives covered
03

Reassemble without the RAID card

The RAID configuration (level, stripe size, disk order) along with parity rotation (for RAID 5 and RAID 6) comes out of the DDF or RIS records in each image, and the array is assembled in software. Losing the card costs you nothing.

Layout read off the disksNo original card needed
04

Get the working data back

All storage structures that sit atop the RAID layer (a VMFS datastore, NTFS, ReFS, ext4 or XFS) are put right on the rebuilt copy and subsequently verified: VMs boot, databases attach, network shares open.

File systems fixed on imagesMount tested, not assumed
05

Checked, returned, signed off

Once you have the complete listing of all the recoverable files back from us, you can "sign-off" and your recovery fee becomes due. Once you've signed-off, all the files will be posted out to you on new media (with postage included) and the case will remain open until you confirm that they can be opened properly at your location.

Sign-off on the file listNew media providedReturn postage on us

First checks on the bench

  • DDF is located at the end of a disk, RIS at the beginning. Knowing which family puts its map where separates a true rebuild from guessing.
  • A disk that has been marked as failed can be an important witness. One that was removed a month ago could hold the latest version of certain regions; the rebuild chooses block by block.
  • Generic tools are going to run right into HP's delayed parity. The parity block is placed a stripe out of step, and the array will only import on HP hardware. We build it exactly the way HP intended.
  • Don't ignore the cache battery. Whether the write-back cache actually reached the disks determines how clean the file system above it will be. That gets checked before anything is promised.

That's why this two-option prompt has such a bad name: Import puts the foreign metadata's view of the array over the one the card is running. Clear removes the DDF map from the disks altogether. Each option takes only one keystroke. Neither option can be undone. Once all disks have been imaged, the options are no longer hazardous. Imaging first is not caution here; it is the whole plan.

Out of the casebook.

EX · SDR-2026-0816SIGNED OFF ✓

A ProLiant that came through the storm and died on reboot

When the mains failed, the UPS ran out of power, and when the server restarted, the Smart Array wanted choices that nobody could make safely. All four disks were imaged, then the RIS metadata was parsed and the delayed parity respected, and the practice-management database was mounted from the rebuild, whole to the last write the cache had flushed just before the power went.

Database mounted clean5 days on the bench

While it's still with you.

Do

  • Shut it down, but take screenshots of the controller screens first
  • Label each disk with its bay number as it is removed from the system
  • Include all members, since even the dead-looking disks carry evidence
  • Identify which services are running on this server: Exchange, SQL, guest VMs, file shares

Avoid

  • When prompted about a foreign configuration, respond "Import" or "Clear"
  • Insert a spare disk into the server and allow it to complete the rebuild process
  • Flashing the card’s firmware during the emergency
  • Return the server to service before an image or copy exists

Bench questions, straight answers.

The server won't start — have I lost the data?

Most of the time you haven't. Server failures are typically caused by array metadata (on disk), controller state or file-system corruption on good disks. Shut the server down, do not click through more prompts and the odds will stay in your favour.

'Foreign Configuration Found' — what does that actually mean?

The Dell PERC is looking at array metadata on the disks that does not match what its own memory holds, after a board change, drives being moved, or a controller fault. The halt is just a precaution. Both options offered by the prompt could destroy data; if you create images of the disks before proceeding, there is no longer a risk with either option.

Is the array recoverable without its original card?

Yes. Each member carries the layout with it (PERC and MegaRAID provide standard DDF metadata, while HP provides RIS blocks). The reconstruction occurs at the bench using images and no matching controller is required.

Is it only files, or do VMs and databases come too?

Both, and the difference is significant. Restoring a VMDK or MDF file simply puts you halfway through, since you'll still have to persuade the hypervisor or database engine to mount it. That layer is what our VMware and database pages cover.

Whatever has gone wrong, keep it switched off.

Powering a damaged device up again costs you data. Start by opening a case instead; diagnosis is always free, regardless of your decision.

0800 6890668