RE: Solaris 10 x64, EMC Powerpath and ASM
- From: "Martin Bach" <development@xxxxxxxxxxxxxxxxx>
- To: development@xxxxxxxxxxxxxxxxx
- Date: Tue, 9 Nov 2010 17:10:08 +0100 (CET)
Hello all,
I figured this out and have my cluster up and running. Should anyone later
on google this, here's the solution.
The emcpower devices are named using this convention:
emcpower#[a-p]
Example: /dev/rdsk/emcpower1a
The number is just a sequence number Solaris assigns when enumerating the
attached storage.
The [a-p] map to the slices of the disks. For example, slice 4 is letter
"e" on Solaris, other OSs differ.
Before you can the emcpower device in Solaris INTEL, you have to use fdisk
to initialise it. For this purpose, I found that emcpower#p0 is the right
device to use. Example would be
# fdisk /dev/rdsk/emcpower0p0
You then create a partition to span the whole disk of type Solaris2. I
found that it wasn't necessary to make the partition active. Exist fdisk
and start format. The difference here is that you pass emcpower0a as the
argument (or whatever you get from powermt display).
Within format, use partition, and modify slice 4. Don't start at cylinder
0, starting with 3 worked for me. There used to be a problem with the VTOC
in Solaris SPARC, not sure if that applies in Solaris Intel but I decided
to better be safe then sorry.
With that done, label the disk and exit the format utility.
Change ownership and permissions on /dev/rdsk/emcpower* to
<gridOwner>:<OSASM group> and chmod to 0600.
Now OUI recognised the emcpower#e slice as a target for the installation.
Hope this helps,
Martin
http://martincarstenbach.wordpress.com/
http://uk.linkedin.com/in/martincarstenbach
> Sorry-resending due to overquoting ...
>
> Hi all,
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
