NAS and network storage · ADR-2025-3171
The Unit Read Its Own Fault Out Loud.
He had done the reading before he wrote to us. On power-up his Buffalo Linkstation played out an error sound followed by 6 flashes
, and the manual is explicit about what that combination means: it is an indication of hard drive no longer being recognised
. Having worked that out, he stopped putting the unit through further starts and asked about the data instead, which is the right order to do those two things in.
Same story on yours? Tell us what it does — the look is free.
0203 0868633
What failed, and why.
An error code is a diagnosis the unit has already made about itself, and this one is unusually specific. It is not reporting a network problem, a share it cannot mount or software it cannot run: it is reporting a disk it can no longer recognise. That puts the work within the case rather than around it. A disk stops presenting itself for one of three reasons — its firmware will not come up, its board has a fault, or the mechanism itself has gone — and from outside they are indistinguishable from one another. Each wants different handling, which is why the assessment comes ahead of everything else, and why nothing at all is settled by putting the unit through another start.
What the bench did with it.
The order of the job →| Equipment used | Its work on this job | The reason for it |
|---|---|---|
| DeepSpar Disk Imager 4 | Copied once the disk would present itself, with retries held to a limit | Heads mapped first, then one platter side to a pass, with every reset, every timeout and the power itself kept under our own control |
| UFS Explorer Professional Recovery | The unit's Linux volume opened off the copy and read out | Opens APFS, ReFS, XFS, ZFS and Btrfs when other software will not |
| ACE Lab PC-3000 Express | Into the service area, where the fault was established | Gets into the manufacturer's service area, where ordinary ATA commands cannot go |
What the bench did with it.
Stop starting the unit and take the disk out of it
Nothing more was asked of the Linkstation. The signal it gives is not a fault that clears on the next attempt, and where a mechanism is involved every further start is a risk run for no information at all. The disk was lifted out and put in front of equipment that can reach it directly, which is the only place the question of why it stopped being recognised can actually be answered.
Establish which of the three faults it is
The service area was reached first, since a disk that cannot bring its own firmware up will never introduce itself to anything. The board was examined and the current draw was watched. Only once that is settled does a route exist: what gets addressed, in what order, and whether the mechanism has to be opened at all.
A NAS disk does not read like a PC disk
Fitting the disk to a computer would have shown unformatted space and proved nothing. What a network unit writes is a Linux volume, usually with a manager placed above the partition table, so the copy was opened with software built for that and the shares came back with their folders.
What went home.
The data was read off the copy rather than out of the unit, and it went home on fresh media with the folders as the shares had them. The Linkstation was not returned to service. NAS and array work opens at the published £500 + VAT, and the assessment ahead of it is not charged for.
Begin here if yours is doing the same thing.
More Apple machines, written up.
Yours doing something similar? Power it down first.
Prices are published and fixed. Memory cards and USB sticks are priced at £250 + VAT. A drive on its own comes to £300 + VAT. Anything holding a second disk, whether RAID, NAS or a server, opens at £500 + VAT. The first look costs nothing, and the figure that follows is fixed and in writing before a penny is charged. Switch it off and post it in. Most jobs carry no fee where no files return.