This discussion is archived
10 Replies Latest reply: Apr 30, 2011 8:33 AM by Levi-Pereira RSS

disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui

857371 Newbie
Currently Being Moderated
Hi All,


Trying 11gr2 rac fresh installtion on two nodes sun sparc physical boxes solaris 10 update 9 having iscsi luns ( created from sun VM storage array) Every thing is smooth till
we come to option "create ASM Disk Group" when it is not able to discover the disks for default ASM group. tried using changing discovery paths '/dev/rdsk/*' but of no help. OS on both nodes shows disks are available using format and and created a file system on these to rule out anything wrong with the luns.
Could not find anything in installation manuals.
Any help please.

Thanks in advance.
  • 1. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    gokhanatil Oracle ACE
    Currently Being Moderated
    user1429015 wrote:
    Hi All,


    Trying 11gr2 rac fresh installtion on two nodes sun sparc physical boxes solaris 10 update 9 having iscsi luns ( created from sun VM storage array) Every thing is smooth till
    we come to option "create ASM Disk Group" when it is not able to discover the disks for default ASM group. tried using changing discovery paths '/dev/rdsk/*' but of no help. OS on both nodes shows disks are available using format and and created a file system on these to rule out anything wrong with the luns.
    Could not find anything in installation manuals.
    Any help please.

    Thanks in advance.
    Please be sure that owner of these partitions are oracle:dba instead of sys.

    You may want to check the following doc: http://blogs.sun.com/pomah/entry/configuration_example_of_oracle_asm

    Regards

    Gokhan
  • 2. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    Levi-Pereira Guru
    Currently Being Moderated
    Hi Gokhan,

    It is good your interest in helping people in the forum. But look at some recommendations.
    Preferably the references in official documentation from Oracle.
    Please be sure that owner of these partitions are oracle:dba instead of sys.
    You may want to check the following doc: http://blogs.sun.com/pomah/entry/configuration_example_of_oracle_asm
    Set group dba to ASMDISKS is wrong it's only for version 11.1 or earlier, the right group to 11.2 is OSASM(default name is asmadmin) group.

    New SYSASM Privilege and OSASM Group for ASM Administration
    OSASM is a new operating system (OS) group that is used exclusively for ASM. Members of the OSASM group can connect AS SYSASM using OS authentication and have full access to ASM.
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17222/changes.htm#UPGRD12483


    Suggest official documentation is 100% trusted.
    Configuring Disk Devices for Oracle ASM
    http://download.oracle.com/docs/cd/E11882_01/install.112/e17213/storage.htm#CACHGBAH

    Regards,
    Levi Pereira
  • 3. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    Bjoern Rost Oracle ACE Director
    Currently Being Moderated
    Levi is right, permissions should be grid:asmadmin and 660 for 11.2.
    I really screwed this one up last week, I forgot to set the permissions to group-writable and added a disk. It as no problem for asm but unfortunately the database (osuser oracle) could not access the disk and it crashed both instances. This is one thing I will remember now =)
  • 4. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    gokhanatil Oracle ACE
    Currently Being Moderated
    Levi Pereira wrote:
    Hi Gokhan,

    It is good your interest in helping people in the forum. But look at some recommendations.
    Preferably the references in official documentation from Oracle.
    Please be sure that owner of these partitions are oracle:dba instead of sys.
    You may want to check the following doc: http://blogs.sun.com/pomah/entry/configuration_example_of_oracle_asm
    Set group dba to ASMDISKS is wrong it's only for version 11.1 or earlier, the right group to 11.2 is OSASM(default name is asmadmin) group.

    New SYSASM Privilege and OSASM Group for ASM Administration
    OSASM is a new operating system (OS) group that is used exclusively for ASM. Members of the OSASM group can connect AS SYSASM using OS authentication and have full access to ASM.
    http://download.oracle.com/docs/cd/E11882_01/server.112/e17222/changes.htm#UPGRD12483


    Suggest official documentation is 100% trusted.
    Configuring Disk Devices for Oracle ASM
    http://download.oracle.com/docs/cd/E11882_01/install.112/e17213/storage.htm#CACHGBAH

    Regards,
    Levi Pereira
    Thanks Levi for correcting. oracle:dba is an old habit, I should be careful about new practices of 11gR2
  • 5. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    857371 Newbie
    Currently Being Moderated
    Thanks Gokhan and Levi,

    I followed the suggestion but still not able to discover the disks during installation. I even installed the grid infrastructure binaries and than tried to configure the ASM diskgroup from
    asmca utiliy but the issue remains the same with permission set to 660 and group to asmadmin / osasm group. I even tried for installation on single node with local harddisk attached to system, it was not even able to discover that local harddisk artition also while permissions set to 660 and proper group asmadmin/osasm etc.

    Any idea what else I am missing

    Thanks

    bash-3.00# echo | format
    Searching for disks...done


    AVAILABLE DISK SELECTIONS:
    0. c1t0d0 <SUN72G cyl 14087 alt 2 hd 24 sec 424>
    /pci@1f,700000/scsi@2/sd@0,0
    1. c1t1d0 <FUJITSU-MAP3735NSUN72G-0401 cyl 14087 alt 2 hd 24 sec 424>
    /pci@1f,700000/scsi@2/sd@1,0
    2. c1t2d0 <FUJITSU-MAP3735NSUN72G-0401 cyl 14087 alt 2 hd 24 sec 424>
    /pci@1f,700000/scsi@2/sd@2,0
    3. c1t3d0 <FUJITSU-MAP3735NSUN72G-0401 cyl 14087 alt 2 hd 24 sec 424>
    /pci@1f,700000/scsi@2/sd@3,0
    4. c3t600144F04DB32BF100000C29FF290900d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 160>
    /scsi_vhci/ssd@g600144f04db32bf100000c29ff290900
    5. c3t600144F04DB32D1E00000C29FF290900d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 160>
    /scsi_vhci/ssd@g600144f04db32d1e00000c29ff290900
    6. c3t600144F04DB4077C00000C29FF290900d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 16>
    /scsi_vhci/ssd@g600144f04db4077c00000c29ff290900
    7. c3t600144F04DB4077D00000C29FF290900d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 16>
    /scsi_vhci/ssd@g600144f04db4077d00000c29ff290900
    8. c3t600144F04DB4077E00000C29FF290900d0 <SUN-SOLARIS-1 cyl 32766 alt 2 hd 4 sec 16>
    /scsi_vhci/ssd@g600144f04db4077e00000c29ff290900
    Specify disk (enter its number): Specify disk (enter its number):
    bash-3.00#


    bash-3.00# pwd
    /dev/rdsk
    bash-3.00# ls -lL c3*
    crw-rw---- 1 oracle asmadmin 118, 72 Apr 28 21:52 c3t600144F04DB32BF100000C29FF290900d0s0
    crw-rw---- 1 oracle asmadmin 118, 73 Apr 28 21:52 c3t600144F04DB32BF100000C29FF290900d0s1
    crw-rw---- 1 oracle asmadmin 118, 74 Apr 28 21:52 c3t600144F04DB32BF100000C29FF290900d0s2
    crw-rw---- 1 oracle asmadmin 118, 75 Apr 28 21:52 c3t600144F04DB32BF100000C29FF290900d0s3
    crw-rw---- 1 oracle asmadmin 118, 76 Apr 28 21:52 c3t600144F04DB32BF100000C29FF290900d0s4
    crw-rw---- 1 oracle asmadmin 118, 77 Apr 28 21:52 c3t600144F04DB32BF100000C29FF290900d0s5
    crw-rw---- 1 oracle asmadmin 118, 78 Apr 28 21:52 c3t600144F04DB32BF100000C29FF290900d0s6
    crw-rw---- 1 oracle asmadmin 118, 79 Apr 28 21:52 c3t600144F04DB32BF100000C29FF290900d0s7
    crw-rw---- 1 oracle asmadmin 118, 80 Apr 28 21:52 c3t600144F04DB32D1E00000C29FF290900d0s0
    crw-rw---- 1 oracle asmadmin 118, 81 Apr 28 21:52 c3t600144F04DB32D1E00000C29FF290900d0s1
    crw-rw---- 1 oracle asmadmin 118, 82 Apr 28 21:52 c3t600144F04DB32D1E00000C29FF290900d0s2
    crw-rw---- 1 oracle asmadmin 118, 83 Apr 28 21:52 c3t600144F04DB32D1E00000C29FF290900d0s3
    crw-rw---- 1 oracle asmadmin 118, 84 Apr 28 21:52 c3t600144F04DB32D1E00000C29FF290900d0s4
    crw-rw---- 1 oracle asmadmin 118, 85 Apr 28 21:52 c3t600144F04DB32D1E00000C29FF290900d0s5
    crw-rw---- 1 oracle asmadmin 118, 86 Apr 28 21:52 c3t600144F04DB32D1E00000C29FF290900d0s6
    crw-rw---- 1 oracle asmadmin 118, 87 Apr 28 21:52 c3t600144F04DB32D1E00000C29FF290900d0s7
    crw-rw---- 1 oracle asmadmin 118, 96 Apr 28 21:52 c3t600144F04DB4077C00000C29FF290900d0s0
    crw-rw---- 1 oracle asmadmin 118, 97 Apr 28 21:52 c3t600144F04DB4077C00000C29FF290900d0s1
    crw-rw---- 1 oracle asmadmin 118, 98 Apr 28 21:52 c3t600144F04DB4077C00000C29FF290900d0s2
    crw-rw---- 1 oracle asmadmin 118, 99 Apr 28 21:52 c3t600144F04DB4077C00000C29FF290900d0s3
    crw-rw---- 1 oracle asmadmin 118,100 Apr 28 21:52 c3t600144F04DB4077C00000C29FF290900d0s4
    crw-rw---- 1 oracle asmadmin 118,101 Apr 28 21:52 c3t600144F04DB4077C00000C29FF290900d0s5
    crw-rw---- 1 oracle asmadmin 118,102 Apr 28 21:52 c3t600144F04DB4077C00000C29FF290900d0s6
    crw-rw---- 1 oracle asmadmin 118,103 Apr 28 21:52 c3t600144F04DB4077C00000C29FF290900d0s7
    crw-rw---- 1 oracle asmadmin 118, 88 Apr 28 21:52 c3t600144F04DB4077D00000C29FF290900d0s0
    crw-rw---- 1 oracle asmadmin 118, 89 Apr 28 21:52 c3t600144F04DB4077D00000C29FF290900d0s1
    crw-rw---- 1 oracle asmadmin 118, 90 Apr 28 21:52 c3t600144F04DB4077D00000C29FF290900d0s2
    crw-rw---- 1 oracle asmadmin 118, 91 Apr 28 21:52 c3t600144F04DB4077D00000C29FF290900d0s3
    crw-rw---- 1 oracle asmadmin 118, 92 Apr 28 21:52 c3t600144F04DB4077D00000C29FF290900d0s4
    crw-rw---- 1 oracle asmadmin 118, 93 Apr 28 21:52 c3t600144F04DB4077D00000C29FF290900d0s5
    crw-rw---- 1 oracle asmadmin 118, 94 Apr 28 21:52 c3t600144F04DB4077D00000C29FF290900d0s6
    crw-rw---- 1 oracle asmadmin 118, 95 Apr 28 21:52 c3t600144F04DB4077D00000C29FF290900d0s7
    crw-rw---- 1 oracle asmadmin 118,104 Apr 28 21:52 c3t600144F04DB4077E00000C29FF290900d0s0
    crw-rw---- 1 oracle asmadmin 118,105 Apr 28 21:52 c3t600144F04DB4077E00000C29FF290900d0s1
    crw-rw---- 1 oracle asmadmin 118,106 Apr 28 21:52 c3t600144F04DB4077E00000C29FF290900d0s2
    crw-rw---- 1 oracle asmadmin 118,107 Apr 28 21:52 c3t600144F04DB4077E00000C29FF290900d0s3
    crw-rw---- 1 oracle asmadmin 118,108 Apr 28 21:52 c3t600144F04DB4077E00000C29FF290900d0s4
    crw-rw---- 1 oracle asmadmin 118,109 Apr 28 21:52 c3t600144F04DB4077E00000C29FF290900d0s5
    crw-rw---- 1 oracle asmadmin 118,110 Apr 28 21:52 c3t600144F04DB4077E00000C29FF290900d0s6
    crw-rw---- 1 oracle asmadmin 118,111 Apr 28 21:52 c3t600144F04DB4077E00000C29FF290900d0s7
    bash-3.00#
  • 6. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    gokhanatil Oracle ACE
    Currently Being Moderated
    According to the document, owner of these devices should "grid:asmadmin" instead of oracle asmadmin:

    # chown grid:asmadmin /dev/rdsk/cxtydzs6
    # chmod 660 /dev/rdsk/cxtydzs6

    Best Regards,

    Gokhan

    -------------------------------------------------------
    If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks
  • 7. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    854421 Explorer
    Currently Being Moderated
    It really depends on what user/group you used during the GI installation. Set the ownership to whatever user you installed GI with, and the group to whatever you set as the asm admin group during the CRS installation.
  • 8. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    Levi-Pereira Guru
    Currently Being Moderated
    Hi,

    Configuring disks to ASM on solaris should worry about some details.
    Solaris disks have an structure is called VTOC (Volume Table of Contents). All this information for the partitions and other data is contained in a special structure stored within the first 512 bytes of the disk, on the first cylinders. Actions like re-writting the VTOC will cause loosing the disk.
    Maybe you create a typical configuration, where slice 0 was formatted using the hole disk. So, during the disk discovery, it cause for missing disks or disks not been discovered.
    The reason seems to be that having partitions that start at cylinder 0, the complete partition is interpreted as the VTOC area which is not used as a regular partition of the disk.

    Check if you having partitions that start at cylinder 0.
    If yes modifying the partitions, starting few cylinders ahead (1 or 2 to avoid wasting space), will help ASM to discover the disk.

    You can use the note below:
    *ASM does not discover disk on Solaris platform [ID 368840.1]*
    or this doc:
    http://www.sun.com/bigadmin/content/submitted/format_utility.jsp
    or documentation:
    Solaris fdisk partitions must start at cylinder 1, not cylinder 0. If you create an fdisk partition, then you must label the disk before continuing.
    http://download.oracle.com/docs/cd/E11882_01/install.112/e17213/storage.htm#CACHGBAH

    Regards,
    Levi Pereira
  • 9. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    857371 Newbie
    Currently Being Moderated
    Hi Levi,

    Your tip worked. Actually i was trying to use whole disk which is partition 2 in solaris and have size 0----maxnumof cylinders according to disk size. Now I created t one extra paritition which starts from cylinder 1 to the desirable number on each disk and set the correct permissions for corresponding raw devices and than installer was able to see the all those disks.

    Thanks for your help.
  • 10. Re: disks not showup for ASM  while insalling  11gr2 on solaris 10 using gui
    Levi-Pereira Guru
    Currently Being Moderated
    Hi,
    If the thread has been answered, please close the thread as answered.

    Levi Pereira

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points