NDR / Whatever it is saying now / Beeping, orange or red lights

Synology orange · QNAP red · WD red · Drobo red and yellow · beeps

Beeping, or an orange or red light. Every make has its own colours. The ones that mean stop are the same.

A NAS has a small vocabulary of lights and beeps, and each maker uses it differently: Synology's STATUS LED goes static or blinking orange for a fan, a temperature or a degraded or crashed volume; QNAP's status light goes red or flashes red and green for a fault, a rebuild or an update; WD's single light goes solid red; a Drobo's bay lights go red for a failed drive and flash red and yellow while it relays out; Buffalo counts an E-code in flashes; ReadyNAS writes it on the display. The beep, on any of them, is the same message as the light with the volume up. What every one of them means in practice is a unit that should be read once, photographed, and powered down. A single-drive NAS is £300 + VAT and a set £500 + VAT upwards after the free look, fixed in writing.

Free first lookOne fixed figure in writingNo data, no bill on most jobsReturn postage paid

Rather talk it through? An engineer answers the bench line
0800 6890668

Power it down. Label each drive with its bay number. Do not rebuild, repair, initialise, reinstall or reset. A rebuild reads every sector of every surviving drive, and on a set with a second weak member it finishes what the first failure began. Nothing on the drives gets worse while the unit is off.

The lights, make by make, and which ones mean stop.

Synology. The STATUS light is green when DSM is ready. Static or blinking orange once DSM is up indicates, in Synology's own words, a system error such as fan failure, system overheating, or volume degrade or crashed. The POWER light blinks while the unit boots or shuts down, and Synology notes it may keep blinking if the unit meets a problem while shutting down; recovery labs read a persistent blink as a board or memory fault. The beep accompanies the orange light and is silenced from the dashboard, which is the one thing worth doing before the unit is powered down.

QNAP. The status light is green in normal use, flashes green while booting or rebuilding, goes red for a hardware or drive fault, and flashes red and green during a firmware update, a rebuild, or when the unit cannot decide. A QNAP beeps twice at boot and once on a drive event; a long beep is a fault. A unit mid-update should not be powered off; a unit mid-rebuild on a set with a weak drive should, and the difference is whether Storage & Snapshots shows a rebuild in progress. WD My Cloud has one light: white or blue steady is fine, blinking is booting or updating, and solid red is a boot or drive fault.

Drobo. Each bay has a light: green is fine, yellow means the drive is nearly full and a larger one is wanted, solid red means the drive has failed and should be replaced, and flashing red means a second fault or a unit critically full. Flashing green and yellow across the bays means a relayout in progress, which should not be interrupted unless a drive is clicking. Buffalo flashes its E-code, long flashes for tens and short for units, and ReadyNAS writes the fault on its front display. On every make, the right sequence is the same: read it, photograph it, silence the beep from the dashboard if the dashboard answers, and power the unit down before anything is rebuilt, repaired or reset.

What it says, and what it means.

Describe yours to us →

What you see	The usual reason	Where that leaves you
Synology STATUS orange, DSM up	Fan, heat, or a degraded/crashed volume	Read Storage Manager; power down
Synology POWER blinking for minutes	Boot or shutdown problem; possibly the board	Power down; do not keep trying
QNAP status red	Hardware or drive fault	Read the dashboard; power down
QNAP flashing red/green	Update, rebuild, or fault	If updating, wait; if rebuilding on a weak set, power down
WD solid red	Boot or drive fault	Power down; do not reset
Drobo bay solid red	Failed drive	Do not replace it yet; power down
Drobo flashing red	Second fault or critically full	Power down now
Beeping on any make	The light, with the volume up	Silence from the dashboard; read; power down

From the box arriving to your files going back.

Work we have closed →

Logged the day it lands, and the first look costs nothing Free

A case number goes on the parcel and a number on every drive the day it is opened, and an engineer settles what has actually happened before anything spins. The unit is examined on its own; each drive is assessed on our own equipment, never in a NAS that will try to rebuild. Back to you come two things together: a straight note of what is liftable and what is not, plus one figure, fixed and written down. Accept it, or decline and owe us nothing.

Nothing to pay for lookingA single figure, put in writingNo rebuilds, no repairs, no resets

The unit, and the drives, apart

