Read the relevant page, build a recovery brief, call an engineer, or send the case securely, without opening a second popup.
Problem, device and brand cards are normal page links. The assessment button builds a saved recovery brief.
Choose the closest description. If you arrived from a problem card, this step is already complete.
Brand, model family, exact model and capacity improve the handoff to the correct engineer.
Tick everything that applies. “Other” fields are available where the usual choices do not fit.
This is an intake guide, not a remote diagnosis or guarantee. The laboratory confirms the method, quote and limitations after assessment.
Read the recovery method, limitations and intake process for this device or issue.
Read the relevant pageBest for uncertainty, dangerous batteries, active incidents, legal deadlines and Emergency 24/7.
Call 1300 806 557Keep the menu open and load Wildfire’s secure submission form in this same full-screen panel.
Save the structured summary for a call, email, internal approval or later submission.
★ 4.8 · 96 Google reviewsBrisbane laboratoryFree Australia-wide post-in
Storage pool crashed, power light blinking, or DSM asking to install.
A Synology joins its drives with SHR or classic RAID, both built on Linux RAID, and keeps your shared folders on a Btrfs or ext4 volume on top. We image every drive and M.2 cache SSD first, then put SHR and the volume back together in software, working only from the images. DiskStation, RackStation and FlashStation units, DSM 6.2 to DSM 7.4.
Decode your Synology’s light or messageReviewed by Viktor Burcevski, last reviewed
Drag the slider to lift the drives out of the Synology and slide them back, or open the story to see what Degraded and Crashed mean inside the unit.
Four drives, one SHR pool.
SHR joins the drives with Linux RAID and puts one Btrfs or ext4 volume on top. Your shared folders live in that volume, spread across every drive.
Drive 2 drops out: Degraded.
DSM keeps serving files from the other three. Synology says no data has been lost at this point; the pool simply has no spare copy left.
Drive 4 goes too: Crashed.
More drives are out than SHR-1 can survive, the allocation status shows Crashed and the shares go offline. Synology says the owner can no longer repair it, but the files are normally still on the drives.
How the files come back.
Each drive is copied in full, the SHR layout is put back together from the copies, and the volume is read in software. Nothing is written to the drives you sent.

