How to Create a Software RAID 1 Array on Debian 12 (Bookworm)

In the world of data management, redundancy and reliability are paramount. Whether you’re managing a small server or a home NAS system, protecting your data from drive failure should be a top priority. One effective and relatively simple method for achieving this on a Linux system is using RAID 1—a mirroring setup where two drives maintain identical data. In this guide, we’ll walk you through creating a software RAID 1 array on a Debian 12 (Bookworm) system using mdadm, the standard Linux tool for managing software RAID.

📌 What is RAID 1?

RAID (Redundant Array of Independent Disks) is a data storage virtualization technology that combines multiple physical disks into one logical unit. RAID 1, also known as mirroring, stores identical data on two (or more) drives. If one disk fails, the system can still operate using the mirrored disk, ensuring high availability and data integrity.

Benefits of RAID 1

• Redundancy: One disk can fail without data loss.
• Read performance boost (in some cases).
• Easy recovery from hardware failure.

Limitations

• Halves available storage (e.g., two 1TB drives = 1TB usable).
• Doesn’t protect against file corruption or accidental deletion.

🧰 Prerequisites

Before proceeding, make sure:

• You’re using Debian 12 (Bookworm).
• You have two identical or similarly sized disks available (e.g., /dev/sdb and /dev/sdc).
• You have root or sudo privileges.
• You’re okay with wiping any data currently on the disks involved in the array.

⚠️ Warning: This guide involves formatting disks. Ensure you’re working with the correct devices and have backed up any important data.

🔧 Step 1: Install mdadm

mdadm is the tool we use to create and manage software RAID arrays.

sudo apt update
sudo apt install mdadm

During installation, Debian might prompt you to configure mdadm for boot-time assembly. Accept the default options, or configure it based on your needs.

💽 Step 2: Identify Your Disks

Use lsblk, fdisk, or blkid to list your disks and confirm their device names:

lsblk

Example output:

NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINT
sda      8:0    0   120G  0 disk
├─sda1   8:1    0   512M  0 part /boot
└─sda2   8:2    0 119.5G  0 part /
sdb      8:16   0   500G  0 disk
sdc      8:32   0   500G  0 disk

Here, /dev/sdb and /dev/sdc are the two disks we’ll use for the RAID 1 array.

🧼 Step 3: Wipe Existing Partitions

Make sure the disks have no partitions or existing data structures.

sudo wipefs -a /dev/sdb
sudo wipefs -a /dev/sdc

Then remove any old partitions if necessary:

sudo fdisk /dev/sdb
# Type "d" to delete, "w" to write and exit.
sudo fdisk /dev/sdc

🛠️ Step 4: Create the RAID 1 Array

Now we’re ready to create the RAID 1 array using mdadm.

sudo mdadm --create --verbose /dev/md0 --level=1 --raid-devices=2 /dev/sdb /dev/sdc

Explanation:

• /dev/md0 is the name of the RAID device.
• --level=1 indicates a RAID 1 setup.
• --raid-devices=2 specifies the number of devices.
• /dev/sdb /dev/sdc are the two physical drives.

You may see a warning that the devices have no superblocks or are not partitioned. This is expected if they’re clean disks. Type yes to proceed.

Check progress with:

cat /proc/mdstat

You’ll see output like:

md0 : active raid1 sdc[1] sdb[0]
      488253440 blocks super 1.2 [2/2] [UU]
      [=>...................]  resync =  9.2% (45000000/488253440)

Wait for the resync to complete, or continue with the next steps as it runs in the background.

📝 Step 5: Create Filesystem on the RAID Array

Once the RAID device /dev/md0 is created, format it with your preferred filesystem. Here we’ll use ext4:

sudo mkfs.ext4 /dev/md0

📂 Step 6: Mount the RAID Array

Create a mount point:

sudo mkdir -p /mnt/raid1

Then mount it:

sudo mount /dev/md0 /mnt/raid1

To verify:

df -h /mnt/raid1

🧱 Step 7: Make the RAID Array Persistent

1. Create an mdadm.conf file

sudo mdadm --detail --scan | sudo tee -a /etc/mdadm/mdadm.conf

2. Update initramfs

sudo update-initramfs -u

3. Add to /etc/fstab

Get the UUID of the RAID array:

sudo blkid /dev/md0

Example output:

/dev/md0: UUID="a1b2c3d4-e5f6-7890-abcd-ef1234567890" TYPE="ext4"

Now add it to /etc/fstab:

sudo nano /etc/fstab

Add this line at the end:

UUID=a1b2c3d4-e5f6-7890-abcd-ef1234567890 /mnt/raid1 ext4 defaults,nofail 0 0

Save and exit. Test with:

sudo mount -a

🔍 Step 8: Verify RAID Health

To check the status of the RAID array:

cat /proc/mdstat

Or use:

sudo mdadm --detail /dev/md0

Example output:

/dev/md0:
           Version : 1.2
     Creation Time : Sat Apr  5 14:00:00 2025
        Raid Level : raid1
        Array Size : 488253440 (465.56 GiB 500.11 GB)
     Used Dev Size : 488253440 (465.56 GiB 500.11 GB)
      Raid Devices : 2
     Total Devices : 2
       Persistence : Superblock is persistent

       Update Time : Sat Apr  5 14:05:00 2025
             State : clean 
    Active Devices : 2
   Working Devices : 2
    Failed Devices : 0
     Spare Devices : 0

Consistency is key to long-term data reliability, so it’s a good idea to schedule regular checks.

---

## 🔄 Step 9: Simulating a Disk Failure (Optional)

To simulate a failure:

```bash
sudo mdadm --fail /dev/md0 /dev/sdb

Check:

cat /proc/mdstat

Then remove the failed disk:

sudo mdadm --remove /dev/md0 /dev/sdb

Replace it with a new disk (e.g., /dev/sdd) and add it back:

sudo mdadm --add /dev/md0 /dev/sdd

The array will rebuild itself, and you’ll see the sync progress.

📋 Summary

Creating a software RAID 1 array on Debian 12 Bookworm with mdadm is a powerful way to add redundancy and peace of mind to your data storage strategy. While RAID 1 doesn’t replace a full backup system, it protects against hardware failure and ensures system uptime.

Key Commands Recap

🧠 Final Thoughts

RAID 1 is ideal for anyone needing disk-level redundancy without diving into more complex setups. Debian 12, with its mature Linux kernel and excellent package support, provides a stable foundation for such a configuration. With regular monitoring and a good backup policy, your software RAID 1 setup will serve you well for years.

If you’re looking to go beyond mirroring, consider exploring RAID 5, RAID 10, or ZFS for larger systems. But for simplicity and data safety, RAID 1 remains a solid choice.