NAS Symptom Recovery
Synology NAS Blinking or Flashing Blue Light Data Recovery
Your Synology NAS shows a power light that blinks or flashes blue and never turns solid, and DSM never loads. That points to a chassis-level hardware failure: a dead motherboard, a failing power supply, or a corrupted boot ROM or DOM that halts the unit before it mounts the storage pool. The SATA drives and their mdadm/SHR array sit intact behind that dead chassis.
Some owners describe it as the power button flashing blue or the power light blinking blue and never going solid. The unit begins POST when you press power, never finishes initializing, and the light keeps flashing instead of turning steady. This is the "Blue Light of Death" (BLOD), and it usually means the NAS chassis has failed, not your data.
The drives inside are standard SATA devices running Linux mdadm software RAID. We remove them, image each one through a write-blocker, reconstruct the SHR/mdadm array offline, and extract your files from the Btrfs or EXT4 filesystem. No data, no fee.
A Synology power button flashing blue, or a power light blinking blue and never going solid, means the unit starts POST but fails before the storage pool mounts. The usual cause is a failed mainboard, power supply, or boot ROM, and in that case the member SATA drives and the data on their mdadm/SHR arrays are intact and independent of the chassis. A member drive that hangs SATA enumeration during POST stalls the boot the same way, so we image and read every drive rather than assume the drives are healthy. Do not reset the unit or let DSM initialize the drives, and keep the physical bay order. Work is mail-in at the Austin, TX lab with no diagnostic fees and no data, no fee. We handle offline Synology array reconstruction once the drives reach stable hardware.
My Synology power button is flashing blue. Can you recover the data?
Yes. A power light blinking blue and never going solid is a chassis-level fault, not a wiped disk. Your files live on standard Linux mdadm, LVM, & SHR members that are independent of the failed mainboard, so we pull every drive, clone each one member-by-member through a hardware write-blocker, & reassemble the SHR (mdadm + LVM + Btrfs/ext4) array offline at the Austin, TX lab.
SHR is not a proprietary black box. It is standard Linux software RAID (the mdadm tool) stacked with LVM (the Linux Logical Volume Manager that lets a Synology combine mismatched drive sizes) and a Btrfs or ext4 filesystem on top. Any lab that tells you SHR can only be read by their in-house tool is selling you a story. We assemble it read-only on a standard Linux workstation with mdadm --assemble --readonly, activate the volume group with vgchange -ay, and read your data directly off the reconstructed volume.
What Is the Synology Blue Light of Death?
The Synology Blue Light of Death is a hardware failure state where the power LED blinks or flashes blue continuously and the NAS never completes its boot sequence. Under normal operation the power LED flashes briefly during POST, then goes solid once DSM loads. When the light never goes solid and DSM never loads, the motherboard, power supply, or boot ROM has failed before the operating system could start.
During BLOD the DSM web interface is unreachable on the network, because the operating system never finishes loading.
The critical point: your data drives are intact. The NAS chassis failed; the SATA drives inside it did not.
User data is stored in Linux mdadm software RAID arrays on those drives, independent of the NAS motherboard.
How to Read Your Synology's LED Indicators
Different LED states point to different failure types. Knowing which LEDs are active helps determine whether the chassis, a drive, or both have failed.
| LED Pattern | Meaning | Data Risk |
|---|---|---|
| Power LED blinking or flashing blue, never goes solid | BLOD: motherboard, PSU, or boot ROM failure. NAS does not reach DSM. | Low. Drives intact. |
| Power LED solid, status LED blinking orange | Volume degraded or crashed, volume not created, or DSM not installed. | Medium. Depends on failure scope. |
| Drive bay LED solid orange | Drive error, or the port for that bay is disabled. | Depends on the drive in that bay. |
What if the Synology is stuck in a boot loop?
A Synology that restarts, flashes blue, and never loads DSM is usually failing before the storage pool finishes mounting. Stop repeated reboot attempts, keep every disk in order, document the model number, and move the case into NAS data recovery once the loop repeats for 20 minutes.
What if DSM says Volume Crashed or Degraded?
A "Volume Crashed" or "Degraded" alert means DSM reached the array layer but one or more mdadm members or the Btrfs volume is unstable. If a member also drops sectors, the job shifts to hard drive data recovery with PC-3000 imaging before any rebuild attempt. A confirmed crash moves the case into dedicated Synology Volume Crashed recovery. If the failed unit had DSM 7.2 volume encryption turned on, the array cannot be read without the LUKS key material: your volume passphrase, your exported recovery key, or an intact Encryption Key Vault recovered from the original system partition. That constraint is covered in Synology encrypted volume recovery.
What should you do next?
Power the unit down, record the bay order, and stop every repair prompt before Synology writes new mdadm or Btrfs metadata. After that, route the case into NAS data recovery or RAID data recovery so the first imaging pass happens on stable hardware.
- Shut the NAS down. If the chassis is looping, beeping, or hanging at the blue LED, stop power-cycling it and treat the next action as a NAS recovery intake rather than another home repair attempt.
- Capture drive order and LED state. Photograph each bay, label every disk, and note whether DSM showed degraded volume warnings so the offline RAID reconstruction starts with the correct member order.
- Escalate directly with the failure details. Send the model number, DSM version, prior rebuild attempts, and any clicking-drive notes with your Synology NAS recovery request so the first engineer review starts with the right failure history.
What Causes the Synology Blue Light of Death?
| Cause | Failure Mechanism | Observable Signature and Affected Models |
|---|---|---|
| Intel Atom C2000 Erratum AVR54 | The most documented cause of Synology BLOD. Intel's Atom C2000 series processors (C2358, C2538, C2558, C2758) have a hardware defect where the LPC clock output signal degrades over time until the clock stops functioning entirely, preventing the processor from completing POST. | Confirmed affected: DS415+, DS1515+, DS1815+, DS2415+, RS815(RP)+, RS2416(RP)+ |
| Power Supply Failure | A faulty or degraded PSU that cannot deliver stable voltage under load. | The unit never reaches DSM, so the member drives and their mdadm arrays are untouched. |
| DOM or Boot ROM Corruption | The internal DOM (Disk on Module) or SPI flash chip holds the boot stage. It does not hold the full DSM operating system: DSM is a Linux distribution installed onto the member drives themselves, which is why a fresh set of disks has to have DSM installed before a pool can exist. If a firmware update is interrupted by a power loss, the boot image on the flash can corrupt, so the unit never completes POST and the power LED keeps blinking. | The user data partitions on the member drives are untouched, so the array is recovered by imaging the drives and assembling it on a workstation. |
| General Motherboard Failure | Component failure on the NAS logic board unrelated to the C2000 defect: failed RAM (prevents POST), degraded voltage regulators, or failed capacitors. | Also covers scenarios where a failing drive causes the NAS to hang during RAID array assembly, which externally appears as a blinking blue LED but is actually a drive-level timeout. |
Can an NVMe cache dropout crash the storage pool?
On models that take M.2 NVMe drives as a read/write cache, such as the DS920+, DS1520+, and DS1621+, the cache SSD can drop off the PCIe bus under sustained write load when its consumer controller firmware panics. The uncommitted writes sitting in that cache are lost, so the underlying hard drive array is left holding an incomplete Btrfs filesystem. DSM reports this as a Volume Crashed error, with the status LED blinking orange. That is a different symptom from a blinking blue power light, and it points at a different failure.
This is a logical storage failure, not a dead chassis. The mainboard, power supply, & boot ROM are healthy; the operating system simply cannot mount the storage pool because the Btrfs metadata tree points at write-cache blocks that never landed on the hard drives.
Btrfs uses Copy-on-Write, meaning it never overwrites a block in place. It writes the new version elsewhere and then updates a pointer. When the cache drops mid-update, the parent tree references a child generation that does not exist, & the mount aborts with a parent-transid-verify-failed error.
The four physical causes in the section above (the Intel Atom C2000 erratum, power supply failure, DOM corruption, and general mainboard failure) leave the array healthy; an NVMe cache dropout leaves the chassis healthy and the array damaged.
- 1. Sustained write load
- A large copy, backup job, or rebuild pushes continuous writes through the M.2 NVMe read/write cache.
- 2. NVMe controller panic
- The consumer SSD controller firmware faults and stops responding to the host.
- 3. PCIe bus dropout
- The cache device disappears from the bus, taking every uncommitted (dirty) write with it.
- 4. Btrfs desync
- The on-disk Btrfs tree now references generations that were stranded in the lost cache, so the filesystem fails verification.
- 5. Volume Crashed
- DSM flags the pool as crashed and stops serving it, while the member drives themselves keep reading normally.
The recovery path here is strictly read-only. We image every hard drive member first, then walk the older Btrfs tree roots with btrfs-find-root and pull files out of the damaged filesystem with btrfs restore, which extracts data without writing a single byte back to the source clones.
We never run btrfs check --repair on the original drives, because its repair pass writes to the disk and overwrites the historical Copy-on-Write generation trees that are the most likely route back to a clean copy of your files. Any mount or repair attempt happens on the clones, never the originals.
Power the unit down and leave it as it is. Every mount attempt, part swap, and reboot happens after the member drives are imaged, not before.
Should You Move Drives to a New Synology Without Checking DSM Version?
Moving drives from a failed NAS into a replacement chassis is a supported Synology migration path, but only in one direction: the replacement has to run the same DSM version as the unit that built the array, or newer.
- DSM version decides whether it is allowed. Migrating into a replacement running an older DSM version than the one that created the array is not a supported path. Do not work around it by letting the new unit set the disks up from scratch.
- Bay order must match exactly. SHR records which physical drive occupies which role in the array. Inserting drives in the wrong bay order can cause DSM to misidentify members or trigger an unwanted reinitialization.
- Model compatibility is not universal. Not all Synology models support migration from every other model. Synology publishes a compatibility matrix. SHR volumes created on newer DSM versions may show as "Not supported" on an older or incompatible unit.
- If you see "All data will be deleted": stop. Power down immediately. Do not proceed past this screen under any circumstances. The drives are still recoverable at this point. After accepting the prompt, they may not be.
How do Synology drives assemble on a Linux workstation?
Each member drive carries a data partition, and those partitions assemble into a Linux md array. What sits on top of that array depends on how the pool was built: an SHR pool with a single volume puts an LVM layer between the array and the filesystem, while a classic RAID pool with a single volume has no LVM layer at all. Knowing which one you have decides what you mount.
| Pool layout | LVM layer | What you mount | Filesystem |
|---|---|---|---|
| Classic RAID, single volume | None | the assembled md device | EXT4 or Btrfs |
| SHR, single volume | Volume group vg1000, logical volume lv | /dev/vg1000/lv | EXT4 or Btrfs |
On an SHR pool, DSM puts the data volume inside an LVM volume group named vg1000 with a logical volume named lv. For SHR pools built from mixed-size drives, DSM creates additional md devices to use the leftover capacity on the larger disks, and those size bands are combined into the same volume group. Run lvs first: on a classic RAID pool with one volume it returns nothing, which tells you to mount the md device itself.
Recovery outside the NAS on a Linux PC requires assembling the md arrays read-only with mdadm, activating the LVM volume group where there is one, and mounting the EXT4 or Btrfs filesystem. Mistakes during this process (assembling in write mode, running fsck prematurely) can corrupt the array metadata. Reading the member order & data offset out of each member superblock before any assembly attempt is covered in mdadm superblock & read-only array assembly.
None of that stack is Synology silicon. mdadm, LVM, & Btrfs are stock Linux components, so an unencrypted SHR pool assembles read-only on a plain Linux workstation with no Synology chassis in the loop; the size-band md devices behind a mixed-drive pool are covered in SHR array reconstruction across mdadm, LVM, & Btrfs. If the unit does reach DSM & the failure surfaces as a crashed or degraded storage pool, start from Synology DSM volume & storage pool recovery instead.
How We Recover Data from a Synology BLOD Failure
We follow an image-first, offline reconstruction workflow. Your original drives are never modified. All assembly and filesystem work happens on cloned images.
- Free evaluation and triage. Document the Synology model number (we check against the Intel C2000 affected model list), SHR vs standard RAID configuration, filesystem type (Btrfs or EXT4), number of member drives, and any prior recovery attempts. If drives were inserted into a replacement NAS, we need to know whether DSM prompted for initialization.
- Write-blocked forensic imaging. Each member drive is connected through a hardware write-blocker and imaged with PC-3000 or DeepSpar. Drives with weak heads or bad sectors get conservative retry profiles and head maps to maximize data capture without accelerating degradation. Drives that click or refuse to spin receive clean-bench head swaps with matched donor parts before imaging.
- mdadm superblock capture and RAID reconstruction. We read mdadm superblocks from the imaged copies of each member. These contain the stripe size, parity rotation, member order, and data offsets. For SHR with mixed-size drives, we also reconstruct the LVM layer (volume group boundaries, logical volume extents). Data Extractor Express RAID Edition performs virtual assembly from images, never from originals.
- Filesystem extraction. Once the virtual array is assembled, we mount the Btrfs or EXT4 filesystem from the reconstructed volume. For Btrfs, we traverse subvolume trees and recover snapshots where applicable. For EXT4, journal replay and inode table reconstruction recover the directory structure. Files are extracted, verified against your priority list, and copied to target media.
Synology Models Commonly Affected by BLOD
The Intel C2000 erratum affects a specific generation of Synology DiskStation and RackStation models manufactured between 2014 and 2017. Other models can also exhibit BLOD from unrelated causes (PSU failure, DOM corruption).
| Model | Processor | BLOD Cause |
|---|---|---|
| DS415+ | Intel Atom C2538 | C2000 AVR54 erratum |
| DS1515+ | Intel Atom C2538 | C2000 AVR54 erratum |
| DS1815+ | Intel Atom C2538 | C2000 AVR54 erratum |
| DS2415+ | Intel Atom C2538 | C2000 AVR54 erratum |
| RS815(RP)+ | Intel Atom C2538 | C2000 AVR54 erratum |
| RS2416(RP)+ | Intel Atom C2538 | C2000 AVR54 erratum |
Two of the C2000 units in that table are rack-mount RackStation hardware rather than desktop DiskStation boxes: the RS815(RP)+ & the RS2416(RP)+. Rack deployments running SHR-2 pools, NVMe cache tiers, or all-flash FlashStation units are handled in enterprise Synology recovery for RackStation & FlashStation deployments.
How Much Does Synology BLOD Recovery Cost?
Synology BLOD recovery follows the published hard drive recovery tiers because each member drive is billed by failure type, not by the NAS badge on the front. File-system work starts at From $250, firmware repair runs $600–$900, and head swaps run $1,200–$1,500; multi-drive reconstruction is quoted after the RAID layout, mdadm metadata, and filesystem damage are confirmed from imaging. Most BLOD cases stay near the lower end because the chassis fails before the member drives do. How a multi-drive quote splits into a per-member imaging fee plus a single array reconstruction fee is laid out in NAS recovery cost per member drive.
- Low complexity
Simple Copy
Your drive works, you just need the data moved off it
Functional drive; data transfer to new media
Rush available: +$100
$100
3-5 business days
- Low complexity
File System Recovery
Your drive isn't recognized by your computer, but it's not making unusual sounds
File system corruption. Accessible with professional recovery software but not by the OS
Starting price; final depends on complexity
From $250
2-4 weeks
- Medium complexity
Firmware Repair
Your drive is completely inaccessible. It may be detected but shows the wrong size or won't respond
Firmware corruption: ROM, modules, or translator tables corrupted; requires PC-3000 terminal access
CMR drive: $600. SMR drive: $900.
$600–$900
3-6 weeks
- High complexity
Most Common
Head Swap
Bench diagnosis found the read/write heads have to be replaced. Clicking can also come from firmware, the preamp, or the spindle
Head stack assembly failure. Transplanting heads from a matching donor drive on a clean bench
50% deposit required. CMR: $1,200-$1,500 + donor. SMR: $1,500 + donor.
50% deposit required
$1,200–$1,500
4-8 weeks
- High complexity
Surface / Platter Damage
Your drive was dropped, has visible damage, or a head crash scraped the platters
Platter scoring or contamination. Requires platter cleaning and head swap
50% deposit required. Donor parts are consumed in the repair. Most difficult recovery type.
50% deposit required
$2,000
4-8 weeks
Hardware Repair vs. Software Locks
Our "no data, no fee" policy applies to hardware recovery. We do not bill for unsuccessful physical repairs. If we replace a hard drive read/write head assembly or repair a liquid-damaged logic board to a bootable state, the hardware repair is complete and standard rates apply. If data remains inaccessible due to user-configured software locks, a forgotten passcode, or a remote wipe command, the physical repair is still billable. We cannot bypass user encryption or activation locks.
No data, no fee. Free evaluation and firm quote before any paid work. Full guarantee details. Head swap and surface damage require a 50% deposit because donor parts are consumed in the attempt.
- Rush fee
- +$100 rush fee to move to the front of the queue
- Donor drives
- Donor drives are matching drives used for parts. Typical donor cost: $50–$150 for common drives, $200–$400 for rare or high-capacity models. We source the cheapest compatible donor available.
- Target drive
- The destination drive we copy recovered data onto. You can supply your own or we provide one at cost plus a small markup. For larger capacities (8TB, 10TB, 16TB and above), target drives cost $400+ extra. All prices are plus applicable tax.
The prices above are for standard hard drives, which covers most jobs. Helium-sealed drives (for example WD or HGST Ultrastar He and Seagate Exos X) must be resealed and refilled with helium in-house after the chamber is opened, so they price higher, in the $200–$5,000+ range. See helium drive pricing.
Data Recovery Standards & Verification
Our Austin lab operates on a transparency-first model. We use industry-standard recovery tools, including PC-3000 and DeepSpar, combined with strict environmental controls to maintain drive integrity. This approach allows us to serve clients nationwide with consistent technical standards.
Localized Clean Zone
Open-drive work is performed in a 0.02 micron ULPA-filtered laminar clean bench.
Transparent History
Serving clients nationwide via mail-in service since 2008. Our lead engineer holds PC-3000 and HEX Akademia certifications for hard drive firmware repair and mechanical recovery.
Media Coverage
Our repair work has been covered by The Wall Street Journal and Business Insider, with CBC News reporting on our pricing transparency. Louis Rossmann has testified in Right to Repair hearings in multiple states and founded the Repair Preservation Group.
Aligned Incentives
Our "No Data, No Charge" policy means we assume the risk of the recovery attempt, not the client.
Technical Oversight
Louis Rossmann
Our engineers review all lab protocols to maintain technical accuracy and honest service. Since 2008, his focus has been on clear technical communication and accurate diagnostics rather than sales-driven explanations.
We believe in showing the bench rather than just describing it. Open-drive work runs on a 0.02 micron ULPA-filtered laminar clean bench, and we filmed it.
See the particle counter test at the benchSynology BLOD Recovery FAQ
Is my data gone if my Synology has the Blue Light of Death?
Can I put my Synology drives into a new NAS to recover data?
What causes the Synology Blue Light of Death?
How long does Synology BLOD recovery take?
Can I recover data from Synology drives using a Linux PC?
Can an NVMe cache drive crash a Synology storage pool?
Why is it dangerous to rebuild a Synology array on SMR drives?
How much does Synology BLOD recovery cost?
Pricing follows the published per-drive tiers on our hard drive recovery page: From $250 for file-system work, $600–$900 for firmware repair, and $1,200–$1,500 for head swaps, plus target media, tax, & donor cost when donor parts are needed. Multi-drive Synology jobs also include array reconstruction labor quoted after imaging confirms member order, mdadm metadata state, & filesystem damage. If we recover nothing, there is no charge.
See the published hard drive pricing tiers and the broader NAS recovery workflow for how we scope multi-drive cases.
Since 2008
Established
As Featured In
Related services
Need Recovery for Other Devices?
Nationwide intake instructions
Synology, QNAP, and multi-disk NAS recovery
Volume Crashed, SHR, Btrfs/EXT4
RAID 0, 1, 5, 6, 10 arrays
Mechanical HDD recovery
QNAP LED error diagnosis
Complete service catalog
Is your Synology power button flashing blue?
Power down, label your drives, and ship them to us. Free evaluation. No data, no fee.