Differences

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

--- raid [2009/11/17 05:56] – 172.26.0.166
+++ raid [2009/11/19 07:13] – 172.26.0.166
@@ Line 50: / Line 50: @@
 unused devices: <none></code>
 ==== Repair RAID ====
 When a disk is failing you might see errors in the system logs from smartd like this:
@@ Line 79: / Line 78: @@
 # mdadm /dev/md3 --fail /dev/hda1 --remove /dev/hda1
 # mdadm /dev/md4 --fail /dev/hda6 --remove /dev/hda6</code>
+''/dev/md2'' is a RAID0 stripe mounted as ''/scratch'', so we have to umount it and then stop it (you can't remove volumes from a stripe):
+<code># umount /dev/md2
+# mdadm --stop /dev/md2</code>
+<note warning> You must Shutdown the server before you physically remove the drive! </note>
 Shut the server down and replace the faulty drive with a new one.  After booting your drive letters may have shifted around, so just be sure to verify which is which before proceeding.
 Clone the partition table from the good drive to the bad one:
@@ Line 91: / Line 93: @@
 /dev/sdc: msdos partitions 1
 </code>
-You can now add the new partitions back to the arrays:
+Re-create the scratch partition (RAID0):
+<code># mdadm --create --verbose /dev/md2 --level=0 --raid-devices=2 /dev/hda5 /dev/hdd5
+# mkfs.ext3 /dev/md2
+# mount /dev/md2 /scratch</code>
+You can now add the new partitions back to the RAID1 arrays:
 <code># mdadm /dev/md0 --add /dev/hdd2
 # mdadm /dev/md1 --add /dev/hdd3
@@ Line 135: / Line 141: @@
 How do you know which physical disk is broken to replace it?
+f
 ===== Hardware RAID =====