2,187
edits
(→Backup: Added script) |
(→Troubleshooting: Added "Software RAID") |
||
Line 321: | Line 321: | ||
# Assuming it states that say <code>eth0</code> has been changed to <code>eth1</code> then just update the <code>/etc/network/interfaces</code> file | # Assuming it states that say <code>eth0</code> has been changed to <code>eth1</code> then just update the <code>/etc/network/interfaces</code> file | ||
=== Software RAID === | |||
==== Replacing a RAID 1 Disk ==== | |||
This procedure was written from the following starting point... | |||
* A machine originally with two disks in RAID1 has failed, one disk has been replaced, and machine started again | |||
...and adapted from this post http://www.howtoforge.com/replacing_hard_disks_in_a_raid1_array | |||
# Backup whatever you can before proceeding, one mistake or system error could destroy your machine | |||
# Confirm which disk is new, and which is old (if the new disk is blank this is easy as there will be no partition info!) | |||
#* <code> fdisk -l </code> | |||
# Partition the new disk the same as the original | |||
#* <code> sfdisk -d /dev/sda | sfdisk /dev/sdb </code> | |||
# Confirm that the layout of both disks is now that same | |||
#* <code> fdisk -l </code> | |||
# Add the newly created partitions to the RAID disks | |||
#* <code> mdadm --manage /dev/md0 --add /dev/sdb1 </code> | |||
#* ''You may have more <code>sd</code> partitions than <code>md</code> partitions, the array size return through <code>mdadm -D /dev/md*</code> should roughly match the number of blocks found from <code>fdisk -l</code>'' | |||
# The arrays should now be being sync'ed, check progress by monitoring <code>/proc/mdstat</code> | |||
#* <code> more /proc/mdstat </code> | |||
[[Category:VMware]] | [[Category:VMware]] | ||
[[Category:Zimbra]] | [[Category:Zimbra]] | ||
[[Category:MySQL]] | [[Category:MySQL]] |