A haulage office off the dock road kept its paperwork on a Seagate wireless drive. The network name still appeared on every laptop in the building. The files behind it did not. The Wi-Fi shows, sort of, but I cannot see it any more, the office manager wrote, with about 1TB of manifests and scanned dockets wanted on something ordinary she could plug in.
| Media | A Seagate wireless external drive, roughly 1TB in use, still broadcasting its network but no longer presenting its files to any machine in the office. |
| What was reported | Seagate wireless drive, network name still visible from laptops, files no longer reachable, around 1TB of scanned paperwork and manifests needed on a plain drive. |
| Fault class | The wireless enclosure. The radio and its controller were still powered, which is why the network showed, but the bridge serving the disk had failed. The disk itself was sound. |
| On the bench | Drive lifted out of the wireless enclosure and read directly behind a hardware write blocker on PC-3000 UDMA, health and firmware profiled, imaged on DeepSpar, the partition table and filesystem parsed in R-Studio, files validated and written to a plain USB drive. |
A wireless drive is two products in one shell. There is a disk, and there is a small computer with a radio that serves the disk over a network. They fail separately. When the radio is alive and the disk is not reachable, what you get is exactly what the office saw: a network name that still appears in the list, and nothing behind it.
The network name showing is good news, not bad. It proves the enclosure is receiving power and its controller is running. That narrows the fault to the link between that controller and the disk, or to the disk itself, and those are both things a bench can reach directly by refusing to use the wireless path at all.
Taking the disk out is the whole trick. Inside the shell is an ordinary drive on an ordinary interface. Read it on the bench and the radio, the app, the firmware of the enclosure and every other layer that failed simply stop being part of the problem.
This one was the enclosure, and the disk was clean. No head work, no board work, no clean air. The disk imaged first time and the paperwork was all there. It is worth saying plainly because it is common: a great many wireless and network drive failures are the box, not the disk.
The enclosure was opened and the drive removed. From that point nothing wireless was involved. The drive went behind a hardware write blocker onto PC-3000 UDMA, where its health and firmware were profiled. It came ready without argument, and the surface read cleanly, which confirmed the enclosure as the fault rather than the disk.
It was imaged on DeepSpar, the partition table and filesystem parsed in R-Studio from the image, and the manifests, dockets and scanned paperwork validated by opening a sample from each year. The whole set was written to a plain USB drive that anybody in the office can plug into anything.
About a terabyte of scanned paperwork came back complete on a drive with no radio in it, which is what she had asked for. The old enclosure was returned in the box, still broadcasting, still useless.
This is one drive, so it is £300 + VAT, not the £500 + VAT that arrays, NAS boxes and servers start at. The work was logical throughout, with no board repair and nothing opened in clean air, so it ran on no fix, no fee terms.
Do not keep resetting the box. Factory resets on wireless and network drives are aimed at the enclosure's own configuration, and on some models that includes rewriting or reinitialising the volume on the disk behind it, which is the one thing standing between you and your files. Do not let a rebuild run either. Power the unit down, leave it alone, and send it as it is. If the disk is sound, and on this class of failure it very often is, the recovery is a straight read once it is out of the shell.
Every case file here is written up from a real enquiry handled for households and businesses across Liverpool, Merseyside and the wider North West, anonymised so that nobody is identifiable. Each one gives the reasoning behind the diagnosis, the method the fault actually called for, and the equipment it was worked on.
An impacted drive has a head fault, and years of home attempts do not change what is sitting on the platters
Clicking is a head fault and a rattle after a knock is usually loose hardware, and both are settled in one clean-air visit
A drive that needs the cable held at an angle has a failing joint at the port, and it always gets worse
The diagnostic is free and takes 2 working days from arrival, the figure is fixed in writing, and logical faults run on no fix, no fee. Start online or ring the freephone.