A design studio accidentally initialised its four-bay Synology DiskStation during a reconfiguration. It rebooted looking perfectly healthy and completely empty — the entire project portfolio apparently gone, and Synology’s own tools finding nothing. The saving grace: initialising a RAID writes a new empty label, but it does not scrub what is underneath.
A design studio’s Synology DiskStation, four drives, was accidentally initialised during a reconfiguration. The box came back up looking healthy and completely empty: the whole project portfolio — CAD files, artwork, client documents — apparently gone. Synology’s own recovery options had found nothing.
Here is the reprieve that makes this recoverable: initialising a RAID array does not scrub the disks. It writes fresh array metadata and a new, empty file system — a new label on the shelves — but the actual data blocks underneath are left almost entirely in place, at least until the array is used again and new writes start landing on them. Which is why the one thing that matters after an accidental initialisation is to stop using it immediately, and why this studio still had a portfolio to recover.
All four disks were pulled, write-blocked and imaged — the NAS itself set aside entirely, since anything done on the live box risks writing over the very blocks being recovered. Working from the images, the old array geometry was reconstructed: the original stripe size, disk order and parity layout determined from the surviving data patterns rather than the new, empty metadata the initialisation had written on top.
With the original array reassembled virtually, the previous file system was read directly from it — underneath the fresh empty one — and the studio’s folders reappeared with their structure intact. None of it touched the Synology; it was all done on copies, which is the only safe way to read past a layer of new metadata to the data it is sitting on.
The CAD projects, high-resolution artwork and client documentation came back with their original folder structure, verified, and returned on fresh storage. The studio lost no billable work.
An accidental initialisation or “create new volume” is far more survivable than it feels, but only if you act on one instinct: stop using the system immediately. The data sits under the new empty file system until fresh writes land on it, so every hour of continued use is a chance to overwrite what is still recoverable. Do not let it rebuild, resync or re-initialise again.
Power it down, send the disks in bay order, and let them be imaged. The free diagnostic will tell you how much of the old volume survives before anything is charged.