Often fixable yourself
NAS shows up but won't open
A NAS in this state is very often something you can resolve yourself, at no cost, and this page tells you how before it tells you anything about us. Where that doesn't work, the rest explains what the fault usually is and what recovery involves.
What this usually turns out to be
An array is a set of member disks plus the arrangement that binds them. Losing the arrangement loses the data even when every disk is healthy.
Corrupt filesystem metadatabetter news
The master file table or catalogue is damaged. The file content is intact and reachable; the map to it is not.
Interrupted write or unsafe removalbetter news
Power lost or the device pulled mid-write, leaving the filesystem in an inconsistent state. Usually very recoverable.
Bad sectors in the metadata region
The drive is degrading and the unreadable areas happen to be the ones holding the index. This case does have a clock on it.
Encryption without the key
BitLocker, FileVault or a NAS volume password. The data is intact but mathematically unreachable without the key or password.
Try this before you pay anyone
Genuinely recoverable at home, provided the drive itself is healthy
- First establish that the drive is not failing: no clicking, no beeping, no slow-then-stall behaviour, and it stays visible rather than dropping out. If any of those are present, stop, because scanning software will keep a dying drive spinning for hours and make things worse.
- Never scan the failing drive and write the output to the same drive. Recover to a different disk with more free space than the data you are recovering.
- TestDisk repairs lost partition tables and is free and open source. PhotoRec, from the same project, ignores the filesystem entirely and carves files out by signature, and it is the right tool when the index is gone.
- On Windows, Microsoft's own Windows File Recovery is free from the Microsoft Store. On a Mac, mount the disk read-only first if you can.
- Recover, verify you can actually open the files, and only then consider reformatting the original.
Carved files often come back without their original names and folder structure, because that information lived in the index that failed. That is normal and it is not a sign you did it wrong. If the drive is encrypted, none of this applies. No carving tool can read what it cannot decrypt.
How recoverable this is
Usually good, and often very good, because the media is intact and the fault is in the description of the data rather than in the data. The main determinant is not the original fault at all. It is whether a repair tool has already been run. Cases that arrive untouched tend to go well. Cases where chkdsk has already rewritten the structures are meaningfully harder, and sometimes that is what decides the outcome.
What moves it, for your device specifically:
- Whether a repair, format or chkdsk has already been run against it
- Whether the underlying media is healthy or has bad sectors
- Whether the volume is encrypted, and whether the key or password is available
- How much has been written to the device since the problem appeared
We will not give you a percentage for your device, and you should be wary of anyone who does. Nobody can know what is recoverable until the media has been imaged and read. What is above describes this class of failure; your drive gets its own answer after an assessment, in writing, at no cost.
What it costs
from $690
RAID, NAS and servers
Arrays rebuilt from the member disks rather than trusting the controller that failed. Any filesystem, including ext4, Btrfs, ZFS and VMFS.
What moves a job within its band: capacity, how much of the media is unstable, whether the filesystem is encrypted, and how much of the drive has to be read before the files you need are reachable. You get one fixed figure after the assessment and it does not move afterwards. If we can’t recover what matters to you, there is no recovery fee.
Not quite your situation?
Pick the device and what it is doing, and this gives you the same answer for that combination instead.