Replacing a failed drive in an md raid1/raid10: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
**If in an array a partition of the failed drive is not marked as faulty, before removing run <code># mdadm --manage /dev/md1 --fail /dev/sda2</code> | **If in an array a partition of the failed drive is not marked as faulty, before removing run <code># mdadm --manage /dev/md1 --fail /dev/sda2</code> | ||
*Insert a new physical disk | *Insert a new physical disk | ||
*Copy the partition table to the new drive from its mirror: <code>sgdisk -R /dev/sda /dev/sdb</code> (from <code>sdb</code> to <code>sda</code>) | *Copy the partition table to the new drive from its mirror: | ||
**For gpt partition table: <code>sgdisk -R /dev/sda /dev/sdb</code> (from <code>sdb</code> to <code>sda</code>) | |||
***<code>sgdisk -G /dev/sdb</code> | |||
[[Category: Linux]] | [[Category: Linux]] | ||
Revision as of 20:11, 2 July 2015
- Check if the kernel already removed the faild drive from the arrays:
# mdadm --detail /dev/md0- If not, remove it by hand:
# mdadm /dev/md0 --remove /dev/sda1 - If in an array a partition of the failed drive is not marked as faulty, before removing run
# mdadm --manage /dev/md1 --fail /dev/sda2
- If not, remove it by hand:
- Insert a new physical disk
- Copy the partition table to the new drive from its mirror:
- For gpt partition table:
sgdisk -R /dev/sda /dev/sdb(fromsdbtosda)sgdisk -G /dev/sdb
- For gpt partition table: