TerraMaster, Asustor or UGREEN NAS Volume Missing? Read This First

Volume missing, or a prompt to initialise or reinstall on a TerraMaster, Asustor or UGREEN NAS? What it means and what to do before you lose data.

TerraMaster, Asustor and UGREEN have become popular choices for home offices and small businesses that want a NAS without paying for the bigger names. They work well, but when one goes wrong the web interface can throw up alarming messages: the volume has disappeared, the pool is degraded, or the box offers to “initialise” the disks or “reinstall the system”. What you click next decides whether your files are still easy to recover. This guide explains what those prompts usually mean and what to do before touching anything.

Common symptoms

  • The NAS powers on but the volume or storage pool is missing, shown as crashed, inactive or unmounted.
  • A disk shows as failed, missing or “not initialised”, and the RAID is reported as degraded.
  • The finder utility (TNAS PC, Asustor Control Center or UGREEN’s app) can see the unit but says it needs setting up or the system needs installing.
  • After a firmware update the NAS will not finish booting, or comes back as if it were brand new.
  • You moved the disks into a replacement unit and it offers to initialise them.
  • Shares are visible but folders are empty, files will not open, or copying stops part-way.

Why these NAS boxes behave this way

Like most consumer NAS systems, these units run Linux. Your disks are normally combined using Linux software RAID, and the volume on top is usually ext4 or Btrfs. On many TerraMaster and Asustor models the operating system itself is also installed in a small partition on each data disk, while some other designs keep the system on internal flash. That matters for two reasons:

  • If the system partition is damaged, or the disks are moved to a different unit, the NAS can look “empty” even though the data partition is untouched.
  • A system reinstall or initialisation wizard is written for new disks. On disks that already hold data, it may repartition or format them, and that is the step that turns a straightforward recovery into a difficult one.

So a message that the NAS needs initialising does not mean your data is gone. Very often it is simply sitting on the disks, waiting to be read properly.

What to do first

  1. Stop writing to it. If the volume is still visible in a degraded state, copy only the most important files off, if they copy cleanly. If copies fail or the unit slows to a crawl, stop.
  2. Do not accept initialise, format or reinstall prompts on disks that hold your only copy of the data.
  3. Do not start a rebuild with a doubtful disk. A rebuild reads every sector on the remaining disks. If a second disk is weak, the rebuild can fail part-way and leave the array in a worse state than before.
  4. Write down what happened: the model, how many disks, the RAID type if you know it, any messages, and what has already been tried (updates, disk swaps, restarts).
  5. Label the disks with their bay numbers before removing them. The order can matter when the RAID is rebuilt in a lab.
  6. Shut the NAS down cleanly if it will let you, rather than leaving it repeatedly trying to repair itself.

Things that often make it worse

  • Pulling disks in and out to “see what happens”, or putting them back in a different order.
  • Running file system repair tools on a volume that sits on a failing disk.
  • Connecting the disks to a Windows PC. Windows cannot read Linux RAID or ext4/Btrfs and will offer to initialise or format them, which is exactly what you want to avoid.
  • Repeatedly re-applying firmware updates to a unit that already failed during one.
  • Replacing a failed disk and rebuilding when there is no backup and another disk is showing SMART warnings or bad sectors.

One failed disk or something bigger?

If the NAS reports a single failed disk in a RAID 1, RAID 5, RAID 6 or similar layout, the volume is degraded but still readable, and your backup is current, replacing the disk and letting it rebuild is the normal procedure. If there is no backup, the safer order is to get the data off first and rebuild afterwards.

If the volume has vanished entirely, if two or more disks are reported as failed, if any disk is clicking, or if the unit failed during an update or a disk swap, treat it as a recovery job rather than a maintenance job. In a lab, each disk is checked and imaged individually, any physically failing disk is dealt with first, and the RAID and file system are reassembled from the copies. Your original disks are not written to.

Preventing a repeat

  • A NAS is not a backup on its own. Keep a second copy elsewhere, ideally with versioning, so ransomware or an accidental deletion cannot take everything.
  • Turn on email alerts so you hear about a degraded pool or SMART warning straight away.
  • Back up before firmware updates, and do not update while the pool is degraded.
  • Replace disks that start showing reallocated or pending sectors, rather than waiting for them to fail.

Need help with a TerraMaster, Asustor or UGREEN NAS?

We recover data from NAS units of all brands, working from images of each disk in our London lab, which includes a clean room for disks with physical faults. See our server and RAID data recovery and UK data recovery service pages, or the full list of our services.

For a free initial consultation, call Data Doctor on 020 7394 2529 or bring the disks to Unit 1, The Willows, 80 Willow Walk, London SE1 5SY. Please label the disks with their bay numbers and do not initialise them first.

Need this recovered? Stop using the device and call 020 7394 2529 — the first consultation is free.