No subject

number. If sdb won't play ball, use the other two and a process of
elimination.

Or you might find the same information under /dev, depending on distro.

Mark

PS On a phone - don't cut and paste commands from this message.

--bcaec517a74251ea3704c42c1df0
Content-Type: text/html; charset=ISO-8859-1

<p>On Jul 5, 2012 10:45 PM, &quot;Roger&quot; &lt;<a href="mailto:roger at roger-beaumont.co.uk">roger at roger-beaumont.co.uk</a>&gt; wrote:</p>
<p>&gt; After 2 RAID failures (both drives) I&#39;m twitchy.</p>
<p>Yes, I would be too :)</p>
<p>&gt; I think I need to:<br>
&gt; 1 - buy another drive,<br>
&gt; 2 - fit and partition it,<br>
&gt; 3 - add its partitions as spares,<br>
&gt; 4 - wait for md2 to resynchronise,<br>
&gt; 5 - &#39;Fail&#39; sdb2 and sdb3, then<br>
&gt; 6 - pull sdb out of the machine and chuck it in the recycling.<br>
&gt;<br>
&gt; Is that the right thing to do and have I got the sequence right?</p>
<p>At the very least, you&#39;ve missed the zeroth step - check you have a valid, current backup &lt;ducks/&gt;</p>
<p>And of course boot &#39;n&#39; nuke sdb before you chuck it...</p>
<p>&gt; PS - and I&#39;m sure I ought to know this - How do I check exactly which drive is /dev/sdb ?</p>
<p>From memory, smartctl -i &lt;device&gt; should give you the model and serial number. If sdb won&#39;t play ball, use the other two and a process of elimination.</p>
<p>Or you might find the same information under /dev, depending on distro.</p>
<p>Mark</p>
<p>PS On a phone - don&#39;t cut and paste commands from this message.</p>

--bcaec517a74251ea3704c42c1df0--