summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/attachments/20130305/326063bf
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/attachments/20130305/326063bf')
-rw-r--r--zarb-ml/mageia-dev/attachments/20130305/326063bf/attachment-0001.html15
-rw-r--r--zarb-ml/mageia-dev/attachments/20130305/326063bf/attachment.html15
2 files changed, 30 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/attachments/20130305/326063bf/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20130305/326063bf/attachment-0001.html
new file mode 100644
index 000000000..56d0ade94
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20130305/326063bf/attachment-0001.html
@@ -0,0 +1,15 @@
+<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Mar 5, 2013 at 12:19 PM, Thomas Backlund <span dir="ltr">&lt;<a href="mailto:tmb@mageia.org" target="_blank">tmb@mageia.org</a>&gt;</span> wrote:<br>
+<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+<br>
+If you follow raid devel list you will soon learn that they dont recommend trusting the /dev/sd* naming either as it is by<br>
+no means static... :)<br>
+<br>
+depending on your hw, they may for example  hange place if you happend<br>
+to have a usb disk plugged at boot and so on.<br>
+<br>
+so the thing to check is for example  what disk is mapped as /dev/disk/by-id/*<br>
+<br>
+<br>
+where you can match on actual disc serial number and so on...<br>
+then you can be sure wich disk is failing / has failed..</blockquote><div><br></div><div>Great advice. I&#39;ll make sure the drive&#39;s serial numbers are visible without removal and then use ls /dev/disk/by-id/ to make sure I get the right one, if/when the time ever comes...<br>
+<br></div><div>Thanks again -- RJ<br><br></div></div></div></div>
diff --git a/zarb-ml/mageia-dev/attachments/20130305/326063bf/attachment.html b/zarb-ml/mageia-dev/attachments/20130305/326063bf/attachment.html
new file mode 100644
index 000000000..56d0ade94
--- /dev/null
+++ b/zarb-ml/mageia-dev/attachments/20130305/326063bf/attachment.html
@@ -0,0 +1,15 @@
+<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Tue, Mar 5, 2013 at 12:19 PM, Thomas Backlund <span dir="ltr">&lt;<a href="mailto:tmb@mageia.org" target="_blank">tmb@mageia.org</a>&gt;</span> wrote:<br>
+<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
+<br>
+If you follow raid devel list you will soon learn that they dont recommend trusting the /dev/sd* naming either as it is by<br>
+no means static... :)<br>
+<br>
+depending on your hw, they may for example  hange place if you happend<br>
+to have a usb disk plugged at boot and so on.<br>
+<br>
+so the thing to check is for example  what disk is mapped as /dev/disk/by-id/*<br>
+<br>
+<br>
+where you can match on actual disc serial number and so on...<br>
+then you can be sure wich disk is failing / has failed..</blockquote><div><br></div><div>Great advice. I&#39;ll make sure the drive&#39;s serial numbers are visible without removal and then use ls /dev/disk/by-id/ to make sure I get the right one, if/when the time ever comes...<br>
+<br></div><div>Thanks again -- RJ<br><br></div></div></div></div>