[ale] SATA disk naming

[Jeff Lightner]

The software RAID (md) puts info on the disks to identify which are part
of the RAID which is why this worked for you.

 

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.

 

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.

 

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.

 

________________________________

From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of Jim
Kinney
Sent: Tuesday, November 11, 2008 11:23 PM
To: ale at ale.org
Subject: Re: [ale] SATA disk naming

 

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.

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

On Tue, Nov 11, 2008 at 10:18 PM, Chris Fowler
<cfowler at outpostsentinel.com> wrote:

Here is something that happened to me strange today.

We have a server we are using to run VMware Server 2.0.  It has
2 250GB SATA drives used as a RAID1 array.  These devices are sda
and sdb.

I noticed an ad at MicroCenter for a 1TB SATA drive @ $129.  We took
the ad to Fry's in Alpharetta and they matched the priced.  I installed
the drive in the 3rd SATA port on the MB.  I booted Linux and for some
odd reason Linux made the 1TB drive sdb and pused the old sdb to sdc.
Not a real problem because the md driver was able to figure this out.  I
thought maybe the vendor who build the server plugged the cables in
wrong
but I checked and everything looked good.

Is there a reason this happened?  Can I force a drive to a device
name by using a command line argument while booting Linux?

On another note, I can't believe that a 1TB drive can be had for $130!
We are going to use it to backup non-critical data.

--
Chris Fowler
OutPost Sentinel, LLC
Support @ SIP/support at pbx.opsdc.com
 or 678-804-8193
Email Support @ support at outpostsentinel.com


_______________________________________________
Ale mailing list
Ale at ale.org
http://mail.ale.org/mailman/listinfo/ale




-- 
-- 
James P. Kinney III
----------------------------------
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.
----------------------------------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.ale.org/pipermail/ale/attachments/20081112/d0eb2f2a/attachment-0001.html