The box and the disks are two different jobs. The unit is tested separately, because a dead power supply, a failed board or a bricked boot flash leaves the drives untouched more often than not. Each drive is then read on the bench: the ones that answer at full speed, and the weak or failed ones in clean air where they need head work. On units that hold an encryption key or a layout of their own, the unit is part of the data and is kept with it.

Unit and disks assessed separatelyFailing members to the clean bench

Every member imaged, once

Nothing is worked on live and nothing is rebuilt on the originals. Every drive in the set is imaged sector by sector, the weak ones head by head with the bad areas last, and the SSD cache with them where there is one. From then on the originals are not touched again.

Every drive, including the cacheWeak areas last

The set put back together, from the images

Order, chunk size, parity rotation and the reshape point are read from the drives' own metadata and the array is reassembled in software: mdadm and LVM under SHR, X-RAID and QTS pools; a ZFS pool imported read-only; Drobo's BeyondRAID zones reconstructed. The file system, Btrfs, ext4, XFS or ZFS, is repaired on the virtual volume, and encrypted volumes are unlocked there with the key you supply. Never on the originals.

Rebuilt in software, from imagesThe file system repaired on the virtual volume

You see the file list before you pay

What was recovered is listed for you first, and only then does a bill exist. Approve the list and it is invoiced; turn it down and it is not — and where nothing has come back, most jobs carry no charge at all. Recovered data travels home on fresh media bought in for your job, with the postage at our end. Your case is not closed until you have opened the files on a machine of your own.

No charge until you accept the figureFresh media, supplied with the job5–10 days at the bench

From the bench

Photograph the lights before you power down. Which bay, which colour, blinking or static: the photograph tells the bench what the unit was reporting when it was last on.
Silence the beep from the dashboard, not with the reset button. The dashboard's alarm setting stops the noise; the button does other things.
A unit mid-update should finish. Powering off a QNAP or Synology during a firmware write is how a bricked boot happens. A unit mid-rebuild on a set with a weak drive is the opposite case.
The light is the unit's opinion. The bench reads the drives' own metadata, which is usually more accurate about what has failed and when.

One job, followed all the way through.

UK · NDR-2026-0528JOB LOGGED ✓

A DS416 beeping with an orange STATUS light, one bay red, and an owner who photographed it and powered down

The photograph showed bay 3 red and the beep silenced from the dashboard; Storage Manager, in the same screenshot, showed the pool degraded and a second drive with a warning. Both weak drives were imaged slowly on the bench, the other two end to end, the SHR arrays assembled from the images and the volume mounted from the virtual set. The second drive failed on the bench during imaging, which is where it should.

100% of it recovered6 days here, and back by post

Illustrative example — replace with a genuine case

What helps, and what harms.

Do this much first

Read the light and the dashboard, and photograph both
Silence the beep from the dashboard
Power down, unless a firmware update is mid-write
Label the bays and send the set

What sets us back

Pressing the reset button to stop the beep
Replacing the drive the light points at
Power cycling to see whether the light clears
Interrupting a firmware update

Questions answered before you commit.

My Synology is beeping with an orange light. What does it mean?

A fan, a temperature, or a degraded or crashed volume, in Synology's own words. Storage Manager says which. Silence the beep from the dashboard, read what it says, and power down.

My QNAP's light is flashing red and green. Should I turn it off?

If it is writing a firmware update, no: let it finish. If it is rebuilding a set with a weak drive, yes, now. Storage & Snapshots shows which.

The Drobo has a solid red light on one bay. Should I replace that drive?

Not yet. A relayout on a set with a second weak drive is how a Drobo loses everything. Power down and send the set in bay order.

What does it cost?

£300 + VAT for a single drive; a set is £500 + VAT upwards, after the free look, fixed in writing.

How long does it take?

5–10 days at the bench for a set.

Where this usually leads.

Synology storage pool degraded →Buffalo E14, E16, E22 →Dead unit, drives fine →Drobo →

Nothing gets worse while it is powered down.

Looking at it is free. Back comes a list of what opened and what did not, together with a single price to finish, set down in writing while you are still free to say no. Until that list reaches you, leave the unit off and the drives in their bays.

0800 6890668

Price my job Packing and posting

Every kind of NAS

Manufacturers

Whatever it is saying now

What it costs, and what follows