Open, and looking at it costs nothing · 9am–5:30pm, Mon to Fri Ring instead, it is quicker: 0115 8220606
NDR Nottingham Data Recovery 0115 8220606 Get my quote
NDR / By what it is doing / A partition reading as RAW

Cause of loss · a volume that has gone RAW

RAW drive recovery for Nottingham. The files never moved; what broke is the index, and indexes get rebuilt.

Refuse the format, then take the power off, whichever part of Nottingham the drive is in. Windows offers that box because offering it is all Windows can do: when a volume stops making sense to it, replacing that volume is the only remedy it knows. Meanwhile the hardware is usually unharmed and every file is where you left it — what has stopped adding up is the bookkeeping written across them. More data is destroyed by people saying yes to that box than by whatever put it on screen. Cards and sticks start at £250 + VAT and a single drive is £300 + VAT, the assessment before either is free, and there is no charge on most jobs where the data cannot be read back.

No files back, no bill — on most jobs Free diagnosis first, then a single price, in writing Parcels come in from Derby, Lincoln and Loughborough

Ask an engineer, and the first look is free
0115 8220606

What the symptom points to.

Not yours? Open the fault finder →
What it looks likeWhat usually causes itWhat that means for you
Drive not accessible, and Windows offers to format itThe file system no longer parses, so Windows falls back to calling the volume RAWTurn it down, then unplug it
Windows says CHKDSK is not available for RAW drivesThere is no file system left for CHKDSK to work on, so it refuses to runGet it off the PC
0x80070570 · file or directory corrupted and unreadableMFT entries that will no longer read backClose it, and stop opening folders
0x80070571 · disk structure corrupted and unreadableDamage in the partition table, or inside the MFTImage it first, mend it after
X:\ not accessible — the parameter is incorrect.Broken structures sitting above sectors that are failingAssume a hardware fault as well
It reports: …does not contain a recognized file systemNothing identifiable as a file system remainsYour files have not moved
The disk you inserted was not readable.Identical fault, macOS wording. Whatever you do, decline InitializeUnplug it, and refuse Initialize
How to pack and post it: pack it so nothing can move, value the parcel at what the data is worth to you rather than what the hardware cost, and use a tracked service to the intake lab. Postage back is ours. Would you rather an engineer talked the packing through first? Ring before you seal the box. All of it is set out on the packing and postage guide.

Which structure on the RAW drive gave out.

When the boot sector goesThe opening sectors of a volume, holding the values Windows insists on seeing before it will mount anything. Small structure, alarming symptoms, and usually repairable.
NTFS: the Master File TableEvery file on the volume is indexed here, together with the point each one begins at. Damage a stretch of those entries and 0x80070570 lands on screen, while the clusters carrying the files sit there completely untouched.
The partition table, goneThe map of where one volume finishes and another starts. Lose it and a disk full of work reports itself as unallocated space, nothing more. Restore the entries and the volumes come straight back.
CHKDSK has nothing to offerCHKDSK will not run at all against a RAW volume, so there is no upside to it. There is a downside: on a worn drive its repair passes keep returning to the same fragile sectors. Do that on an image instead, and leave the original alone.

From the parcel arriving to the files going home.

Jobs already finished →
01

Booked in the day it arrives, and the first look is on us Free

Your device picks up a case number the day it arrives, and an engineer then establishes what has genuinely gone wrong — at no cost, and ahead of everything else. Two things come back to you together: a plain account of what can be lifted and what cannot, and one fixed figure in writing. Agree to that figure, or turn it down and pay nothing.

The first look is freeOne fixed figure, in writingNo charge at this point
02

Nothing is touched before the image

Nothing gets repaired until a copy exists — taken sector by sector, with the slow areas noted and saved for last. A damaged structure and a tired mechanism usually turn up together, and one image handles both.

Slow areas noted, left till lastYour drive is never written to
03

Rebuilt on the image, not the disk