Who signs off every Synology job
Executive Data Engineer / Executive Forensic Consultant
Viktor reads the image of every drive and cache SSD that comes in, works out how DSM built the SHR pool, and checks your file list before anything is invoiced.
Crashed SHR-1 and SHR-2 pools, read-write cache sets rejoined with their hard drives, encrypted volumes opened with the owner's own recovery keys, and ransomware cases where the drives are kept as evidence.
The 20-second answer
Usually. A failed drive, a dead unit or a broken SHR layer rarely touches the files themselves. Crashed means DSM can no longer repair the pool on its own, not that your folders are gone.
Read the exact word in Storage Manager or Synology Assistant, then shut down from DSM or hold the power button until it beeps, and number each drive by bay. Call first if a Repair is running or a crashed volume still opens.
Every drive and cache SSD is assessed free and you get one fixed written quote with a time estimate. The price follows how many drives there are, how they failed and what was pressed since. Say no and you owe nothing.
01 Symptoms · start here
Tap the light or message you can see for the first safe move and the one button not to press. Every answer is checked against Synology's Knowledge Center, and the full explanation sits below the decoder.
Tap the closest match. The full explanations follow just below, in “Synology warnings, explained”.
Lights and sounds
Storage Manager
Synology Assistant, or your files
Your answer appears here.
Then tap that word in the Storage Manager row above.
Questions, answered first
Often, yes. Crashed means more drives dropped out than SHR or RAID can survive, or the file system broke, and Synology says the owner can no longer repair the pool. The files are normally still on the drives.
If files still open in File Station, Synology says not to power off and to copy the data off first. If they will not open, photograph the screen, shut down from DSM or with a short press until it beeps, and number every drive and cache SSD by bay.
Do not click Repair or Remove, reset, reinstall or move the drives into another unit. Remove erases every drive in the pool.
Not until the drives are safe. A Degraded pool has lost no data yet, but Repair reads every remaining drive across its used space, all of it once the pool is over 80% full, and that long read is when a second weak drive gives out.
Hidden bad sectors cluster and may not have been read since they were written. SHR and RAID 5 are Linux RAID, which drops a drive that stops answering for too long, so on a Degraded pool the second loss means Crashed. DSM also slows a repair on purpose, so the pool can sit unprotected for hours or days.
Do not start Repair if another drive shows Warning, Critical or Failing, or the files are not in a backup you have restored from. Image every drive first.
They can. A drive-managed SMR drive needs idle time to tidy its overlapping tracks; under the long writes of a Repair it can stall until Linux RAID drops it, with nothing physically broken.
In 2020 Western Digital confirmed its 2 to 6 TB WD Red drives used SMR and renamed its CMR range WD Red Plus, and iXsystems found the 4 TB WD40EFAX could fault during rebuilds. Synology tells owners not to mix CMR and SMR drives in one array.
Do not re-add a dropped SMR drive and press Repair. Check the model number of any replacement first.
Synology's LED chart calls a blinking power light “powering on”: the hardware is still starting, before DSM loads or the drives are joined. Stuck there, it is a hardware or start-up fault, not a problem with your files.
Synology says blinking for more than 20 minutes points to the motherboard or power supply; a USB device, add-in card, M.2 SSD or a weak adapter can also stop start-up. For the DS415+, DS1515+, DS1815+, DS2415+, RS815(RP)+ and RS2416(RP)+, Synology acknowledged a clock-signal component fault in 2017 and said it was not known to cause data loss.
Do not start it with only some of the original drives. Synology lists drives missing from a pool as a cause of crashes.
Synology's test needs no drives. Power off, take out the drives (numbered by bay) and any USB device, memory, M.2 SSD or add-in card, unplug the power for a few seconds and switch on.
Adapter light blinking or dark: the adapter is the likely fault. Adapter steady but the NAS still blinking after 20 minutes: the board or power supply. A steady light and a beep within about three minutes means the board works, and a unit that fails only with several drives fitted points to an adapter short of current.
Do not move the drives straight into a replacement if there is no backup. HDD migration writes to them, so image first.
Every restart passes power, the bootloader on the unit's flash, then the system partition on every drive, so a weak adapter, a failing board or a damaged system partition often shows on the first restart after a power cut or an update.
A sudden cut can also leave file system errors, which Synology lists as a cause of crashed volumes, and Linux RAID normally refuses to start a RAID 5 or 6 set that was degraded and shut down uncleanly. DSM updates cannot be rolled back.
Do not retry the update, reset or reinstall. Check what Synology Assistant says first.
Yes. A read-write cache takes new writes on the SSDs first and passes them to the hard drives later, and Btrfs metadata can be pinned to it, so Synology lists a crashed or badly removed cache as a cause of crashed volumes.
One SSD failing in a RAID 1 cache makes DSM write the cache back and stop caching. More failures than the cache's RAID survives, and Synology says data held only on the cache is lost. Same-age SSDs wearing out together, an SSD pulled early, or a forced migration can each crash the volume with good hard drives.
Do not pull, replace or repair the cache SSDs on a failed unit. They may hold writes the hard drives never got.
It can. Synology says drives that suddenly show Not installed are not being recognised, and warns: “Do not continue installing DSM, or all data on the drives will be deleted.”
Configuration lost, Migratable and Recoverable are different: Synology says a reinstall for those leaves the data in the volume alone. Even then, image the drives first if there is no backup, because a reinstall writes to every drive.
Do not click Install on Not installed, or accept a prompt to format. Close the installer and power down.
Not from that message alone. The system partition is a small copy of DSM that Synology mirrors across every drive, kept apart from the volume your files live in; one drive's copy has failed.
Treat it as a warning about that drive: check its health and the pool's status, and make sure what you cannot lose is backed up first.
Do not reinstall DSM or reset to clear it, or pull the drive while the pool is Degraded.
Before you press anything on the Synology
02 Costs
It depends on the unit in front of us, so there is no flat fee. Each drive and cache SSD is assessed free, you get one fixed quote in writing, and walking away at that point costs you nothing.
If nothing can be recovered, you pay $0 and your drives come back to you free. The exception is highly complex or forensic cases, whose fees are set out in writing before any work starts.
What moves the price on a Synology
A two-bay DS224+ or a twelve-bay rack unit: every drive is imaged in full, and one with a physical fault goes to the hard drive bench first.
SHR across mixed drive sizes is several Linux RAID sets joined as one pool, and each set is rebuilt before the volume opens.
An encrypted volume needs its recovery key, plus the Key Vault password if the vault was kept on the unit.
The SSDs are imaged too, and their pending writes are merged back into the pool.
Repair onto a weak drive, Remove, a reinstall or a move into a new unit all change the rebuild.
Before you pay anyone
Only when the files exist nowhere else. A Synology often keeps free copies of its own, so look there first.
Btrfs snapshots, each shared folder's recycle bin and a Hyper Backup task may already hold what you need. Restore into a new folder, never over the damaged one.
Client files, accounts, CCTV footage or family photos that only ever lived on the Synology.
A backup you have test-restored already holds everything. The free assessment tells you either way.
03 Process
Each layer DSM built is put back in the same order, and only ever on images.
Each drive and M.2 SSD photographed and recorded by serial, bay and slot.
A drive that will not read cleanly goes to the hard drive or SSD bench before imaging.
Every sector of every drive, through write blockers, onto lab storage.
The Linux RAID sets are read from the images and joined as DSM joined them, extra mixed-size sets included.
Btrfs or ext4 read in software, snapshots checked, encrypted volumes unlocked with your key, cache writes merged.
You check the recovered files before paying, then they go onto a new drive.
04 Laboratory
One Brisbane laboratory, our own engineers, and no drives sent overseas or to another company.

