<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Feb 17, 2015 at 5:37 PM, Munir Nassar <span dir="ltr"><<a href="mailto:nassarmu@gmail.com" target="_blank">nassarmu@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">First of all, BACKUP YOUR DATA before proceeding because RAID IS NOT BACKUP.<br>
<br>
you need to find out how the drives are currently configured... are<br>
you using linux-md? assuming that you are here are some tips:<br>
<br>
mdadm --detail /dev/md0 (or wherever it is)<br>
<br>
you should see something like:<br>
0 8 17 0 active sync /dev/sdb1<br>
1 8 1 1 active sync /dev/sda1<br>
2 8 33 2 active sync /dev/sdc1<br>
3 8 49 3 active sync /dev/sdd1<br>
<br>
although in your case one of those will be listed as down, notice how<br>
i have /dev/sdb1, which means i am using the first partition... this<br>
will not always be the case (it might be 2, 3 or whatever, it may even<br>
be the entire drive)<br></blockquote><div><br></div><div>Very very much like your table. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
now, BACKUP YOUR DATA before proceeding.<br>
<br>
assuming it is a partition then you will want to copy the entire<br>
partition map over from one of the good drives (and i am assuming here<br>
that all drives are partitioned the same, again might not be)<br>
sudo /sbin/sfdisk -d /dev/GOOD| /sbinsfdisk --force /dev/NEW<br>
<br></blockquote><div>I was forced to use gdisk.<br></div><div>Would think that the commands are similar but different.<br></div><div>(I really wish that man pages had examples of BOTH good and bad commands<br></div><div>together with results from running whichever. This would be far easier for the<br></div><div>non-specialist to understand and follow.)<br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
and BACKUP YOUR DATA before proceeding<br>
<br>
Now you can add the drive to the array using mdadm:<br>
mdadm --add /dev/md0 /dev/NEW<br>
<br>
and you can monitor the rebuilding process by catting /proc/mdstat,<br>
you will most likely want to update the boot loader so that your<br>
system can boot from the new drive as well.<br></blockquote><div><br></div><div>New drive is absolutely NOT involved with anything boot. The array is <br></div><div>for storage and nothing else.<br></div><div>There is another drive for operating systems and info. <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
but BACKUP YOUR DATA before proceeding<br>
<br>
Of course, you will want to think long and hard when you are doing any<br>
of this, if you copy the partition table the wrong direction you risk<br>
destroying your data. If you are using something else in addition like<br>
LVM then you will need to adjust accordingly. most importantly however<br>
is that you BACKUP YOUR DATA. and I cannot stress this enough: BACKUP<br>
YOUR DATA before doing any of this.<br>
<br>
Remember RAID IS NOT BACKUP. so in case i have not said it enough yet:<br>
BACKUP YOUR DATA.<br></blockquote><div><br></div><div>Lots of disk changing coming up!<br><br></div><div>Thanks for your tips and insights!!<br><br></div><div>Dee<br></div></div></div></div>