Home / Case Studies / NAS & Network Storage
NAS & Network Storage · case file

The Folders Stopped Showing

Intermittent faults buy themselves time by healing just often enough. The folders on this wireless WD My Book World "would't show", the owner told us, and it had "happend alot but always come back" — until the day it didn't, leaving the shares "not showing on my xbox media player nor my computer". A network drive that flickers like that isn't having connection trouble; it's failing on instalments, the disk or its filesystem stumbling a little more each time. When a network drive finally goes dark, the network is the wrong place to look — the disk comes out of the enclosure and is read directly, where Wi-Fi, shares and media players no longer get a vote.

RAID / NASHard DriveNot DetectedCorruption / Filesystem
// case at a glance
MediaA wireless WD My Book World network drive — folders intermittently vanishing for months, now gone from every device on the network.
Reported situationWD My Book World · folders disappearing and returning over a long period · now absent on the media player and the computer alike · contents wanted.
Fault classFailing disk or damaged filesystem inside the network enclosure — the unit can no longer serve its shares. Data ordinarily intact on the disk itself; reached by direct reading out of the enclosure and rebuilding the Linux-based volume from an image.
Equipment usedDisk removed from the network enclosure and connected directly — PC-3000 UDMA behind a hardware write-blocker, health and weak areas assessed; DeepSpar read-only imaging in managed passes where the disk is degrading; the enclosure's Linux-based volume parsed and rebuilt from the image in R-Studio and UFS Explorer, folders restored and verified onto fresh media.
// the decode

The decode

A pattern of folders vanishing and returning teaches most owners the wrong lesson: that the problem passes. What's actually happening inside a little network enclosure like this is a disk beginning to struggle — reads timing out, the embedded system stumbling over them, shares dropping and then limping back when a retry lands. Every 'it came back' was a successful retry, not a recovery. The final silence is the same fault, finished.

Off the network is the only sensible place to work on it now. The enclosure adds three layers of suspects — Wi-Fi, the embedded server, the media player's expectations — and all three are noise once the disk itself is in hand. Direct connection answers the real questions in minutes: how healthy is the disk, and what state is the volume in? These little network units also keep their data in a Linux-arranged volume that a Windows machine can't read even when the disk is perfectly well — one more reason the DIY route dead-ends here, and no reflection on the data's condition.

The months of flickering do add one instruction: gently. A disk that's been failing on instalments gets imaged read-only in managed passes — the strong areas banked first, the weak ones revisited on their own terms — and the folder structure is rebuilt from the image, never from the tiring original.

// on the bench

On the bench

Enclosure opened, disk out, and onto PC-3000 UDMA behind a write-blocker — the network never consulted again. Health assessed, weak regions mapped, then a read-only DeepSpar image in careful passes. From the image, the Linux-based volume is parsed in R-Studio and UFS Explorer, the vanishing folders rebuilt in full, and the contents verified out onto fresh media readable on an ordinary computer.

// the outcome

The outcome

The folders that came and went, recovered from a copy that can't do either. Assessment is free and reported within two working days of the unit arriving, followed by one fixed figure in writing. Where the recovery stays at disk-and-filesystem level it runs as logical work — no fix, no fee; if the disk itself needs opening, that clean-air stage takes half up front with the balance due only on success.

A network drive acting intermittent

Treat the first vanishing as the warning it is: copy everything off while a good retry lasts, because each return is borrowed time. Once it's gone dark for good, don't reboot it on a loop and don't factory-reset the enclosure — reset routines can re-initialise the very volume you're hoping to keep. Unplug it at the wall, leave the disk inside, and send the whole unit as it is. One box in the post beats another month of hoping the folders come back on their own.

Got one like this in York? Every case here starts the same unhurried way: a free diagnostic, finished inside 2 working days of your media reaching the bench, then one written quote that stays put. Logical faults run no fix, no fee; anything that means opening the drive — mechanical, electrical, water or fire damage — takes 50% of the quote up front; ransomware, CCTV, BitLocker and other forensic-classed jobs are payable up front in full. If the data sits inside a laptop, PC, Mac or server, take the hard drive or SSD out and post the drive alone — we don’t offer an internal drive-removal service, and storage soldered to a motherboard (Apple Silicon Macs and the like) is outside our intake; a drive that unplugs or unscrews is what the bench works on. Send it tracked and insured to Leeds Data Recovery, 17th Floor, The Pinnacle, Albion Street, Leeds, LS1 5AA — packing notes and the shipping form are here.
Start a free diagnostic

Every case file on this site is written up from a genuine enquiry handled for customers across York and North Yorkshire, anonymised to keep client confidence. Each one sets out the diagnostic reasoning and the recovery method our engineers apply to that fault, on the equipment named.

// related case files

More cases like this one

Browse all case studies →

Recognise your own drive in this one?

Free diagnostic inside 2 working days of arrival, one fixed quote, no fix no fee on logical faults — start online or ring the freephone.