A Synology DiskStation came up after a firmware upgrade reporting its volume as crashed and refusing to mount it. The disks were healthy — the problem sat in the software layers Synology builds on top of them. We imaged the members and reassembled the array and file system to bring the data back.
The DiskStation had run without complaint until a firmware upgrade, after which it booted but declared its storage volume “crashed” and would not bring it online. The disks themselves were fine; something in the upgrade had left the volume's software structures inconsistent. The business relied on the shares it held, and with no reliable separate copy, the unit was taken out of service and the disks brought in rather than risking a repair attempt on the appliance itself.
A Synology NAS doesn't simply format a disk. It layers software RAID (Linux mdadm) beneath a logical-volume manager, with an ext4 or Btrfs file system on top. A firmware upgrade touches these layers, and if the process is interrupted or a structure is left half-updated, the appliance can decide the volume is unsafe and refuse to mount it — even though the underlying data is intact. Recovering it means reassembling those layers, in the right order, away from the appliance that won't cooperate.
Each disk was cloned sector by sector through a write blocker and read cleanly. All work continued on the images, keeping the originals untouched — important, because reassembling a multi-layer stack involves trying and checking interpretations, and doing that on copies means nothing is ever at risk.
From the images, the Synology stack was rebuilt from the bottom up: the software-RAID members were reassembled into the array, the logical volume mapped out, and the file system located within it. Where the upgrade had left structures inconsistent, they were repaired against the file system's journal and redundant copies rather than trusted blindly, and the volume was then mounted read-only so its folder tree could be walked and the data extracted with names and structure intact.
Files were opened across the recovered shares to confirm they were whole, then returned on a fresh drive. About 98% came back, the small remainder tied to structures the upgrade had already overwritten. We flagged the usual point — a NAS is resilient day to day but is not itself a backup — and that keeping a separate copy makes even a botched upgrade a non-event.
Hardware imager with write blocker · Linux mdadm software-RAID and LVM reassembly · ext4/Btrfs repair and read-only mount. Read-only imaging, all work in-house in Belfast.
Send it to us for a free, no-obligation diagnostic. We’ll tell you what can be recovered and put a fixed price in writing before any work starts — and on most jobs, if we can’t get your data back, there’s nothing to pay. Post your device in, or drop it to us by appointment.
Yes, in the large majority of cases. A crashed-volume message after an update usually means the software layers are inconsistent while the data is intact. We image the disks and reassemble the array and file system independently of the appliance.
Be cautious — letting an appliance rebuild or re-initialise a volume it thinks is broken can overwrite recoverable data. If the files matter and there's no backup, power it down and send the disks in first.
Yes — both, along with the mdadm software RAID and LVM that Synology layers beneath them. Send all the disks, labelled with their order.