A Netgear ReadyNAS often holds years of shared office files, scanned documents or family photos, so it is alarming when the admin page says “No volume exists”, a volume shows as inactive, or the box simply sits on “Booting” and never appears in RAIDar. The good news is that in many of these situations the data is still on the disks. The bad news is that several of the options the NAS offers you, and some of the advice on forums, can turn a recoverable fault into a permanent loss. This guide explains what the common ReadyNAS messages mean and what is safe to do next.
How a ReadyNAS stores your data
It helps to know what is underneath. Current ReadyNAS models running ReadyNAS OS 6 build their volumes from standard Linux software RAID (md), with the Btrfs file system on top. Older models running RAIDiator use Linux RAID with ext3 or ext4. X-RAID is Netgear’s automatic mode, which expands the volume as you add or swap in larger disks by layering several RAID groups together; Flex-RAID lets you choose RAID levels yourself.
Two practical consequences follow:
- The disks cannot simply be plugged into a Windows PC and read. Windows does not understand Linux RAID or Btrfs, and will usually offer to initialise the disks, which you must not accept.
- An X-RAID volume that has been expanded several times can be made of more than one RAID layer. If one layer fails, the whole volume goes offline, even if most disks are healthy.
What the common messages mean
“No volume exists” or “Remove inactive volumes to use the disk”
This means ReadyNAS OS can see the disks but cannot assemble or mount the volume on them. Typical causes are a disk that has dropped out of the RAID, two disks failing close together, a power cut during a write or an expansion, or Btrfs metadata damage. The prompt to remove inactive volumes is the dangerous part: removing the volume deletes its configuration and makes the disks available for a new, empty volume. It does not repair anything.
Volume degraded, then dead
A degraded volume is running without its redundancy. If a second disk fails, or a rebuild hits read errors on a weak disk, the volume goes offline. On larger, older disks this is a common way for a ReadyNAS to fail.
Stuck on “Booting” or not found by RAIDar
ReadyNAS OS lives on the disks themselves as well as on internal flash, so a failing disk can stop the unit starting, as can a failed power supply or mainboard. The data may be perfectly intact even though the box will not boot.
The boot menu: OS reinstall versus factory default
ReadyNAS units have a boot menu, reached by holding the reset button while powering on. It includes options such as OS reinstall and Factory default. They are not the same:
- OS reinstall reinstalls the operating system and resets settings such as the admin password and network configuration. It is designed to leave the data volume alone, and is sometimes the right step for a corrupted OS on otherwise healthy disks.
- Factory default wipes the disks and creates a new, empty volume. Never choose it while you still need the data.
Because the two sit next to each other in a menu driven by button presses and LEDs, mistakes happen. If you are not certain which option you are selecting, and certain that the disks are healthy, leave the boot menu alone.
What not to do
- Do not remove, delete or recreate the volume, and do not run a factory default.
- Do not swap disks between bays, or take them all out without labelling their positions first.
- Do not insert a new disk to “rebuild” when more than one disk has problems, or when you are not sure which disk failed.
- Do not connect the disks to a Windows PC and accept the prompt to initialise them.
- Do not keep power cycling a unit that will not boot. If a disk is failing mechanically, each start can damage it further.
- Do not run Btrfs or file system repair commands over SSH unless you have complete copies of every disk first. Some repair options rewrite metadata and cannot be undone.
What you can safely do
- Note the exact messages on the admin page or front display, and take screenshots of the volume and disk pages if you can still reach them.
- Download the logs from the admin page if it still loads. They often show which disk dropped out, and when.
- If the volume is still readable, even if degraded, copy the most important shares off first, before attempting any rebuild.
- If it is not readable, shut the unit down cleanly, label each disk with its bay number, and stop there.
How a lab recovers a failed ReadyNAS
A professional recovery starts with each disk, not the NAS. Each disk is checked and, if needed, repaired in a clean room, then copied sector by sector to a working image. The Linux RAID layers are then reassembled from those images, in the correct order and with the correct parameters, and the Btrfs or ext file system is read from the rebuilt volume. Because the work is done on copies, the original disks are never written to. This is also why it matters that nobody has tried to recreate the volume first: a fresh volume overwrites the RAID information the reconstruction relies on.
If your NAS supports a business, see our server and RAID data recovery page, or our UK data recovery service for an overview of how we work.
Need help with a ReadyNAS?
If your ReadyNAS is showing “No volume exists”, an inactive volume or will not boot, power it down, keep the disks in order and call Data Doctor on 020 7394 2529 for a free initial consultation. We work from our clean room at Unit 1, The Willows, 80 Willow Walk, London SE1 5SY.