Partition table, boot sector and MFT are put back together on the copy. Your own disk is never written to, and any step that turns out badly can be undone and taken again.

Any step can be undoneYour own disk comes back untouched
04

If the index cannot be repaired

However far gone the MFT may be, the contents of a file stay in the clusters they have always occupied. Each is lifted out of the image by the signature its format begins with, and whatever tree the surviving records can still support is built back around them.

Identified by their file headersFolder tree kept where it survives
05

The file list comes before the bill

The file list reaches you before any invoice does. Say yes and it is billed; say no and it is not — and on most jobs, if nothing comes back there is nothing to pay. Whatever comes off goes home on media bought in for your case, carriage at our end. Nothing here is closed until you have opened those files on your own machine.

Nothing is charged until you agree the figureNew media, bought in for your jobWe pay to send it home

What comes in most often

  • Unreadable does not mean empty — work on the copy, repair it there, and the volume normally opens again with its contents intact.
  • Format costs you more than the corruption did — a single click puts a blank file system exactly where the records a rebuild needs are sitting.
  • Corruption seldom arrives alone — bad sectors keep spreading until the metadata is within range, which is why nothing here is treated as purely logical until an image has proved that it is.
  • NTFS keeps spares of its own — every NTFS volume carries a copy of the first few records of its MFT plus a spare boot sector. Neither holds the file records themselves, but the pair is what lets a rebuild find the structures again; the MFT itself is what then gets read.

One habit unites them all: CHKDSK, Disk Utility's First Aid, whatever free RAW repairer a forum is recommending this month — each of them puts writes onto the disk it is meant to be mending. With sound hardware underneath you get away with it. With failing hardware, a job that would have come back complete comes back in pieces. Imaging takes a day. A free assessment tells you which sort of disk you are holding, and it costs nothing to ask.

One of these, from start to finish.

NG · NTG-2026-1783ON THE LOG ✓

Unplugged mid-write, and Windows called the volume RAW

A cable caught mid-write, and by morning the only thing Windows would offer was a format. Before anything else, an end-to-end image was taken of the 4TB, and every repair after that was done to that copy: boot sector, then the damaged mirror of the MFT. The original was never written to at all. Fifteen years of client files came back with the folder tree the way it was.

100% of the files back3 days between arrival and return

What helps, and what does damage.

Worth doing first

  • Say no to Format, and no to Initialize
  • Switch it off and set it aside
  • Was anything unusual going on first — a power cut, a cable out mid-write?
  • Say whether anybody has already run CHKDSK against it

What makes it harder

  • Pressing Format, or Initialize on a Mac
  • CHKDSK /f or /r aimed at a disk you already distrust
  • Turning a free RAW repairer loose on the original
  • Clicking through the folders to see what survived

Answers before you spend anything.

Windows keeps pushing me to format it. Should I?

Say no. Formatting cleans nothing — it lays a fresh file system down on top of the damaged one, and where it lands is exactly on the records carrying your folder names, your dates and the shape of the tree. Those records are the raw material any rebuild is made out of.

What is RAW telling me, exactly?

That the structures describing the volume can no longer be read: the MFT, the boot sector, the partition table, or some combination. Everything those structures describe is still sitting exactly where it was written.

Would CHKDSK help at all?

It cannot even start on a RAW volume, so the gain is nil. The cost is real, though: on a worn disk every repair pass spends a little more of what remains. That work belongs on a copy.

It turned RAW right after I yanked the cable. Did I do this?

Quite possibly, and it is one of the commoner ways to end up here. Interrupt a write and the index is left half-finished, still pointing at files that were never touched by any of it.

Switched off, a drive cannot get any worse.

The look costs nothing. What comes back to you is a file list — what opened, what did not — plus one figure to finish the job, in writing, before anything chargeable begins. Most jobs carry no fee at all unless the data comes back. Leave the drive switched off until you have that list.

0115 8220606