<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PersonName"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:blue;
        text-decoration:underline;}
span.EmailStyle17
        {mso-style-type:personal-reply;
        font-family:Arial;
        color:navy;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>
</HEAD>
<BODY lang=EN-US link=blue vlink=blue>
<DIV>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>The software RAID (md) puts info on the
disks to identify which are part of the RAID which is why this worked for you.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>It is also why they often suggest you use
label on simple partions and refer to those in /etc/fstab instead of the
partition names.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Only God knows why they can’t just
mark the disks at install and keep track of them in Linux like every other UNIX
OS does. I recall how frustrated I was when it turned out Solaris would
rename tape drives based on discovery at boot rather than keeping the same name
all the time. At least they had a way to setup “persistence” in the
st.conf.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>And I’m old enough that the start of
“uuid” makes me think it ought to have something to do with serial
file transfers rather than disk names.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> ale-bounces@ale.org
[mailto:ale-bounces@ale.org] <b><span style='font-weight:bold'>On Behalf Of </span></b>Jim
Kinney<br>
<b><span style='font-weight:bold'>Sent:</span></b> Tuesday, November 11, 2008
11:23 PM<br>
<b><span style='font-weight:bold'>To:</span></b> <st1:PersonName w:st="on">ale@ale.org</st1:PersonName><br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [ale] SATA disk
naming</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>The drive ordering is
based more on the device ordering from the pci bus scan and sata init.
Check what cat /proc/scsi/scsi says. I bet the new sdb even though it's in a
sata#3 socket has a lower lun than sata#2.<br>
<br>
And yes, this is why the transition to UUID is happening for distros like
Fedora. I think Ubuntu also does drives by UUID as well. For some reason I
don't find UUID=c2a3c3bd-414c-4c30-a83c-38e69551808a easier to read than
/dev/sda<o:p></o:p></span></font></p>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Tue, Nov 11, 2008 at 10:18 PM, Chris Fowler <<a
href="mailto:cfowler@outpostsentinel.com">cfowler@outpostsentinel.com</a>>
wrote:<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Here is something that happened to me strange today.<br>
<br>
We have a server we are using to run VMware Server 2.0. It has<br>
2 250GB SATA drives used as a RAID1 array. These devices are sda<br>
and sdb.<br>
<br>
I noticed an ad at MicroCenter for a 1TB SATA drive @ $129. We took<br>
the ad to Fry's in Alpharetta and they matched the priced. I installed<br>
the drive in the 3rd SATA port on the MB. I booted Linux and for some<br>
odd reason Linux made the 1TB drive sdb and pused the old sdb to sdc.<br>
Not a real problem because the md driver was able to figure this out. I<br>
thought maybe the vendor who build the server plugged the cables in wrong<br>
but I checked and everything looked good.<br>
<br>
Is there a reason this happened? Can I force a drive to a device<br>
name by using a command line argument while booting Linux?<br>
<br>
On another note, I can't believe that a 1TB drive can be had for $130!<br>
We are going to use it to backup non-critical data.<br>
<br>
--<br>
Chris Fowler<br>
OutPost Sentinel, LLC<br>
Support @ SIP/<a href="mailto:support@pbx.opsdc.com">support@pbx.opsdc.com</a><br>
or 678-804-8193<br>
Email Support @ <a href="mailto:support@outpostsentinel.com">support@outpostsentinel.com</a><br>
<br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'><br>
<br clear=all>
<br>
-- <br>
-- <br>
James P. Kinney III <o:p></o:p></span></font></p>
</div>
</DIV>
<DIV STYLE="FONT-SIZE: 9pt; FONT-FAMILY: Courier New">
<FONT FACE="Arial" SIZE="2">----------------------------------<BR>CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you.<BR>----------------------------------<BR></FONT>
</DIV></BODY></HTML>