Taking in new cases now · 9am–5:30pm, weekdays In a rush? Ring 0800 6890668
BHDR Birmingham Data Recovery 0800 6890668 Get it seen
BHDR / Faults we see / RAW and corrupt file systems

Cause of loss · corruption & RAW

RAW drive recovery, Birmingham. Nothing is erased; the index that finds your files can be put back.

Windows has one answer for a volume it cannot read, and that answer is Format. It can see the disk. It cannot make sense of the structures written on it. So it offers the only tool in its box. Most files lost to corruption go in the few minutes after that box appears, not to the corruption itself.

Nothing recovered, nothing to pay Diagnosed free, then one fixed price From Walsall, Dudley or Coventry, it travels by post

Tell an engineer what it is doing
0800 6890668

Reading the RAW-volume symptoms, one by one.

No match here? Run the triage →
SymptomsWhat is behind itWhat to do
You need to format the disk in drive X: before you can use itThe file system is unreadable to Windows, and RAW is what it calls thatNever press Format
CHKDSK is not available for RAW drives. File system type: RAW.CHKDSK declining the job; it has nothing it can repairUnplug it and stop
File or directory corrupted and unreadable (0x80070570)MFT entries Windows can no longer readClose the window, stop looking
Disk structure is corrupted and unreadable (0x80070571)Damage in the partition table or the MFTCopy it first, repair second
Location is not available. The parameter is incorrect. X:\ cannot be accessed.Structural damage with bad sectors underneath itTreat the disk as dying
Windows: no recognized file system on this driveNothing left of the file-system metadataThe file data is still below
On a Mac: this disk is not readable by the computerRAW under another name; the button not to press is InitializePress Eject, never Initialize
Sending it by post: send it tracked and fully insured to our intake lab, and we cover the postage coming back; if you want the packing checked before it goes, an engineer will talk it through with you. Every step is written out on the posting page.

The structures that fail.

A broken boot sectorA few sectors right at the front of the volume, carrying the values Windows has to have before it can read a byte. Tiny structure, alarming symptoms, and normally repairable.
NTFS's Master File TableThe catalogue NTFS keeps of every file on the volume, including where each one begins. Break a few entries and 0x80070570 shows up, though the data those entries point at reads perfectly well.
Partition table goneThe map the disk holds of where every volume begins and ends. Lose that and a full drive shows up as blank, unallocated space. Get the entries right again and the volumes come straight back.
CHKDSK: all risk, no returnSet CHKDSK on a RAW volume and it refuses to start, so there is nothing on the credit side. On the debit side, if the drive is tired, its repair passes hammer the same weak sectors over and over. Structural work belongs on a copy, not the disk.

From arrival to the files going home.

Recent jobs on record →
01

Case opened, and the diagnosis costs nothing Free

Every item gets a case number of its own the day it lands. An engineer then works out what has actually failed and tells you plainly which files have a real chance of coming back and which do not. Only then does a price follow: one figure, fixed, in writing, and it costs you nothing to see it. Nothing is charged until you say yes.

The diagnosis is freeOne price, put in writingNothing agreed
02

The copy is taken first

Before anything is repaired the disk is copied sector by sector, and any region that reads badly is logged and left until the end. Damaged structures and dying hardware usually turn up together, so the copy covers you against both at once.

Bad areas loggedWe do not write to the original
03

The repairs go on the image

Boot sector, partition table and MFT are all put back on the image, never on your drive, so anything that goes the wrong way can be wound back.

Every step can be undoneThe drive returns as it came
04

If nothing can be rebuilt

Whatever has happened to the MFT, the contents are still in the same clusters. Each file is lifted out of the image by its signature, and as much of the folder tree goes back as the remaining evidence supports.

Carved out by file signatureFolder tree put back together
05

Approved by you, then posted back

No invoice is raised until the full list of recovered files has sat in front of you and you have said go ahead. Your data comes back on media we buy new, posted at our expense, and the job is not closed here until every file has opened on your own machine.

Your say-so on the file listYour data on new mediaWe cover the postage back

What the first look turns up

  • A drive Windows cannot read is not a drive that has been wiped — image it, work on the copy, and the volume normally mounts again with the lot still on it.
  • Most of the damage we see was done by that Format button — press it and a blank file system is written straight over the records a rebuild needs.
  • Corruption is often the sign of something else — bad sectors spread, eating metadata on the way, so nothing is called a purely logical fault until the imaging has said so.
  • NTFS holds a spare of its own — there is a mirror of the MFT and a second copy of the boot sector, and a rebuild is generally put together out of those.

One thing links every repair tool: CHKDSK, First Aid in Disk Utility, whichever free RAW fixer a forum points you at — all of them write to the disk they are supposed to be saving. If the hardware underneath is healthy, that generally does no harm. If it is not, a job that could have come back whole comes back in pieces instead. Waiting a day for an image is all that caution costs.

Recent pages of the casebook.

BH · BHD-2026-8633RECORDED ✓

A 4TB archive pulled mid-write, and Windows saw RAW

The lead came out of the socket while a write was still running, and by the next morning Windows had nothing to offer but a format prompt. An image of the whole disk came first. The boot sector and the damaged MFT mirror were then repaired on that image alone. Fifteen years of client work went back with the folders as they had been.

100% recovered3 days from arrival

Before the parcel goes.

Do this first

  • Say no to Format and to Initialize
  • Switch it off and leave it alone
  • Cast your mind back: a power cut, or a yanked cable?
  • Tell us if CHKDSK has already run on it

What not to do

  • Accepting the Format dialog, or Initialize on a Mac
  • Turning CHKDSK /f or /r loose on hardware you already suspect
  • Grabbing a free fixer off the web and pointing it at the disk
  • Opening folder after folder to check what survived

The questions that come up every week.

Windows keeps asking me to format the disk. What happens if I let it?

Say no. A format lays a blank file system down on top of the broken one, and the structures that still hold your folder names and dates are the first thing it lands on. Those are what a rebuild works from.

Why does Windows call it RAW?

Because it can no longer read the structures that describe the volume. That damage usually sits in the boot sector, the partition table or the MFT. The files themselves are still down there, whole.

Should I run CHKDSK on it?

It will not even start on a RAW volume, so there is nothing to win. Set against that, if the disk is already tiring, each pass takes more out of it. Repair work belongs on an image, not the original.

I unplugged it without ejecting and it went RAW. My doing?

Probably, and you are not the first. Pull the cable mid-write and the index ends up describing a state that never finished, while the files it points to sit there intact.

Nothing more is lost while the power stays off.

Every extra power-up takes something off a drive that is already going. Leave it switched off and let the free diagnosis say what still reads.

0800 6890668