Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Yes—but only if Linux can see both microSD cards as separate storage devices. A Raspberry Pi’s built-in microSD slot exposes one card, so a second card needs its own USB reader or a controller that presents each card independently. Linux software RAID can mirror a data volume across the two cards, but microSD RAID is an advanced availability experiment, not a substitute for backups. For a Pi that matters, an SSD or NVMe drive with automated backups is usually a better design.
What RAID 1 on microSD means
RAID 1 is mirroring: Linux sends each write to both members of an array. If one card fails in a way the RAID system can handle, the array may remain accessible from the other. Linux supports RAID 1 through its MD subsystem and device-mapper RAID; the kernel’s MD documentation describes array assembly and management, while its device-mapper RAID documentation identifies raid1 as mirroring.
- Usable capacity: approximately the capacity of the smaller card, not the sum of both. Partition both cards to the same conservative size if their reported usable capacities differ.
- Writes: go to both members, and are constrained by the slower card and shared connection.
- Reads: may be served by either member, but faster reads are not guaranteed; gains depend on implementation, workload, readers, and cards.
- Benefit: potential continuity after some single-card failures—not general protection from data loss.
Two cards in an adapter do not automatically make a RAID array. Linux must enumerate each as an independent block device. A dual-slot reader that combines them into one device will not provide the two members a conventional software RAID 1 array needs.
Can a Raspberry Pi mirror its built-in card?
Not by using the built-in slot alone: it presents one card, commonly as /dev/mmcblk0. The second card must be connected through another independently addressable interface. Possible layouts include the built-in card plus a USB reader, two USB readers, or a controller that exposes each card separately.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →#1 Best Overall
- READY TO BOOT, NO FLASHING REQUIRED: This card arrives with 64-bit Raspberry Pi OS already installed, so you can skip downloading images, flashing software, and checking checksums. Just insert it, power on, and go.
- WORKS ACROSS THE RASPBERRY PI LINEUP: Compatible with the Raspberry Pi 5, 500, 400, 4B, 3B, 3B+, 3A+, Zero 2 W, and Compute Module models - a great fit whether you're starting a new build or upgrading an old one.
- U3 / CLASS 10 SPEED: A solid speed rating for responsive everyday use - booting the desktop, running apps, coding, browsing, and general Pi projects all feel smooth and reliable.
- 64GB OF ROOM TO WORK: Plenty of space for the operating system plus your software, files, and projects - with headroom left over as your builds grow.
- THE EASY WAY TO GET STARTED: Perfect for beginners who want a working Pi out of the box, and a real time-saver for pros. Includes a printed instruction sheet with a setup guide and a link to a walkthrough video.
Community members have reported Linux MD RAID configurations using USB SDXC adapters on Pi 4 and Pi 5 systems, but those are practical community reports, not an official Raspberry Pi-supported configuration. Results depend on the adapters, operating system, kernel, partitioning, and boot design. See the Pi community configuration discussion.
Before partitioning or formatting anything, check that both cards appear as separate whole disks:
lsblk -o NAME,SIZE,MODEL,SERIAL,TYPE,TRAN,MOUNTPOINTS
ls -l /dev/disk/by-id/Record stable paths under /dev/disk/by-id/ where available. Names such as /dev/sda and /dev/sdb can change after a reboot or reconnection. Do not continue unless you can identify both physical cards and their partitions without ambiguity.
When microSD RAID is a poor fit
microSD cards vary in endurance and failure behavior. Their sustained-write performance, controller behavior, and usable life are not always obvious from the label. RAID does not remove those limits, and rebuilding a mirror adds sustained activity to the surviving member.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- Write-heavy services: databases, logging, surveillance recording, torrents, and frequently rewritten caches are generally poor matches for microSD RAID.
- Root filesystem activity: package updates, logs, swap, and containers can create writes even when a Pi seems mostly idle.
- Shared components: the two cards may still depend on the same Pi, power supply, USB hub, reader enclosure, cabling, and cooling. Any shared failure can take both members offline.
- Similar media: two cards from the same model or batch may share wear or manufacturing risks. Matching capacity simplifies setup, but does not make failures independent.
Do not infer endurance from an A2 label: A2 is an application-performance classification, not an endurance rating. Raspberry Pi’s current official cards are listed in 32 GB, 64 GB, and 128 GB capacities with C10/U3/V30/A2 classifications; those are product specifications, not evidence that the cards are suited to continuous server writes (Raspberry Pi card documentation).
What RAID 1 does—and does not—protect
A healthy mirror can keep a data volume available after some single-member failures, giving you time to replace a card. It does not create an independent historical copy.
- Not protected: accidental deletion or overwrite, filesystem corruption mirrored to both cards, a bad update, malware, or operator error.
- Not protected: failure of the Pi, power supply, shared reader or hub, or damage from fire, theft, water, or electrical fault.
- Not guaranteed: recovery if both cards fail, the remaining member fails during rebuild, or a device disconnect is misread as a card failure.
Keep a backup on storage outside the array. For important files, use a backup with version history or snapshots where possible, and periodically test restoring files. RAID can reduce downtime in some cases; a separate backup addresses many causes of loss that mirroring cannot.
Recommended approach: mirror a data volume, not the boot setup
The steps below create a data-only RAID 1 array after the Pi has booted from a separate medium. That keeps the firmware boot path separate from the array. You need a Linux-capable Pi, two independently visible cards, adequate power for the readers, and a backup destination outside the array. Raspberry Pi documentation lists supported boot-media options and installation guidance by model (installation documentation); availability of USB or PCIe storage depends on the Pi model and hardware.
Destructive-operation warning: partitioning, creating an array, and formatting can erase data. Confirm the device identity and current contents before every destructive command. Replace example names and placeholders only after verifying the exact card and partition.
Rank #2
- SanDisk 32GB Ultra microSDHC 120MB/s A1 Class 10 UHS-I
1. Install mdadm and identify the cards
On a Debian-based Raspberry Pi OS installation, install the RAID management tools:
sudo apt update
sudo apt install mdadmList disks and stable identifiers, then record which whole-disk path belongs to each card:
lsblk -o NAME,SIZE,MODEL,SERIAL,TYPE,TRAN,MOUNTPOINTS
ls -l /dev/disk/by-id/2. Unmount and partition both cards
If a card contains data you need, stop and back it up before proceeding. Unmount any mounted partitions, substituting the verified partition paths:
Recommended Free Tools
sudo umount /dev/sdX1
sudo umount /dev/sdY1Use fdisk, parted, or another partition editor to create the same partition layout on both cards: one partition per card, equal in size, with the Linux RAID partition type when supported by the tool. Do not copy sector numbers from another system; reported capacity and alignment vary. Check the result:
sudo fdisk -l /dev/sdX
sudo fdisk -l /dev/sdY3. Create the RAID 1 array and wait for synchronization
Use the two verified partition paths—not the whole-disk paths—to create the array. The following placeholders must be replaced with the actual stable partition identifiers from your system:
sudo mdadm --create --verbose /dev/md0
--level=1
--raid-devices=2
/dev/disk/by-id/<card-one>-part1
/dev/disk/by-id/<card-two>-part1Creating the array starts an initial synchronization. Do not treat the mirror as fully synchronized until that process completes. Monitor it with:
cat /proc/mdstat
sudo mdadm --detail /dev/md0Status wording varies by kernel and mdadm version. Check the reported state and progress rather than relying on one exact phrase.
4. Create a filesystem and mount the volume
Only format the newly assembled array if you intend to erase its contents. For a new ext4 data volume:
sudo mkfs.ext4 /dev/md0
sudo mkdir -p /srv/raid1
sudo mount /dev/md0 /srv/raid1
df -h /srv/raid1Verify basic access by writing and reading a disposable test file:
Rank #3
- Up To 48MB/s Read Speed
- 10-year warranty
- Easily Back Up Files With "SanDisk Memory Zone" App
- SD adapter included for compatibility with digital cameras
- The 32GB SanDisk Ultra microSDHC UHS-I Memory Card works with any device that has a microSDHC card slot
sudo sh -c 'echo RAID1-test > /srv/raid1/test.txt'
cat /srv/raid1/test.txt5. Save the array configuration and mount at startup
Record the array definition in the system’s mdadm configuration:
sudo mdadm --detail --scan | sudo tee -a /etc/mdadm/mdadm.confGet the filesystem UUID:
sudo blkid /dev/md0Add an /etc/fstab entry using the UUID reported for the filesystem, not the example placeholder:
UUID=<filesystem-uuid> /srv/raid1 ext4 defaults,noatime 0 2Test the entry before rebooting:
sudo umount /srv/raid1
sudo mount -a
findmnt /srv/raid1The Raspberry Pi Magazine NAS guide also demonstrates creating an mdadm array, formatting /dev/md0, and persisting a mount.
Test failure handling before relying on the mirror
A simulated member failure can confirm that the volume remains readable while degraded. Use the exact partition path for the intended member; do not substitute a guessed device name:
sudo mdadm --manage /dev/md0 --fail /dev/sdX1
sudo mdadm --detail /dev/md0If the volume remains accessible, remove that failed member:
sudo mdadm --manage /dev/md0 --remove /dev/sdX1After replacing or reinitializing the card and creating a matching partition, add its verified partition path back to the array:
Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchWindows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallsudo mdadm --manage /dev/md0 --add /dev/sdX1
watch cat /proc/mdstatMonitor until the rebuild finishes and verify the array state with mdadm --detail. Rebuild reads and writes can stress the surviving card. Do not remove a member from a live system unless you understand the specific reader and device behavior; a simulation is not a substitute for a recovery plan.
Troubleshooting common failures
A reader disconnects or the array becomes degraded
A missing device may be a reader, cable, hub, power, contact, or card problem. Review recent kernel messages and current devices before marking a card failed:
dmesg --ctime | tail -n 100
lsblk
sudo mdadm --detail /dev/md0Check power, cables, hub stability, reader compatibility, and card seating. Do not assume a disconnect proves that the card itself has failed.
Rank #4
- SMOOTH CONTENT CAPTURE: Class 10, U3, V30 speed class performance with read speeds up to 100MB/s for fast and smooth burst mode HD Photography and 4K Ultra HD Videography²
- FASTER APP LAUNCH: A1 App Performance enables apps to run directly from the microSD card, delivering faster app launch and performance. A1 provides minimally 1500 IOPS (Read) and 500 IOPS (Write)
- EXTENSIVE COMPATIBILITY: Record and transfer videos, photos, music, files and more from microSD enabled host devices such as Android smartphones and tablets, action and surveillance cameras, drones, computers and more
- USE WITH SD HOST DEVICES: Included SD adapter for compatibility with SD enabled host devices including DSLR cameras, video cameras, desktops, and laptops
- EXTREME RELIABILITY: Shock Proof, Temperature Proof, Waterproof, Drop Proof, X-Ray Proof, Wearout Proof, Vibration Proof, ESD Proof, and Humidity Proof³
The array appears under a different name
Do not assume it will always assemble as /dev/md0. Inspect metadata and array definitions:
sudo mdadm --examine --scan
sudo mdadm --detail --scanMounting by filesystem UUID, as in the earlier fstab setup, avoids tying the mount to a particular md device name.
Both members are degraded during rebuild
Stop unnecessary writes and make an independent copy of readable data before attempting recovery. Forced assembly is a recovery operation, not routine administration; the kernel MD documentation covers array management and recovery concepts. Avoid casual --assemble --force attempts, which can worsen a difficult recovery if used on the wrong devices or state.
A file is deleted or the filesystem is corrupted
A mirrored deletion or corrupted state can exist on both members. Restore from the separate backup or versioned copy; RAID itself does not provide historical versions.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Can the Raspberry Pi boot from a RAID 1 array?
Do not equate three different things: a data array working after Linux starts, Linux assembling an array early in boot, and the Raspberry Pi firmware locating and loading boot files from the arrangement. A data-only array avoids much of that complexity.
Free tools Windows power users keep installed
One-click scans. No signup required.
Root-on-RAID requires careful coordination of boot partitions, initramfs modules, early array assembly, mdadm.conf, device identifiers, and degraded-boot recovery. Community examples describe mirrored boot and root partitions, but they are configuration-specific rather than a universal recipe; see the community discussion of boot and root mirroring and the USB SDXC RAID report.
Raspberry Pi documentation describes USB mass-storage boot on Pi 4 and newer flagship models subject to boot-order configuration and hardware compatibility, and notes that early Pi 4 boards may need a bootloader update. That does not mean a Pi will automatically boot from whichever member of an arbitrary software mirror remains available. Consult the current computer documentation and boot configuration documentation for the specific model and firmware. For a reliability-focused setup, keep the boot path simple and use RAID for data unless you have tested a model-specific root-on-RAID recovery procedure.
Choose between microSD RAID, an SSD, and backups
| Option | Advantages | Trade-offs | Best fit |
|---|---|---|---|
Two microSD cards in mdadm RAID 1 |
Low-cost learning project; may preserve availability after some single-card failures. | Needs independently visible devices; adds reader, hub, power, endurance, and recovery concerns; is not a backup. | Lab, low-write data, or an availability experiment with a tested recovery plan. |
| One card plus scheduled image backup or clone | Simple and provides a recovery copy. | There may be downtime after failure, and changes since the last copy can be lost. | Basic Pi projects where simplicity matters more than uninterrupted service. |
| USB SSD | Generally a more suitable storage choice for sustained server workloads. | Costs more and needs enclosure, cable, and power planning. | Most home servers and write-active services. |
| NVMe through a compatible Pi 5 PCIe setup | Offers a higher-performance storage path for appropriate Pi 5 hardware. | Requires additional hardware and model-specific compatibility checks. | Pi 5 servers or workloads that benefit from faster storage. |
| Two SSDs in RAID 1 | Combines mirroring with a more suitable media choice than microSD for many server workloads. | Still needs separate backups and adds power and hardware complexity. | Availability-focused storage with a tested backup plan. |
| Independent backup, snapshots, or application-level replication | Can preserve versions or independent copies beyond what a mirror retains. | Requires storage, configuration, and restore testing. | Valuable data that must be recoverable after deletion, corruption, or device loss. |
For ordinary Pi use, a single reputable boot card plus scheduled backups may be easier to restore than microSD RAID. For databases, containers, logging, or NAS use, an SSD or compatible NVMe setup is usually a better storage foundation. Raspberry Pi Imager can flash an operating system to a boot medium, but it does not manage RAID or replace a backup (Raspberry Pi Imager).
Choosing cards and readers
- Choose equal nominal capacities and partition both cards to a common size that fits the smaller usable device.
- Use cards from a reputable source; avoid treating advertised performance labels as proof of endurance.
- For sustained writes, reconsider microSD rather than assuming a “high speed” or A2 label makes it a server drive.
- Choose readers or controllers only after verifying that Linux exposes each card as a separate block device.
- Plan for sufficient USB power and avoid making a fragile shared hub the critical link between both members.
- Keep the backup on a physically or logically independent destination.
Raspberry Pi’s official card page lists product capacities and performance classifications, but those specifications are not a guarantee of RAID suitability or service life. Check the current official microSD product page for availability by region; pricing and reseller options vary.
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteQuick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
