![]() |
|
Fedora - Managing RAID arrays with mdadm - Printable Version +- Sick Gaming (https://sickgaming.net) +-- Forum: Computers (https://sickgaming.net/forum-86.html) +--- Forum: Linux, BSD & Unix (https://sickgaming.net/forum-88.html) +--- Thread: Fedora - Managing RAID arrays with mdadm (/thread-89859.html) |
Fedora - Managing RAID arrays with mdadm - xSicKxBot - 04-18-2019 Managing RAID arrays with mdadm Mdadm stands for Multiple Disk and Device Administration. It is a command line tool that can be used to manage software RAID arrays on your Linux PC. This article outlines the basics you need to get started with it. The following five commands allow you to make use of mdadm’s most basic features:
Notes on features mdadm --create The create command shown above includes the following four parameters in addition to the create parameter itself and the device names:
By using level=1 (mirroring) in combination with metadata=1.0 (store the metadata at the end of the device), you create a RAID1 array whose underlying devices appear normal if accessed without the aid of the mdadm driver. This is useful in the case of disaster recovery, because you can access the device even if the new system doesn’t support mdadm arrays. It’s also useful in case a program needs read-only access to the underlying device before mdadm is available. For example, the UEFI firmware in a computer may need to read the bootloader from the ESP before mdadm is started. mdadm --assemble The assemble command above fails if a member device is missing or corrupt. To force the RAID array to assemble and start when one of its members is missing, use the following command: Code: # mdadm --assemble --run /dev/md/test /dev/sda1Avoid writing directly to any devices that underlay a mdadm RAID1 array. That causes the devices to become out-of-sync and mdadm won’t know that they are out-of-sync. If you access a RAID1 array with a device that’s been modified out-of-band, you can cause file system corruption. If you modify a RAID1 device out-of-band and need to force the array to re-synchronize, delete the mdadm metadata from the device to be overwritten and then re-add it to the array as demonstrated below: Code: # mdadm --zero-superblock /dev/sdb1# mdadm --assemble --run /dev/md/test /dev/sda1 # mdadm /dev/md/test --add /dev/sdb1These commands completely overwrite the contents of sdb1 with the contents of sda1. To specify any RAID arrays to automatically activate when your computer starts, create an /etc/mdadm.conf configuration file. For the most up-to-date and detailed information, check the man pages: Code: $ man mdadm $ man mdadm.confThe next article of this series will show a step-by-step guide on how to convert an existing single-disk Linux installation to a mirrored-disk installation, that will continue running even if one of its hard drives suddenly stops working! |