Differences

This shows you the differences between two versions of the page.

--- linux:centos:software-raid1-setup [2020/04/13 11:58] – odefta
+++ linux:centos:software-raid1-setup [2025/01/02 18:22] (current) – external edit 127.0.0.1
@@ Line 3: / Line 3: @@
 ====== Intro ======
-RAID 1 = mirrored pair of two hard disks
+RAID 1 = mirrored pair of two hard disks \\
-If one disk fail, the raid will continue to be operational.
+If one disk fail, the raid will continue to be operational. \\
-Read performance will be increased for parallel read operations.
+Read performance will be increased for parallel read operations. \\
-Write performance will be likely the same (almost the same).
+Write performance will be likely the same (almost the same). \\
-===== Prerequisites =====
+====== Prerequisites ======
   * Two hard disks of same size.
@@ Line 17: / Line 17: @@
 </code>
-===== Setup =====
+====== Setup ======
+==== Format first hard disk (/dev/sda) with xfs (supports also hard disks higher than 2TB) ====
+<code>
+mkfs.xfs -f -L DISK1 /dev/sda
+</code>
+-f = force \\
+-L = hdd label
+==== Format second hard disk (/dev/sdb) with xfs ====
+<code>
+mkfs.xfs -f -L DISK2 /dev/sdb
+</code>
+==== Create the raid array ====
+<code>
+mdadm --verbose --create /dev/md0 --level=raid1 --raid-devices=2 /dev/sda /dev/sdb
+</code>
+==== Format the raid array as xfs ====
+<code>
+mkfs.xfs /dev/md0
+</code>
+==== Mount the raid array (in /data1 folder) ====
+<code>
+mkdir /data1
+</code>
+<code>
+mount /dev/md0 /data1
+</code>
+==== Automatically mount the raid volume at startup ====
+Edit **/etc/fstab** and add:
+<code>
+/dev/md0 /data1 xfs defaults 0 0
+</code>
+==== Load automatically the raid 1 configuration at startup  ====
+<code>
+mdadm --detail --scan --verbose >> /etc/mdadm.conf
+</code>
+==== Check the raid configuration ====
+<code>
+mdadm -D /dev/md0
+</code>
+<code>
+/dev/md0:
+           Version : 1.2
+     Creation Time : Mon Apr 13 03:07:50 2020
+        Raid Level : raid1
+        Array Size : 3906886464 (3725.90 GiB 4000.65 GB)
+     Used Dev Size : 3906886464 (3725.90 GiB 4000.65 GB)
+      Raid Devices : 2
+     Total Devices : 2
+       Persistence : Superblock is persistent
+     Intent Bitmap : Internal
+       Update Time : Mon Apr 13 15:24:47 2020
+             State : clean, resyncing
+    Active Devices : 2
+   Working Devices : 2
+    Failed Devices : 0
+     Spare Devices : 0
+Consistency Policy : bitmap
+     Resync Status : 90% complete
+              Name : medjavaro:0  (local to host medjavaro)
+              UUID : 257d9837:5eda9e27:59a51c12:d139b615
+            Events : 15822
+    Number   Major   Minor   RaidDevice State
+       8       16        0      active sync   /dev/sda
+       8       32        1      active sync   /dev/sdb
+</code>
+==== Replace a failed hard disk in the raid configuration ====
+Suppose the /dev/sdb hard disk failed. \\
+To replace it with a good hdd, set it as failed and remove it from the array:
+<code>
+mdadm /dev/md0 --fail /dev/sdb --remove /dev/sdb
+</code>
+Add the new device to the array:
+<code>
+mdadm --add /dev/md0 /dev/sdb
+</code>
+==== Re-add a good hard disk (after cable disconnection for example) ====
+After reinserting the hard disk, it may be mounted now on a different device letter.\\ Ckeck it by running:
+<code>
+fdisk -l
+</code>
+Output:
+<code>
+...
+Disk /dev/sdd: 4000.8 GB, 4000787029504 bytes, 7814037167 sectors
+Units = sectors of 1 * 512 = 512 bytes
+Sector size (logical/physical): 512 bytes / 4096 bytes
+I/O size (minimum/optimal): 4096 bytes / 4096 bytes
+</code>
+After identifying it, re-add it to the raid array with:
+<code>
+mdadm --manage /dev/md0 --add /dev/sdd
+</code>