<div class="gmail_quote">On Sat, Nov 20, 2010 at 5:33 PM, Jean-Yves Avenard <span dir="ltr"><<a href="mailto:jyavenard@gmail.com">jyavenard@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi<br>
<div><div></div><div class="h5"><br>md has always been happier with entire disks.</div></div></blockquote><div><br></div><div>At the time, I was too chicken to make a bootable raid.</div><div>It's been working fine for years, otherwise.</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">Why don't just just remove sdd2 from the array, format it, re-add it<br>
and let md rebuild the array?<br></blockquote><div><br></div><div>That's the way things are looking. I guess I just wanted some hint that the drive was</div><div>indeed corrupted, and it wasn't something else. (Just for example, I'm reading about</div>
<div>a lot of drives being re-mapped after an upgrade.)</div><div><br></div><div>You mentioned, "format". As I read things, raid doesn't require a formatted drive.</div><div>(Only an fdisk'd one.) Isn't it that all I have to do is:</div>
<div><br></div><div>mdadm /dev/md0 -f /dev/sda2 # fail it</div><div>mdadm /dev/md0 -r /dev/sda2 # remove it</div><div>mdadm /dev/md0 -a /dev/sda2 # hot add it</div><div><br></div><div>?</div><div><br></div><div>Thanks!</div>
<div><br></div></div>