Executive Data Engineer / Owner
Runs each Synology job, from the first call to the file list you approve.

Electrical Engineer
Takes the drives that will not spin up or read, and their board and power faults.

Co-founder · mobile & encryption
Unlocks encrypted Synology volumes and folders with the owner's own keys.
Need confidentiality? We sign an NDA on request, and on every forensic case as standard. Where the drives may be evidence, forensic handling applies from the first call, and companies can be invoiced.
A lab that runs DSM's Repair, or rebuilds on your own drives, takes the very risk you were trying to avoid.
The recovered file list, checked against the folders that matter to you, should come before the invoice.
What our clients say on Google
4.8 from 96 reviews
“Great communication with fast service, managed to retrieve all family photos and videos off a broken hard drive.”
“Excellent Data Recovery and re set up. Viktor goes above and beyond to explain everything regardless of how long it takes. After disasters through the years gone by with other so-called experts, it was stessfree and a relief to discover Wildfire. Excellent pricing and communication. ☆☆☆☆☆ Highly recommend 👌”
“Wildfire Data Recovery were fantastic to deal with from start to finish. Extremely responsive to any customer requests and we able to perform data recovery and phone repair where Samsung official repairer advised they would not likely be able to preserve the data. Very satisfied with Viktor and his team. Highly recommend 👌”
05 Start
Tell us the model, the drive count and the exact word on the screen. Anything you added from the decoder is already filled in below.
Prefer to speak to us?
1300 806 55706 Delivery
Post the drives from anywhere in Australia on our free tracked label, or in Brisbane book a courier pickup within the hour for $85 (up to $120 further from the city). With four or more drives, call before you pack.
DSM's Shut Down, or a three-second press until it beeps. Save the ten-second hold for a unit that will not respond.
Each drive gets its bay number, each M.2 SSD its slot, before it comes out.
M.2 or SATA cache SSDs go with the hard drives, removed only with the unit fully off.
An anti-static bag each, padding between them, and a firm box.
Keep the unit and adapter unless we ask for them.
Have recovery keys and the Key Vault password ready; never pack them or type them into the form.
Call 1300 806 557 before cutting power.
Leave it on and call.
Close it. Do not install.
Please do not: Windows may offer to initialise them.
07 Answers
What Synology owners ask us most, answered from Synology's own documents and drive-failure research.
Data and lifespan: same-batch failures and ageing disks
There is no safe age. In Backblaze's 2025 analysis of about 317,000 drives running around the clock, failure rates stayed fairly flat for most of a drive's life and peaked at 4.25% a year at about ten years; its 2021 analysis peaked at 14.24% at about seven years and nine months.
A small office NAS is not a data centre, so your drives' model, age and warnings matter more than fleet averages. The real double-failure risks are a set of same-age drives, one already on Warning, and a pool left Degraded. Synology recommends data scrubbing twice a year; we add planned replacement and a backup you have test-restored.
Same model, same age, same hours and heat: their failures are not independent. A study of drive replacements in large fleets found significant correlation between them, and Backblaze says drives bought in bulk can fail in a cluster when a model has a problem.
A rebuild then reads every used sector of every survivor, often the first full read in years without regular scrubbing, which is when hidden bad sectors surface. The second failure is usually a drive that was already weak, so image first and rebuild only from the images.
Playbook and emergency triage: what not to do
No. HDD migration carries the pool across unchanged, so a Crashed pool arrives crashed, and Synology still says a crashed volume cannot be repaired.
The move also writes DSM onto every drive and keeps the newer DSM version. It fails outright if the new model lacks Btrfs (Synology says the volumes then cannot be mounted), if a 2025 model refuses the drives, or if a read-write cache needed removing first. For a crashed SHR volume, image the drives before they go into anything.
For deleted files on a healthy Synology, try snapshots, the recycle bin and Hyper Backup, restoring into a new folder. For a crashed or degraded pool, no: software needs every drive attached and SHR reassembled before it can see a file, and Synology's spare-drive method writes the system partition to your original drives.
Usually just the drives and any cache SSDs, each numbered by bay or slot. Keep the unit and adapter until we have spoken.
Yes, with the keys. Each encrypted volume needs its recovery key, and the Key Vault password if the vault was set to Local. Skipping the vault password after a migration erases the vault, leaving each volume locked until its recovery key is entered.
Most jobs take 12 to 15 business days. Complex ones take longer, because slower methods are needed to reach the data, and your written quote gives the estimate for your unit.
$0, under our No Data, No Fee policy: you get a plain account of what we found, and your drives come back free by tracked post or for collection. The exception is highly complex or forensic cases, whose fees are set out in writing before any work starts. Read our No Data, No Fee policy.
08 Learn
Ransomware, critical advisories and company changes that matter when a Synology fails, newest first, from Synology's own advisories and press releases.
Security watch · last checked 15 November 2026
Synology rates CVE-2026-76954 at 9.8: a flaw in DSM's Auth API that lets an attacker with no login read or write files. It also fixes an rsync login bypass, with no workaround listed. Run at least these builds, released 12 October 2026:
| DSM branch | Minimum build |
|---|---|
| DSM 7.4 | 7.4.1-90080 Update 1 |
| DSM 7.3 | 7.3.2-86009 Update 5 |
| DSM 7.2.2 | 7.2.2-72806 Update 10 |
| DSM 7.2.1 | 7.2.1-69057 Update 13 |
| DSM 7.2, 7.1, 6.2 | No fix listed |
Four flaws in the Plex Media Server package, fixed in version 1.43.5.11079. Packages update separately from DSM.
Synology warned of ransomware on outdated and end-of-life DSM, tied to a flaw it fixed in December 2024 (SA-24:20). Press reports name it C3RB3R: files renamed .L0CK3D, a note called read-me3.txt. Synology has not named the flaw used, and one security firm blames the September 2026 flaws instead. Hong Kong's computer emergency team says disconnect, keep the note and logs, and do not reset or format; updates do not decrypt.
Two PHP flaws scored 9.8 open PHP packages such as Web Station and WordPress to remote code. Synology patched them even on end-of-life DSM 7.2, 7.1, 7.0 and 6.2 (PHP 7.3 excepted), and says DSM's built-in PHP is not exposed; CISA lists both flaws as exploited since 26 October.
SA-26:13 (18 September) fixed two no-login flaws scored 9.8; its builds are superseded by SA-26:19. Two Telnet flaws were fixed in January and March, one of them on CISA's exploited list: turn Telnet off in Control Panel, Terminal.
At Pwn2Own Ireland, researchers broke into a DS925+ twice and a BeeStation Plus. Fixes: SA-25:12 for BeeStation (Critical, BeeStation OS 1.3.2-65648) and SA-25:14 for DSM.
StealthWorker (2021) guessed weak admin passwords; a Synology variant of eCh0raix (2020 to 2021) encrypted data folders; 2019 brought a password-guessing wave; and SynoLocker (2014) encrypted files on old DSM 4 builds that Synology said it could not decrypt.
CISA's exploited list (9 November 2026 edition) has nothing under Synology's name, but the PHP and Telnet flaws Synology patched are on it under other vendors. In Australia, report ransomware to the Australian Cyber Security Centre on 1300 CYBER1.
Synology, 2024 to 2026
DSM 7.4 (June 2026) runs to about June 2028 and is the last version for most 16 to 19 series units. DSM 7.3 (October 2025) is the long-term branch, to about October 2028. 7.2.1 and 7.2.2 still get fixes; plain 7.2 has had none since February 2025, 7.1 ended about June 2025 and 6.2 on 1 October 2024. Updates cannot be rolled back.
DSM 7.3 lets 2025 DiskStation Plus, Value and J models use other makers' hard drives again, but M.2 pools and caches still need listed drives, and 2025 rack and FlashStation units accept unlisted hard drives only by migration. Remove the pool on such migrated drives and Synology says that unit will not use them again.
Video Station left in DSM 7.2.2, Photo Station in DSM 7.0, and DSM 7.4 drops Mail Station and Synology Mail Server. A reinstall or newer unit loses their databases.
Synology is trading normally, with DSM updates in October 2026 and advisories in November 2026.
Inside the unit
Five layers, each put back in order before your folders reappear.
Every drive carries pieces of every layer above it, so bay order matters.
DSM mirrored on every drive, with the bootloader on the unit's flash. A reinstall writes to every drive.
Linux RAID. SHR slices drives into chunks so mixed sizes waste less; SHR-1 survives one failure, SHR-2 two, and mixed sizes mean several RAID sets in one pool.
Btrfs adds snapshots and optional checksums; ext4 is common on older and entry models. Snapshots live inside the same volume, so in our view they are no backup if the pool is lost.
With a read-write SSD cache, new writes reach the SSDs before the hard drives, which makes the cache part of the set.
09 Library
The terms DSM uses on a failed unit, and the documents behind this page.
Synology's own Knowledge Center, advisories and press releases first, then government, research and drive makers. Press reports are used only for dates and names.
Free assessment
Free assessment of every drive and cache SSD, one fixed written quote, and your recovered file list before any invoice. If nothing can come back, you hear it straight and pay nothing.
QNAP, WD My Cloud, UGREEN and every other NAS maker.
RAID levels, failed rebuilds and controller arrays.
What to do this week if your DSM is out of date.
Synology, QNAP and others, model by model.
Check your DSM version and settings in two minutes.
Should this array be rebuilt, or left alone?
Print labels for each drive before it leaves the unit.
Encrypted or renamed files on any device.