His account is unusually precise, and the precision points somewhere hopeful. An old WD Cloud NAS holds photos and documents; it "powers on and shows that files exist on the device", and he notes "There is no evidence the data is corrupt or encrypted". It appears as a network device, but clicking to view files "it opens "twonky" in the browser and no files are listed". A NAS that powers, reports data present, and lists nothing through a media server has a sharing or configuration fault, not a failed disk — the data is very likely sitting intact on a healthy drive that the NAS is simply no longer presenting correctly.
| Media | WD My Cloud NAS — powering, visible on the network, indicating files are present, but serving no file listing; access attempts land on the Twonky media server showing nothing. |
| Reported situation | NAS powers on and reports data exists · appears as a network device over Ethernet · file access opens Twonky in a browser with no files listed · no sign of corruption or encryption · photos and documents wanted. |
| Fault class | Configuration or file-sharing failure on a functioning NAS — the drive and its data likely intact, the sharing services or user permissions misbehaving, distinct from disk failure or corruption. |
| Equipment used | Drive removed and imaged under a hardware write-blocker before any change, so nothing on the NAS is altered · the drive's Linux filesystem read directly from the image in UFS Explorer, bypassing the NAS's sharing layer entirely · data located and verified independently of Twonky and the NAS's own file services · recovered photos and documents extracted with folder structure, validated by rendering. |
The NAS reporting files present is the crucial clue, and it is good news. That the device powers, appears on the network, and indicates data exists means the disk is spinning, readable, and holding data — the hardware is working. What is failing is the layer that presents those files to him, not the storage itself. A dead disk does not report that files exist; a misconfigured one does.
Twonky opening instead of a file listing points straight at the sharing layer. Twonky is a media-server application that streams media to devices — it is not the way to browse a NAS's full file store. Being routed to Twonky, which then lists nothing, suggests the NAS's normal file-sharing services are not responding correctly, so access falls through to the media server, which only ever indexes certain media and is showing an empty or stale index. The files are not in Twonky's remit; that is a symptom of the sharing services being down, not of missing data.
His own read — no corruption, no encryption — is very plausibly right. These NAS faults commonly arise from the device's software: user accounts or share permissions that reset, sharing services that fail to start after an update or a power event, or configuration that drifted on ageing firmware. None of that touches the data on the disk. The photos and documents remain intact; the NAS has simply lost the ability to hand them over through its normal front door.
The recovery bypasses the NAS entirely, which is what makes it clean. Rather than fighting the NAS's broken sharing layer, the drive is removed and its filesystem read directly. My Cloud drives store data on a Linux-format volume that a desktop does not read natively, but the right tools read it straight from an image — reaching the files at the storage level, underneath Twonky and the permissions and services that are misbehaving. The malfunctioning software is stepped around, not repaired.
Imaging first guarantees nothing is disturbed. The drive is imaged under write-blocking before anything, so no attempt to coax the NAS back, no permissions change, and no firmware reset can put the data at risk. All work happens on the copy, which matters because the data is intact and the only real danger would be an intervention that damaged a currently-healthy volume.
The honest prognosis is strong, with a small caveat. A NAS reporting files present, with a healthy-appearing disk, almost always yields its data in full via direct filesystem reading. The one caveat, confirmed at assessment, is that the drive is genuinely healthy rather than beginning to fail behind the software symptoms — checked before the work, with the recoverable content confirmed before any charge.
The drive was removed and imaged under a hardware write-blocker before any change to the NAS. Its Linux filesystem was read directly from the image in UFS Explorer, bypassing the NAS's sharing layer entirely, and the data located and verified independently of Twonky and the NAS's own file services. The recovered photos and documents were extracted with their folder structure and validated by rendering.
NAS drive imaged untouched, its filesystem read directly beneath the broken sharing layer, and the data extracted with organisation. The diagnostic costs nothing and completes within two working days of arrival, and the quote is one fixed written figure with VAT already in it; if the data can't be brought back, no charge is made. The decode: the NAS showing files present means the disk is healthy — the failure is in how it serves them, not the data. Read straight from the drive, underneath Twonky and the permissions that broke, your photos and documents come back.
Don't reset the NAS to factory settings or rebuild its configuration hoping the files return — those steps can wipe or reformat the disk that still holds your intact data. A NAS reporting files present with a healthy disk usually has a sharing or permissions fault, not a data loss, and being routed to a media server like Twonky is a symptom of that. The data is best reached by reading the drive directly at the filesystem level, so preserve the NAS as-is.
Our case files are written up from genuine enquiries our lab has handled for customers across Swansea and South Wales, anonymised to protect client confidentiality. Each one describes the diagnostic and recovery approach our engineers apply to that fault, using the equipment listed.
Free diagnostic, fixed quote, no fix no fee — start now or call the freephone.