Data Recovery Case File · NAS & Network Storage · Past the Filesystem Question
His Linux Attempt Ruled Out the Obvious Answer
His enquiry contains an elimination that most people never perform. A network unit showing a flashing red indicator: "I took out the hard drive to connect via a SATA cable, but Windows shows that there is no media. I had no luck with a few Linux tools either." The usual explanation for a network drive showing nothing on Windows is the filesystem. He tested that and it was not the answer — which is worth a great deal, because it moves the diagnosis somewhere much more specific.
| Media | Hard drive removed from a single-bay network storage unit — host reporting no media present; Linux tooling likewise unsuccessful; unit indicating a failed member |
| Reported situation | Network unit ceasing to function with a flashing failure indicator · drive removed and connected directly · Windows reporting no media present · Linux tools attempted without success · contents required |
| Fault class | Drive not presenting capacity — failure below the filesystem layer; unit's failure indication consistent |
| Equipment used | Owner's cross-platform attempt accepted as filesystem elimination · assessed on a native connection with readiness sequence read directly under strict timeouts · service area assessment in technological modes (PC-3000 Express) · imaging on restored addressing · appliance volume layer interpreted after capture |
The decode: what he ruled out, and what is left
Why the obvious explanation exists: network storage units run a Linux-based system and format their disks with Linux filesystems. Connect one of those disks to a Windows machine and it will not present a usable volume — not because anything is wrong, but because Windows does not read that format. That accounts for a large proportion of enquiries about NAS disks showing nothing, and the remedy is simply to read them on a system that understands the format.
Why his attempt matters: he tried Linux tools, which do read those filesystems. Getting nothing there eliminates the format question entirely. Most people never take that step — they see nothing on Windows, conclude the disk is dead, and are frequently wrong. He has proved it properly.
Why "no media" is the stronger phrasing: a disk with an unreadable filesystem still appears — the system sees a device of a stated capacity and reports that it cannot interpret the volume on it. No media means something different: the host is not being told there is any storage at all. That is below the filesystem, below partitioning, and below anything a different operating system could help with, which is precisely why the Linux attempt also returned nothing.
Where that places the fault: the drive is not completing the start-up that lets it report its capacity and geometry. Most often that means it cannot read its own service area — the reserved region holding firmware, calibration and defect maps, which must be read successfully on every power-up before the drive can identify itself.
Why that is a reasonable place to be: the service area is separate from where user data lives. A drive unable to read its own configuration still holds every file, and the region is addressed in the drive's technological modes, after which it images conventionally.
Why the unit's indicator is consistent: the flashing failure light was the appliance reporting that it could not use the member. It reached the same conclusion the two operating systems did, from the same cause.
What happens after the drive is readable: the appliance's own volume layer is interpreted on the captured image — many units place their filesystem inside a volume-management layer rather than directly on the disk, which is a second step and one best done against a copy rather than the drive.
On the bench
The owner's cross-platform attempt was accepted as filesystem elimination — network units formatting their disks with Linux filesystems that Windows cannot read, so a Linux attempt returning nothing rules out the commonest explanation entirely. The drive was assessed on a native connection with the readiness sequence read directly under strict timeouts, service area assessment performed in technological modes on the PC-3000 Express, and imaging on restored addressing. The appliance volume layer was interpreted after capture, against the image rather than the drive.
The outcome
The filesystem question eliminated by the owner, the service area repaired and the drive imaged before the appliance's volume layer was interpreted. Free assessment, one fixed written figure including VAT; where a drive has to be opened, 50% of parts and labour is payable upfront with the balance only on success — otherwise no recovery, no fee. The decode: network units use Linux filesystems Windows cannot read, which explains most NAS disks showing nothing — and trying Linux tools is the step that rules it out. "No media" is stronger than an unreadable filesystem: it means no capacity is being reported at all, which is below anything an operating system can address.
NAS disk showing nothing when connected directly
Try reading it on Linux before concluding anything — network units run a Linux-based system and format their disks with filesystems Windows simply doesn't read, which accounts for a large share of these enquiries and is fixed by using the right system rather than by any recovery at all. If you've done that and still got nothing, you've eliminated the commonest explanation properly, which most people never do. Worth noting the exact wording too: a disk with an unreadable filesystem still appears, with the system reporting a device of known capacity that it can't interpret. "No media" means the host isn't being told there's any storage there at all, which sits below the filesystem and below partitioning — so no operating system could have helped.
Your Linux test settled it — call Guildford Data Recovery on 01483 901310; readiness read under strict timeouts, service area repaired in technological mode, appliance volume layer interpreted against the image.
Request a quote online →
Our case files are drawn from genuine enquiries received by our laboratory over the past ten years, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery procedure our engineers apply to that fault, using the equipment listed.