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. If it keeps blinking for more than 20 minutes, Synology points to the motherboard or the power supply. A faulty drive or an attached device can cause the same symptom.
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).
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. Synology points to the motherboard or power supply. Your data sits on the member drives, in mdadm/SHR arrays that don't depend on the chassis. A faulty drive can cause the same symptom, so we image & read every drive instead of assuming they're 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 that blinks blue and never goes solid means the unit never finished powering on. It doesn't mean your disks were wiped. Your files live on standard Linux mdadm, LVM, & SHR members that don't depend on the chassis. We pull every drive & clone each one member-by-member through a hardware write-blocker. Then we 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. During a normal boot the power LED blinks while the hardware initializes and turns static blue when the Linux kernel loads, before DSM is ready.
Your data is on the drives inside the unit, in Linux mdadm software RAID arrays that don't depend on 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. Synology points to a motherboard or PSU failure, & a faulty drive or attached device can cause it too. The NAS never reaches DSM. | Depends on the cause. |
| 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 | Synology's guide labels this "Drive error / Port 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 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?
If a member drive behind that alert is dropping sectors, it becomes a hard drive data recovery job. We image on the PC-3000 before anyone attempts a rebuild. 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 can't be read without the LUKS key material. That means your exported recovery key or an intact Encryption Key Vault. 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 | Intel erratum AVR54 covers the Atom C2000 product family. Intel says the LPC clock outputs (LPC_CLKOUT0 and/or LPC_CLKOUT1) may stop working, & after that the system can't boot. | Built on the Intel Atom C2538: DS415+, DS1515+, DS1815+, DS2415+, RS815(RP)+, RS2416(RP)+ |
| Power Supply Failure | A defective power adapter that can't supply enough current. | The unit won't boot with multiple drives installed. |
| General Motherboard Failure | With the drives & external devices pulled, the power LED still keeps blinking for more than 20 minutes. | A faulty drive can cause the same symptom. Synology's test for that is booting with a spare drive. |
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. 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. DSM runs, but it can't mount the storage pool because the Btrfs filesystem on the hard drives is incomplete.
Btrfs uses Copy-on-Write: it writes the new version of a block elsewhere and then updates a pointer. A parent node's pointer records the generation of the block it points to. When the cache drops out mid-update, that generation no longer matches the block on disk, & the mount aborts with a parent transid verify failed error.
- 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
- What's left of the Btrfs filesystem on the hard drives is incomplete, so it 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?
Synology supports migrating drives from a failed NAS into a replacement chassis.
- Check the DSM version. After an HDD migration, the replacement ends up on whichever DSM version is newer between the two units, so it has to support that version. Don't work around it by letting the new unit set the disks up from scratch.
- Keep the bay order. Synology recommends putting the drives in the same order they sat in the original unit.
- Model compatibility is not universal. Not all Synology models support migration from every other model. Synology publishes a compatibility matrix.
- If you see "All data on the hard drive(s) 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 with a single volume, 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. Assemble in write mode & you can corrupt the array metadata. Run fsck too early & it writes to the filesystem. 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. All assembly and filesystem work happens on cloned images.
- Free evaluation and triage. 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 with failed heads get 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, 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.
Which Synology models use the Intel Atom C2538?
These Synology DiskStation and RackStation models use the Intel Atom C2538, a C2000-family processor covered by Intel erratum AVR54. Other models can also show BLOD from unrelated causes, such as power supply failure.
| Model | Processor | Intel Erratum |
|---|---|---|
| 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 $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. 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
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'll provide one. For larger capacities (8TB, 10TB, 16TB and above), target drives cost $400+ extra. All prices are plus applicable tax.
Sealed helium drives are on their own price list, $200–$5,000+. When a head swap or platter repair opens one, we refill it with helium. That adds $400–$800, and the donor has to be an exact match. Helium drive prices
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.