---
title: Reassembling a Linux mdadm RAID Safely: Superblocks, Events, Overlays
url: https://recdata.lu/en/guides/mdadm-reassemble-software-raid/
description: Linux software RAID that will not assemble? How to read mdadm superblocks and event counts, when --force is acceptable, why --create is dangerous, and how to work on overlays.
language: en
---

NAS and RAID

# Reassembling a Linux mdadm RAID without making it worse

Linux software RAID (mdadm) sits under most NAS units and many servers. When an array refuses to start, the right commands can bring it back in minutes, and the wrong one can overwrite the very metadata that describes it. This guide is for administrators who want to understand what they are looking at before typing anything.

Published 16 November 20263 min readBy [Mirush Murataj](https://recdata.lu/en/about-us/#author)

Read before you write: mdadm --examine on every member, and note the result.

In short

- Read before you write: mdadm --examine on every member, and note the result.
- --assemble --force is a calculated risk; --create is a last resort that can destroy data.
- Work on clones or copy-on-write overlays, never on the only copy.

## Rule number one: copy before you experiment

If the data matters, image every member first (with GNU ddrescue on a healthy machine, or in a lab if a disk is failing). If you cannot clone, at least work through **copy-on-write overlays**: device-mapper snapshots that send every write to a separate file, so the original disks are never modified. Every experiment below should happen on clones or overlays.

## Read the superblocks

Each member of an md array carries a superblock describing the array. Start with:

- `cat /proc/mdstat` to see what the kernel has assembled, if anything.
- `mdadm --examine /dev/sdX1` on **every** member partition.

Note for each member:

| Field | Why it matters |
| --- | --- |
| Array UUID | All members of one array share it |
| Raid Level, Raid Devices | Confirms the layout |
| Chunk Size, Layout | Stripe size and parity rotation |
| Device Role | The position of this disk in the array |
| Events | A counter increased on each array change: the most important clue |
| Update Time | When this member was last written |
| Array State | How this member saw the array the last time it was updated |

## Reading the event counter

Members with the same (or nearly the same) event count are in sync. A member far behind dropped out earlier and holds stale data. In a RAID 5 with four disks where one member is thousands of events behind and another is a few events behind, the best assembly usually uses the three most recent members and leaves the stale one out.

## Assembling read-only

Try first: `mdadm --assemble --readonly /dev/md0` followed by the members you have chosen. If mdadm refuses because the event counts differ slightly, `--force` tells it to accept the most recent members and update the lagging superblock. That is a write: do it on overlays, and only when the difference is small and you understand why.

Then mount the file system read-only (for ext4, `mount -o ro`; for XFS add `norecovery` so the log is not replayed) and copy the data off before doing anything else.

## Why --create is dangerous

`mdadm --create` with `--assume-clean` writes **new** superblocks with the parameters you give. If the chunk size, layout, member order, metadata version or data offset differs from the original even slightly, the array assembles into garbage, and the original superblocks are gone. Newer mdadm versions also use a different default data offset than older ones, a classic trap on arrays created years ago. It is a last resort for specialists, on overlays, with the old --examine output in front of you.

## When to stop

- A member makes noise, disappears from the bus or shows rapidly growing reallocated or pending sectors.
- Two members have very different event counts and you are not sure which one is current.
- The file system will not mount read-only.

At that point, every extra attempt reduces what can be recovered. Our [RAID data recovery](https://recdata.lu/en/data-recovery/raid/) service rebuilds the array from clones, in software, without touching your disks. See also [RAID 5 rebuild failed: what happened and what to do now](https://recdata.lu/en/guides/raid-5-rebuild-failed/).

## Frequently asked questions

Is mdadm --assemble --force safe?

It is relatively safe when the event counts differ by a few units and the disks are healthy, but it writes to the superblocks. Use overlays or clones whenever the data matters.

What does a big difference in the Events field mean?

That member left the array long before the others. Its data is out of date and should normally be left out of the assembly.

## Official sources and useful links

- [Linux RAID wiki (kernel.org)](https://raid.wiki.kernel.org/): Reference documentation for Linux software RAID (mdadm).

Share this guide

- [LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Frecdata.lu%2Fen%2Fguides%2Fmdadm-reassemble-software-raid%2F)
- [Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Frecdata.lu%2Fen%2Fguides%2Fmdadm-reassemble-software-raid%2F)
- [WhatsApp](https://wa.me/?text=https%3A%2F%2Frecdata.lu%2Fen%2Fguides%2Fmdadm-reassemble-software-raid%2F)
- [Email](mailto:?body=https%3A%2F%2Frecdata.lu%2Fen%2Fguides%2Fmdadm-reassemble-software-raid%2F)
-

Cite this article

Murataj, Mirush. "Reassembling a Linux mdadm RAID without making it worse". RecData, 16 November 2026. https://recdata.lu/en/guides/mdadm-reassemble-software-raid/

Is your data important?

Do not try anything that could make the fault worse. The diagnosis is free and you get a fixed quote before any work starts.

[Request a free diagnosis](https://recdata.lu/en/free-diagnosis/) [RAID data recovery](https://recdata.lu/en/data-recovery/raid/)

Need a diagnosis?

Free, no obligation, reply within 2 hours.

[Free diagnosis](https://recdata.lu/en/free-diagnosis/)[+39 389 965 7366](tel:+393899657366)

## Read next

- [RAID 5 rebuild failed: what happened and what to do nowA RAID 5 is built to survive the loss of one disk. The danger comes afterwards: the rebuild reads every…](https://recdata.lu/en/guides/raid-5-rebuild-failed/)
- [Synology volume crashed or storage pool degradedSynology NAS units are reliable, which is precisely why many offices and homes in Luxembourg use them as…](https://recdata.lu/en/guides/synology-volume-crashed/)
- [Recovering deleted files on WindowsA file deleted on Windows is rarely gone at once. Depending on where it was and how it was deleted, it may be…](https://recdata.lu/en/guides/recover-deleted-files-windows/)
- [Recovering deleted photos and files on AndroidAndroid phones keep more copies than people think: trash folders, Google backups, WhatsApp backups, memory…](https://recdata.lu/en/guides/recover-deleted-files-android/)
- [Recovering deleted photos on iPhoneOn an iPhone, a deleted photo first goes to the Recently Deleted album, where it stays for 30 days. After…](https://recdata.lu/en/guides/recover-deleted-photos-iphone/)
- [Bad sectors: can they be repaired?A warning about bad sectors is one of the most common messages a hard drive gives before it fails. The word…](https://recdata.lu/en/guides/hard-drive-bad-sectors/)

Your device has stopped responding? Switch it off and talk to us.

[Request a free diagnosis](https://recdata.lu/en/free-diagnosis/)
