Linux Hotplug development
 help / color / mirror / Atom feed
From: David Roth <davidalanroth@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Need help with udev in CentOS 6.0 for SATA and eSATA HD
Date: Wed, 12 Oct 2011 07:11:18 +0000	[thread overview]
Message-ID: <CBFD304C-A523-465A-87AF-F2A43AEDB256@gmail.com> (raw)

I've recently installed CentOS 6.0 X86_64.

I have a server with two internal SATA hard disk drives running a  
software RAID 1. I'm adding two external eSATA hard disk drives which  
will be mirrored in a software RAID 1 too.

Please kindly correct me if this information is wrong, but I was told  
that the internal drives must be /dev/sda and /dev/sdb. And the eSATA  
should be /dev/sdc and /dev/sdd.

During my testing, I connected just one LaCie eSATA drive and it's  
getting assigned /dev/sdb while the internal drives are being  
assigned /dev/sda and /dev/sdc.

I want the internal drives to be sda and sdb. This external eSATA for  
testing to be /dev/sdc.

I've written some rules and placed them in /etc/udev/rules.d in a file  
named 10-local.rules:

KERNEL="sd*",ATTRS{model}="LaCie d2Next-Q",NAME="sdc"

The above didn't work. I wondered if matching on KERNEL might be the  
problem. So I tried this:

ATTRS{model}="LaCie d2Next-Q",NAME="sdc"

This didn't work either.

I've used udev successfully on CentOS 5 with USB drives to create  
SYMLINKs. But this is the first time I've tried to work with SATA  
drives where I want to force a renaming of the device. I don't think I  
should be trying to do a SYMLINK, because I simply want the device  
name itself changed.

By the way, I've also noticed that using udevadm it doesn't list the  
serial number of the drive like it did with udevinfo, unless I'm doing  
this wrong?
udevadm info -a -p $(udevadm info -q path -n /dev/sda)

Thanks in advance for your helpful suggestions!

David Roth


                 reply	other threads:[~2011-10-12  7:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CBFD304C-A523-465A-87AF-F2A43AEDB256@gmail.com \
    --to=davidalanroth@gmail.com \
    --cc=linux-hotplug@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox