[FATAL] [INS-30508] Invalid ASM disks.

Dear Gurus
please help for troubleshoot the Invalid asm disk error on solaris
Oracle Grid 11.2.0.3.0
Solaris10 with EMC Powerpath Partition
-bash-3.2$ ./runInstaller -silent -responseFile /aaa/Oracle11g_SunSPARC_64bit/grid/response/grid_install.rsp
Starting Oracle Universal Installer...
Checking Temp space: must be greater than 180 MB.   Actual 90571 MB    Passed
Checking swap space: must be greater than 150 MB.   Actual 90667 MB    Passed
Preparing to launch Oracle Universal Installer from /tmp/OraInstall2013-09-15_12-17-47PM. Please wait ...-bash-3.2$ [FATAL] [INS-30508] Invalid ASM disks.
   CAUSE: The disks [/dev/rdsk/emcpower2a, /dev/rdsk/emcpower6a, /dev/rdsk/emcpower8a] were not valid.
   ACTION: Please choose or enter valid ASM disks.
A log of this session is currently saved as: /tmp/OraInstall2013-09-15_12-17-47PM/installActions2013-09-15_12-17-47PM.log. Oracle recommends that if you want to keep this log, you should move it from the temporary location to a more permanent location.

I'm grateful for your response and your time
We had resolve the issue our self
[/dev/rdsk/emcpower2a, /dev/rdsk/emcpower6a, /dev/rdsk/emcpower8a]
above partition by default take the slice 0
we had refer below link
ASM Create Partitions in Solaris and add them as disks in AS
In Sparc architecture, the solaris disk is subdivided into 8 slices.
Below is the common configuration of these eight slices:
slice 0: Holds files and directories that make up the operating
system.*
slice 1: Swap, Provides virtual memory, or swap space.
slice 2: Refers to the entire disk, by convention. The size of this
slice should not be changed.**
slice 3: /export, Holds alternative versions of the operating system.
slice 4: /export/swap. Provides virtual memory space for client
systems. ***
slice 5: /opt. Holds application software added to a system.
slice 6: /usr. Holds operating system commands--also known as
executables-- designed to be run by users.
slice 7: /home. Holds files created by users.
* Cannot be used as ASM disk. Using this slice causes disk corruption
and may render the disk as unusable.
** Should not be used as ASM Disk, as slice refers to the entire disk
(Including partition tables).
*** Is the recommended slice to be used for ASM disk.
as per asm recommendation we had used slice 4 the same
so we had detail diagnose and came to know that we have to use
[/dev/rdsk/emcpower2e, /dev/rdsk/emcpower6e, /dev/rdsk/emcpower8e]
here e refer the slice 4
we had use below changes in silent file and it's working fine
oracle.install.asm.diskGroup.disks=/dev/rdsk/emcpower2e,/dev/rdsk/emcpower6e,/dev/rdsk/emcpower8e
sample logs
INFO: Starting Output Reader Threads for process /tmp/OraInstall2013-09-17_05-03-21PM/ext/bin/kfod
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower2e oracle oinstall
INFO: The process /tmp/OraInstall2013-09-17_05-03-21PM/ext/bin/kfod exited with code 0
INFO: Waiting for output processor threads to exit.
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower6e oracle oinstall
INFO: Parsing 2560 CANDIDATE /dev/rdsk/emcpower8e oracle oinstall

Similar Messages

INS-30508 Invalid ASM disks on 11.2.0.3 OL 6.2 grid standalone install

New set of Dell servers R710s running OL 6.2 redhat compatible kernel
$ uname -a
Linux seoltpo-02 2.6.32-220.el6.x86_64
Connected to EMC VNX5500 and using powerpath 5.6.0. Not a rac environment ... doing 11.2.0.3 base install of grid infrastructure for a standalone server.
Not using ASMLIB.
Disk permissions are correct as grid install begins ...
brw-rw---- 1 grid oinstall 120, 704 Jul 26 21:18 emcpoweras
brw-rw---- 1 grid oinstall 120, 720 Jul 26 21:18 emcpowerat
brw-rw---- 1 grid oinstall 120, 736 Jul 26 21:18 emcpowerau
brw-rw---- 1 grid oinstall 120, 752 Jul 26 21:18 emcpowerav
brw-rw---- 1 grid oinstall 120, 768 Jul 26 21:18 emcpoweraw
brw-rw---- 1 grid oinstall 120, 784 Jul 26 21:18 emcpowerax
brw-rw---- 1 grid oinstall 120, 800 Jul 26 21:18 emcpoweray
brw-rw---- 1 grid oinstall 120, 816 Jul 26 21:18 emcpoweraz
GUI installer sees the powerpath LUNs after changing the Disk Discovery path ... for example ....
INFO: ... discoveryString = /dev/emcpower*
INFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpower*']
with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() { eval `/usr/bin/modulecmd bash $*`
}, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
INFO: Parsing 40960 CANDIDATE /dev/emcpoweras grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerat grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerau grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerav grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweraw grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpowerax grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweray grid oinstall
INFO: Parsing 40960 CANDIDATE /dev/emcpoweraz grid oinstall
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweru
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweru"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
*** Of course there are other LUNs not going to be part of ASM disk groups so it cannot read all of them initially.
Somehow after first looking at the disks and seeing them the first time the permissions are changed back on the disks over to root:root as soon as the GUI sees the disks.
You select the disks that you want in the GUI ( but the permissions have been changed already ) so click Next and wham INS 30508 ...
The Install log shows that kfod is apparently scanning the disks a bunch of time ... but before the error appears install log sees that permissions have changed.
Somehow actions caused from running the GUI are changing the permissions? Something is wrong somewhere ... powerpath ? 11.2.0.3 on this kernel version ? Seems very bizarre ...
NFO: Executing [tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod, nohdr=true, verbose=true, disks=all, status=true, op=disks, asm_diskstring='/dev/emcpoweras','/dev/emcpowerat','/dev/emcpowerau','/dev/emcpowerav','/dev/emcpoweraw','/dev/emcpowerax','/dev/emcpoweray','/dev/emcpoweraz']
with environment variables {XFILESEARCHPATH=/usr/dt/app-defaults/%L/Dt, LANG=en_US.UTF-8, DISPLAY=191.4.0.79:0, PWD=/u01/software_install/11_2_base/grid, _=/u01/software_install/11_2_base/grid/install/.oui, NLSPATH=/usr/dt/lib/nls/msg/%L/%N.cat, USER=grid, QTINC=/usr/lib64/qt-3.3/include, CLASSPATH=, G_BROKEN_FILENAMES=1, HOME=/home/grid, HOSTNAME=waoltpo-02, MODULESHOME=/usr/share/Modules, LESSOPEN=|/usr/bin/lesspipe.sh %s, LD_LIBRARY_PATH=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/../lib, ORACLE_HOME=/tmp/OraInstall2012-07-28_03-19-37AM/ext/bin, LOGNAME=grid, SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass, SHELL=/bin/bash, CVS_RSH=ssh, SHLVL=2, HISTCONTROL=ignoredups, KDE_IS_PRELINKED=1, MAIL=/var/spool/mail/grid, QTDIR=/usr/lib64/qt-3.3, JAVA_HOME=, QTLIB=/usr/lib64/qt-3.3/lib, MODULEPATH=/usr/share/Modules/modulefiles:/etc/modulefiles, LS_COLORS=, LC_ALL=, KDEDIRS=/usr, HISTSIZE=1000, module=() { eval `/usr/bin/modulecmd bash $*`
}, LOADEDMODULES=, TERM=vt220, PATH=/usr/bin:/usr/ccs/bin:/usr/lib64/qt-3.3/bin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/opt/dell/srvadmin/bin:/etc/opt/emcpower/bin:/home/grid/bin:/u01/software_install/11_2_base/grid/install}
INFO: Starting Output Reader Threads for process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraz
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraz"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: The process /tmp/OraInstall2012-07-28_03-19-37AM/ext/bin/kfod exited with code 0
INFO: Waiting for output processor threads to exit.
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweray
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweray"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerax
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerax"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweraw
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweraw"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerav
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerav"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerau
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerau"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpowerat
INFO: Parsing ORA-15025: could not open disk "/dev/emcpowerat"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Parsing KFOD-00311: Error scanning device /dev/emcpoweras
INFO: Parsing ORA-15025: could not open disk "/dev/emcpoweras"
INFO: Parsing Linux-x86_64 Error: 13: Permission denied
INFO: Parsing Additional information: 42
INFO: Parsing Additional information: 12247695
INFO: Parsing Additional information: 1598903119
INFO: Output processor threads exited.
SEVERE: [FATAL] [INS-30508] Invalid ASM disks.
CAUSE: The disks [dev/emcpoweras, /dev/emcpowerat, /dev/emcpowerau, /dev/emcpowerav, /dev/emcpoweraw, /dev/emcpowerax, /dev/emcpoweray, /dev/emcpoweraz] were not valid.
ACTION: Please choose or enter valid ASM disks.
INFO: Advice is ABORT
INFO: Adding ExitStatus INVALID_USER_INPUT to the exit status set
INFO: Completed validating state <CreateASMDiskGroup>
INFO: Terminating all background operations
INFO: Terminated all background operations
INFO: Transition aborted
INFO: Rolled back to state <CreateASMDiskGroup>
Is there some kind of configuration steps I am missing somewhere?
Yeah I know probably going to have to open an SR here but some of you guys around here are pretty sharp. Can I attach the whole install log here somehow?

Well I am not exactly opposed to udev rules for the powerpath devices ... not that I know what that is exactly ... if this can fix my problem.
I found an example or two from google ...
It looks like on my OL 6.2 system there is a difference in the files ( rules I guess ) under /etc/udev/rules.d
# *** OL 5.7 system below
$ ls -ltr
total 232
-rw-r--r-- 1 root root 1088 Jun 6 2007 60-pcmcia.rules
-rw-r--r-- 1 root root 58016 Jun 6 2007 60-libsane.rules
-rw-r--r-- 1 root root 2319 Jul 14 2008 bluetooth.rules
-rw-r--r-- 1 root root 114 Nov 5 2008 90-alsa.rules
-rw-r--r-- 1 root root 1823 Nov 5 2008 85-pcscd_ccid.rules
-rw-r--r-- 1 root root 316 Dec 8 2010 60-raw.rules
-rw-r--r-- 1 root root 82 Jan 13 2011 90-hal.rules
-rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
-rw-r--r-- 1 root root 292 May 11 2011 98-kexec.rules
-rw-r--r-- 1 root root 143 Jun 7 2011 60-net.rules
-rw-r--r-- 1 root root 331 Jun 9 2011 90-ib.rules
-rw-r--r-- 1 root root 992 Jul 8 2011 40-multipath.rules
-rw-r--r-- 1 root root 9366 Jul 22 2011 60-wacom.rules
-rw-r--r-- 1 root root 107 Jul 22 2011 95-pam-console.rules
-rw-r--r-- 1 root root 61 Jul 22 2011 90-dm.rules
-rw-r--r-- 1 root root 471 Jul 22 2011 51-hotplug.rules
-rw-r--r-- 1 root root 16732 Jul 22 2011 50-udev.rules
-rw-r--r-- 1 root root 515 Jul 22 2011 05-udev-early.rules
-rw-r--r-- 1 root root 175 Jul 22 2011 88-clock.rules
# *** OL 6.2 system below
$ ls -ltr
total 64
# *** OL 6.2 system below
$ ls -ltr
total 64
-rw-r--r--. 1 root root 1914 Apr 27 2010 85-pcscd_ccid.rules
-rw-r--r--. 1 root root 320 Jul 2 2010 90-alsa.rules
-rw-r--r--. 1 root root 1060 Jul 24 2010 60-pcmcia.rules
-rw-r--r--. 1 root root 1652 Nov 20 2010 60-fprint-autosuspend.rules
-rw-r--r--. 1 root root 2486 Dec 23 2010 97-bluetooth-serial.rules
-rw-r--r-- 1 root root 935 Mar 7 2011 95-dataeng-udev.rules
-rw-r--r-- 1 root root 77 Mar 25 2011 05-udev-pp.rules
-rw-r--r--. 1 root root 706 Mar 29 2011 56-hpmud_support.rules
-rw-r--r--. 1 root root 6858 Mar 29 2011 40-hplip.rules
-rw-r--r--. 1 root root 83 May 20 2011 90-hal.rules
-rw-r--r--. 1 root root 316 Oct 13 2011 60-raw.rules
-rw-r--r--. 1 root root 54 Dec 7 2011 99-fuse.rules
-rw-r--r--. 1 root root 292 Dec 7 2011 98-kexec.rules
-rw-r--r--. 1 root root 53 Dec 7 2011 91-drm-modeset.rules
-rw-r--r--. 1 root root 789 Jul 19 07:28 70-persistent-cd.rules
??? So no file 50-udev.rules ... in the 6.2 system ??? But tons of stuff in the 5.7 system ...

Cannot identify ASM disks

Hi All,
I am getting this error [FATAL] [INS-30508] Invalid ASM disks. The environment is as below
HP-UX Itanium
11.2.0.2
Volume group ownership:
drwxr-xr-x 2 root sys 8192 Apr 21 14:09 vg1_x_ks_r1_1
logical volume Ownership:
crw-rw---- 1 oracle dba 64 0x010001 Apr 21 14:09 rlv_x_kw_01
crw-rw---- 1 oracle dba 64 0x010002 Apr 21 14:09 rlv_x_kw_02
When i change the volume group owner to oracle, it works fine. I want to know why it should be oracle??
Please let me know if you have any references on this as i am a beginer and i want to learn in depth
Thanks,

Just as a sidenode:
for 11.2 you should set the ownerwship to be "installation user" of grid infrastructure and usergroup "ASM administrator", which you specify during GI installation.
For this reason documentation states
grid:asmadmin
However if in your case you are using oracle as the installation owner and dba as the asm administrator group, than this is o.k.
Sebastian

OUI will not detect ASM disks on EqualLogic PS6100

RHEL 5.5 w/ ASMLIB
Oracle 11g w/ Dell EqualLogic PS6100 iSCSI SAN
We've created the ASM disks and can see them before starting the OUI...
[root@dr-dbnode2 logs]# kpartx -l /dev/mapper/eql-8-cb2b76-0fde2e258-3ac70a955884f0dd-oracleasmdisk3
eql-8-cb2b76-0fde2e258-3ac70a955884f0dd-oracleasmdisk3p1 : 0 585954747 /dev/mapper/eql-8-cb2b76-0fde2e258-3ac70a955884f0dd-oracleasmdisk3 63
[root@dr-dbnode2 logs]# kpartx -l /dev/mapper/eql-8-cb2b76-0d8e2e258-55270a955854f0dd-oralceasmdisk2
eql-8-cb2b76-0d8e2e258-55270a955854f0dd-oralceasmdisk2p1 : 0 585954747 /dev/mapper/eql-8-cb2b76-0d8e2e258-55270a955854f0dd-oralceasmdisk2 63
[root@dr-dbnode2 logs]# kpartx -l /dev/mapper/eql-8-cb2b76-074e2e258-08670a9557f4f0dd-oracleasmdisk1
eql-8-cb2b76-074e2e258-08670a9557f4f0dd-oracleasmdisk1p1 : 0 585954747 /dev/mapper/eql-8-cb2b76-074e2e258-08670a9557f4f0dd-oracleasmdisk1 63
[root@dr-dbnode2 etc]# oracleasm listdisks
ASMDATA1
ASMDATA2
ASMDATA3
[root@dr-dbnode2 etc]# oracleasm querydisk -v -d -p ASMDATA1
Disk "ASMDATA1" is a valid ASM disk on device /dev/dm-2[253,2]
/dev/mapper/eql-8-cb2b76-074e2e258-08670a9557f4f0dd-oracleasmdisk1p1: LABEL="ASMDATA1" TYPE="oracleasm"
/dev/sdj1: LABEL="ASMDATA1" TYPE="oracleasm"
[root@dr-dbnode2 etc]# oracleasm querydisk -v -d -p ASMDATA2
Disk "ASMDATA2" is a valid ASM disk on device /dev/dm-8[253,8]
/dev/mapper/eql-8-cb2b76-0d8e2e258-55270a955854f0dd-oralceasmdisk2p1: LABEL="ASMDATA2" TYPE="oracleasm"
/dev/sdf1: LABEL="ASMDATA2" TYPE="oracleasm"
[root@dr-dbnode2 etc]# oracleasm querydisk -v -d -p ASMDATA3
Disk "ASMDATA3" is a valid ASM disk on device /dev/dm-4[253,4]
/dev/mapper/eql-8-cb2b76-0fde2e258-3ac70a955884f0dd-oracleasmdisk3p1: LABEL="ASMDATA3" TYPE="oracleasm"
/dev/sdg1: LABEL="ASMDATA3" TYPE="oracleasm"
[grid@dr-dbnode2 ext]$ kfod asm_diskstring='/dev/oracleasm/disks/*' nohdr=true verbose=true disks=all status=true op=disks
286110 CANDIDATE /dev/oracleasm/disks/ASMDATA1 grid asmadmin
286110 CANDIDATE /dev/oracleasm/disks/ASMDATA2 grid asmadmin
286110 CANDIDATE /dev/oracleasm/disks/ASMDATA3 grid asmadmin
When we run the OUI we get to the 'Add Disks' screen and there are no disks listed at all...
So we tried to run with a -silent install and -force with the disks in our rsp file and the action log shows the following...
[root@dr-dbnode2 logs]# cat installActions2012-01-12_05-06-51PM.log
INFO: Waiting for completion of background operations
INFO: Completed background operations
INFO: Executing action at state CreateASMDiskGroup
INFO: Completed executing action at state <CreateASMDiskGroup>
INFO: Waiting for completion of background operations
INFO: Completed background operations
INFO: Moved to state <CreateASMDiskGroup>
INFO: Waiting for completion of background operations
INFO: Completed background operations
INFO: Validating state <CreateASMDiskGroup>
INFO: inventory location is/opt/oracle/app/oraInventory
INFO: inventory location is/opt/oracle/app/oraInventory
INFO: inventory location is/opt/oracle/app/oraInventory
INFO: Is CRS Installed false
INFO: while getting CSS versionjava.lang.Exception: Unable to find the specified Oracle Home.
WARNING: KFOD not found at
INFO: inventory location is/opt/oracle/app/oraInventory
WARNING: KFOD not found at
FINE: oracle.install.commons.util.Resource:Can't find resource for bundle oracle.install.asm.resource.ASMErrorResID, key oracle.install.asm.bean.ASMInputValidationErrorCode.hint
SEVERE: [FATAL] [INS-30508] Invalid ASM disks.
CAUSE: The disks [dev/oracleasm/disks/ASMDATA1, /dev/oracleasm/disks/ASMDATA2, /dev/oracleasm/disks/ASMDATA3] were not valid.
ACTION: Please choose or enter valid ASM disks.
INFO: Advice is ABORT
INFO: Adding ExitStatus INVALID_USER_INPUT to the exit status set
INFO: Completed validating state <CreateASMDiskGroup>
INFO: Terminating all background operations
INFO: Terminated all background operations
FINE: oracle.install.commons.util.Resource:Can't find resource for bundle oracle.install.commons.util.resource.ErrorCodeResourceBundle, key oracle.install.commons.util.exception.CommonErrorCode.hint
INFO: Finding the most appropriate exit status for the current application
INFO: Exit Status is -2
INFO: Shutdown Oracle Grid Infrastructure
INFO: Unloading Setup Driver
Been stuck here for a couple days...
My current direction is looking at the "WARNING: KFOD not found at" message...
kfod does exist in the /tmp/OraInstall2012-01-12_04-40-31PM/ext/bin/kfod folder while the installation is running...so I'm not sure what to make of it.
Let me know if anyone can shed some light here...
Thanks in advance,
Colby

We managed to figure it out...
It turns out that a previously failed -silent run of the OUI had left some Oracle files hanging about. The OUI not showing the ASM disks because they were associated to the failed installation. After removing 'ALL' the files from the failed installation and a reboot we were able to get through the full install successfully.
Make sure you fully clean up after a failed install...
cs

Reinstalling Oracle 11gR2 RAC Grid Problem - ASM Disks Group

Folks,
Hello.
I am installing Oracle 11gR2 RAC using 2 Virtual Machines (rac1 and rac2 whose OS are Oracle Linux 5.6) in VMPlayer.
I have been installing Grid Infrastructure using runInstaller in the first VM rac1 from step 1 to step 9 of 10.
On the step 9 of 10 in the Wizard, accidentally, I touch the Mouse, and the Wizard is gone.
The directory for installing Grid in the 2 VMs is the same: /u01
In order to make sure everything is correct, I delete entire directory /u01 in the 2 VMs and install Grid in rac1 again.
I have understood it's not the right way to delete /u01. The right way is to follow the tutorial
http://docs.oracle.com/cd/E11882_01/install.112/e22489/rem_orcl.htm#CBHEFHAC
But I have deleted /u01 and need to fix one by one. I install Grid again and get the error message on step 5 of 9 as follows:
[INS - 30516] Please specify unique disk groups.
[INS-3050] Empty ASM disk group.
Cause - Installer has detected the disk group name provided already exists on the system.
Action - Specify different disk group.
In Wizard, the previous Disk Group name is "DATA" and its Candidate disks (5 ASMDISKs) are gone. I try to use a different name "DATA2", but no ASMDISKs come up under "Candidate disks". For "ALL Disks", all ASMDISKs cannot be selected.
I want to use the same ASM disk group "DATA" and don't want to create a new disk group.
My question is:
How to have the previous ASM disks and its group "DATA" come up under "Candidate Disks" so that can use it again ?
Thanks.

Hi, in case this helps anyone else. I got this INS-30516 error too was stumped for little while. I have 2 x 2-node RAC which are hitting same SAN. The first-built RAC has a DATA diskgroup. When went to build second RAC on new ASM disk new DIskgroup (but same diskgroup name DATA) got INS-30516 about diskgroup name already in use etc. Finally figured out all that was required was to restrict diskstring using button in installer to only retrieve the LUNS for this RAC (this was quick and dirty - all LUNS for both RAC being presented to both RAC). Once diskstring only searched for the LUNS required for this RAC only, e.g.
ORCL:DATA_P* (for DATA_PD and FRA_PD)
the error went away.
I also have DATA_DR and FRA_DR presenting to both RAC. Apparently it scans the header and if it finds a diskgroup name that is already in use based on the diskstring scan it will not allow reuse of the diskgroup name since it has no way of knowing that the other ASM disks are for a different RAC.
HTH

Empty ASM disk group [INS-30507]

Hello Good people!
I have SUSE Linux Enterprise Server 11 (x86_64) and grid infrastucture 11.2.
I have installed ASMlib, and made
/etc/init.d/oracleasm status
Checking if ASM is loaded: yes
Checking if /dev/oracleasm is mounted: yes
/etc/init.d/oracleasm querydisk ASMDISK1
Disk "ASMDISK1" is a valid ASM disk
Then i am trying install grid infrastucture, on step CONFIGURE ORACLE GRID nfrastucture for Standalone Server,
i can`t find my Disk "ASMDISK1"
Why grid infrastucture can`t find my Disk "ASMDISK1"?

ssolbach,
i am trying to deletedisk ASMDISK1 using root.
etc/init.d/oracleasm configure
Configuring the Oracle ASM library driver.
Default user to own the driver interface [oracle]:
Default group to own the driver interface [oinstall]:
Start Oracle ASM library driver on boot (y/n) [y]:
Scan for Oracle ASM disks on boot (y/n) [y]:
Writing Oracle ASM library driver configuration: done
Initializing the Oracle ASMLib driver: done
Scanning the system for Oracle ASMLib disks: done
/etc/init.d/oracleasm status
Checking if ASM is loaded: yes
Checking if /dev/oracleasm is mounted: yes
*******************************************************************

Error while creating asm disk group

i am trying to convert my database SRAVAN as an ASM instance.
so do i need to set ORACLE_SID=+ASM???? r else it wil be SRAVAN??
I WAS ENDED UP WITH FOLLOWING ERRORS WHILE CREATING DISK GROUP.
guyz please do help me
SQL> CREATE DISKGROUP dgroup1
2 NORMAL REDUNDANCY
3 FAILGROUP ctlr1
4 DISK '/u04/app/oracle/product/asmdisks/disk1'
5 FAILGROUP ctlr2
6 DISK '/u04/app/oracle/product/asmdisks/disk2';
CREATE DISKGROUP dgroup1
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk2' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk2'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
ORA-15031: disk specification '/u04/app/oracle/product/asmdisks/disk1' matches
no disks
ORA-15025: could not open disk '/u04/app/oracle/product/asmdisks/disk1'
ORA-15059: invalid device type for ASM disk
Linux Error: 32768: Unknown system error
Additional information: 42
Additional information: -1073785968
[oracle@sierra200 dbs]$ cd /u04/app/oracle/product/asmdisks
[oracle@sierra200 asmdisks]$ ls -ltr
total 205008
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:42 disk1
-rwxrwxrwx 1 oracle oinstall 104857600 Jul 27 11:47 disk2
Thanks & Regards
Sravan Dalavai

Looks like you are asking ASM to use plain files. Have you used the Device Loopback (losetup) a d made the emulate raw devices?
http://www.idevelopment.info/data/Oracle/DBA_tips/Automatic_Storage_Management/ASM_20.shtml

Creation of ASM disk for OUI

I need to install a Oracle Database in order to install Enterprise Manager Cloud Control 12c.
Need the database to use a ASM disk.
I used the following command to create the disk, per the Oracle Database Installation Guide.
#/usr/sbin/oracleasm createdisk DISK1 /dev/sdd1
#oracleasm listdisks
DISK1
However, when running the OUI for Oracle Database 12c (understand 11.2.0.3 is certified for Cloud Control), step 7
errors INS-30517 when attempting to select "Oracle Automatic Storage Management" for "Storage type".
Researched the error at this location but no cause or action was provided.
http://docs.oracle.com/cd/E16655_01/server.121/e26079/common_errormessages.htm
INS-30517: Automatic Storage Management software is not configured on this system.
The database install guide states that I need to ensure the "disk discovery string" is set the "ORCL:*" or is left empy ("") so the installer discovers these disks.
It doesn't show how to confirm or change the settings.
At this point I'm at a stopping point.

All ASMLib installations require the oracleasmlib and oracleasm-support packages. The oracleasm kernel driver is included in the Oracle UEK kernel. Perhaps you are missing the oracleasmlib package. You can download it from:
Oracle Linux: Oracle ASMLib | Oracle Technology Network
Oracleasmlib is not necessary for ASM to work, but it contains software necessary for Linux oracleasm, including the /usr/sbin/oracleasm-discover utility, which the Oracle installer used in the previous 11g version to detect available ASM volumes.

Shrinking ASM disk

I just tried to resize an ASM disk and although the feedback was 'successful', there doesn't appear to have been any change.
I was attempting to shrink disk DATA_0001 from 200G to 100G. Am I missing something obvious?
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
          0                      /dev/iscsi/rman11                   20489          0          0
          0                      /dev/iscsi/rmanB11                 102398          0          0
          0                      /dev/iscsi/rman1                    20490          0          0
          0                      /dev/iscsi/vote3                      300          0          0
          0                      /dev/iscsi/vote1                      300          0          0
          0                      /dev/iscsi/rmanP11                 204805          0          0
          0                      /dev/iscsi/vote2                      300          0          0
          0                      /dev/iscsi/rmanP1                  204810          0          0
          0                      /dev/iscsi/rmanB1                  102405          0          0
          1 DATA_0000            /dev/iscsi/db1                      10245      10245      10109
          2 FRA_0000             /dev/iscsi/flshbk1                  20490      20490      20465
GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
          2 FRA_0001             /dev/iscsi/flshbkR1                409605     409605     409262
          1 DATA_0001            /dev/iscsi/dbR1                    204810     204810     202297
13 rows selected.
SQL> alter diskgroup data resize disk 'data_0001' size 100g;
Diskgroup altered.
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk;
GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
          0                      /dev/iscsi/rman11                   20489          0          0
          0                      /dev/iscsi/rmanB11                 102398          0          0
          0                      /dev/iscsi/rman1                    20490          0          0
          0                      /dev/iscsi/vote3                      300          0          0
          0                      /dev/iscsi/vote1                      300          0          0
          0                      /dev/iscsi/rmanP11                 204805          0          0
          0                      /dev/iscsi/vote2                      300          0          0
          0                      /dev/iscsi/rmanP1                  204810          0          0
          0                      /dev/iscsi/rmanB1                  102405          0          0
          1 DATA_0000            /dev/iscsi/db1                      10245      10245      10004
          2 FRA_0000             /dev/iscsi/flshbk1                  20490      20490      20465
GROUP_NUMBER NAME                 PATH                                OS_MB   TOTAL_MB    FREE_MB
          2 FRA_0001             /dev/iscsi/flshbkR1                409605     409605     409262
          1 DATA_0001            /dev/iscsi/dbR1                    204810     204810     202402
13 rows selected.The free_mb seems to have increased, but otherwise I can't see the effect of my change. Maybe I'm looking in the wrong place??
I tried restarting the ASM instance but it made no difference.
After resizing the disk in ASM I shrunk the disk volume in our storage array. ASM was of course down at the time.
When I attempted to restart ASM I saw this ...
SQL> startup
ASM instance started
Total System Global Area 283930624 bytes
Fixed Size                  2158992 bytes
Variable Size             256605808 bytes
ASM Cache                  25165824 bytes
ORA-15032: not all alterations performed
ORA-15036: disk '/dev/iscsi/dbR1' is truncatedNone of my diskgroups are mounted ...
SQL> select group_number, name, state from v$asm_diskgroup;
GROUP_NUMBER NAME            STATE
          0 DATA            DISMOUNTED
          0 FRA             DISMOUNTEDHere's the messages from the ASM instance alert log ...
SQL> ALTER DISKGROUP ALL MOUNT
NOTE: cache registered group DATA number=1 incarn=0x5f5e3343
NOTE: cache began mount (not first) of group DATA number=1 incarn=0x5f5e3343
NOTE: cache registered group FRA number=2 incarn=0x5f5e3344
NOTE: cache began mount (not first) of group FRA number=2 incarn=0x5f5e3344
WARNING::ASMLIB library not found. See trace file for details.
NOTE: Assigning number (1,0) to disk (/dev/iscsi/db1)
NOTE: cache dismounting group 1/0x5F5E3343 (DATA)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 1/0x5F5E3343 (DATA)
NOTE: cache ending mount (fail) of group DATA number=1 incarn=0x5f5e3343
kfdp_dismount(): 1
kfdp_dismountBg(): 1
NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
ERROR: diskgroup DATA was not mounted
NOTE: Assigning number (2,1) to disk (/dev/iscsi/flshbkR1)
NOTE: Assigning number (2,0) to disk (/dev/iscsi/flshbk1)
NOTE: cache dismounting group 2/0x5F5E3344 (FRA)
NOTE: dbwr not being msg'd to dismount
NOTE: lgwr not being msg'd to dismount
NOTE: cache dismounted group 2/0x5F5E3344 (FRA)
NOTE: cache ending mount (fail) of group FRA number=2
incarn=0x5f5e3344
kfdp_dismount(): 2
kfdp_dismountBg(): 2
NOTE: De-assigning number (2,0) from disk (/dev/iscsi/flshbk1)
NOTE: De-assigning number (2,1) from disk (/dev/iscsi/flshbkR1)
ERROR: diskgroup FRA was not mounted
ORA-15032: not all alterations performed
ORA-15036: disk '/dev/iscsi/dbR1' is truncated
ERROR: ALTER DISKGROUP ALL MOUNTAny clues?
Thanks,
Steve

Thanks Markus. I changed the size of the volume back to the original and was able to restart the ASM instances on both nodes. I confirmed it saw the size as the original 200G.
I then shut down ASM on the second node and issued the alter on the first node. Here's what happened ...
SQL> select group_number, name, path, os_mb, total_mb, free_mb from v$asm_disk order by name;
GROUP_NUMBER NAME       PATH                                OS_MB   TOTAL_MB    FREE_MB
           1 DATA_0000 /dev/iscsi/db1                      10245      10245      10004
           1 DATA_0001 /dev/iscsi/dbR1                    204810     204810     202402
           2 FRA_0000   /dev/iscsi/flshbk1                  20490      20490      20465
           2 FRA_0001   /dev/iscsi/flshbkR1                409605     409605     409262
           0            /dev/iscsi/rman1                    20490          0          0
           0            /dev/iscsi/rmanP1                  204810          0          0
           0            /dev/iscsi/rmanB1                  102405          0          0
           0            /dev/iscsi/rmanP11                 204805          0          0
           0            /dev/iscsi/rmanB11                 102398          0          0
           0            /dev/iscsi/rman11                   20489          0          0
10 rows selected.
SQL> alter diskgroup data resize disk 'data_0001' size 100g;
alter diskgroup data resize disk 'data_0001' size 100g
ERROR at line 1:
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15066: offlining disk "DATA_0001" may result in a data lossHere's the details from the alert log ...
SQL> alter diskgroup data resize disk 'data_0001' size 100g
NOTE: requesting all-instance membership refresh for group=1
WARNING: cache read a corrupted block gn=1 dsk=1 blk=257 from disk 1
NOTE: a corrupted block was dumped to /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_5295.trc
ERROR: cache failed to read gn=1 dsk=1 blk=257 from disk(s): 1
ORA-15196: invalid ASM block header [kfc.c:9133] [endian_kfbh] [2147483649] [257] [0 != 1]
System State dumped to trace file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_ora_5295.trc
NOTE: cache initiating offline of disk 1 group 1
WARNING: initiating offline of disk 1.3688884620 (DATA_0001) with mask 0x7e
NOTE: initiating PST update: grp = 1, dsk = 1, mode = 0x15
kfdp_updateDsk(): 14
Thu May 07 15:45:38 2009
kfdp_updateDskBg(): 14
ERROR: too many offline disks in PST (grp 1)
Thu May 07 15:45:38 2009
NOTE: halting all I/Os to diskgroup DATA
Thu May 07 15:45:38 2009
SQL> alter diskgroup DATA dismount force
NOTE: active pin found: 0x0x6ddf6060
NOTE: active pin found: 0x0x6ddf6168
ERROR: ORA-15130 signalled during resize of diskgroup DATA
Thu May 07 15:45:38 2009
NOTE: membership refresh pending for group 1/0xdc0f1999 (DATA)
kfdp_query(): 15
kfdp_queryBg(): 15
SUCCESS: refreshed membership for 1/0xdc0f1999 (DATA)
ERROR: ORA-15130 thrown in RBAL for group number 1
Errors in file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5202.trc:
ORA-15130: diskgroup "DATA" is being dismounted
Errors in file /var/oracle/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_5202.trc:
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15032: not all alterations performed
ORA-15130: diskgroup "DATA" is being dismounted
ORA-15066: offlining disk "DATA_0001" may result in a data loss
ERROR: alter diskgroup data resize disk 'data_0001' size 100g
NOTE: cache dismounting group 1/0xDC0F1999 (DATA)
NOTE: dbwr not being msg'd to dismount
Thu May 07 15:45:41 2009
Dirty detach reconfiguration started (old inc 6, new inc 6)
List of nodes:
0
Global Resource Directory partially frozen for dirty detach
* dirty detach - domain 1 invalid = TRUE
10 GCS resources traversed, 0 cancelled
Dirty Detach Reconfiguration complete
Thu May 07 15:45:41 2009
freeing rdom 1
Thu May 07 15:45:41 2009
WARNING: dirty detached from domain 1
NOTE: cache dismounted group 1/0xDC0F1999 (DATA)
kfdp_dismount(): 16
kfdp_dismountBg(): 16
NOTE: De-assigning number (1,0) from disk (/dev/iscsi/db1)
NOTE: De-assigning number (1,1) from disk (/dev/iscsi/dbR1)
SUCCESS: diskgroup DATA was dismounted
SUCCESS: alter diskgroup DATA dismount force
ERROR: PST-initiated MANDATORY DISMOUNT of group DATA
Thu May 07 15:46:06 2009
SQL> alter diskgroup data resize disk 'data_0001' size 100g
ORA-15032: not all alterations performed
ORA-15001: diskgroup "DATA" does not exist or is not mounted
ERROR: alter diskgroup data resize disk 'data_0001' size 100gLooks like my earlier attempt has indeed screwed up something so even though the instances start OK and mount the diskgroup, I think there's a fair chance something would go splat sooner rather than later.
As this is a test database, I think I'll cut my losses and rebuild the diskgroup then restore it from backup. I'm assuming the effort involved in correcting the corruption will be greater than rebuilding and restoring.
Do you agree with this?
Then I'll try again and hopefully get it right.
Thanks for your help!!!
Steve

Using udev devices for ASM disk on Linux

Hello all,
I need details related to using udev devices as ASM disk on Linux.
What I want to know is, once i get the list of ASM Disks that are used to create the DiskGroups, based on the path of the Disk (whether /dev/sdj or /dev/dm-3 or /dev/asm_udev_device, /dev/vx/<vxvm-volume>, /dev/<lvm-volume>) how do i get to know if the device type is a udev device?
I want to know an automated process, so that i can script it out to separate out each device easily.
Please let me know if anyone has expertise on using udev devices with Oracle ASM.
I have referred the link but no much details available http://www.oracle.com/technology/products/database/asm/pdf/device-mapper-udev-crs-asm%20rh4.pdf
Further, the behavior of udevinfo command is very different across version of Linux. From Suse 10 onwards, udevadm has to be used instead.
Its confusing to me.
Please help.
~Sumeet.

My installation, ASM On SI
S.O HP-UIx
Disk internal, not SAN
Internal disk configuration for Oracle.
PV Name /dev/dsk/c11t0d0
PV Name /dev/dsk/c11t1d0
PV Name /dev/dsk/c11t2d0
PV Name /dev/dsk/c11t3d0
PV Name /dev/dsk/c11t4d0
PV Name /dev/dsk/c11t6d0
Vg:
/dev/vgora
Lv
/dev/vgora/lvu01 <-- Oracle Bin mounted /u00
/dev/vgora/lvu02 <-- External Archive /u02
In /dev/vgora
brw-r----- 1 root sys 64 0x010001 Mar 8 14:42 lvu01
brw-r----- 1 root sys 64 0x010002 Mar 8 16:15 lvu02
brwxrwxr-x 1 root sys 64 0x010003 Mar 19 14:19 lvasm01
brwxrwxr-x 1 root sys 64 0x010004 Mar 19 14:20 lvasm02
brwxrwxr-x 1 root sys 64 0x010005 Mar 19 14:20 lvasm03
brwxrwxr-x 1 root sys 64 0x010006 Mar 19 14:20 lvasm04
brwxrwxr-x 1 root sys 64 0x010007 Mar 19 14:20 lvasm05
brwxrwxr-x 1 root sys 64 0x010008 Mar 19 14:20 lvasm06
brwxrwxr-x 1 root sys 64 0x010009 Mar 19 14:20 lvasm07
brwxrwxr-x 1 root sys 64 0x01000a Mar 19 14:20 lvasm08
brwxrwxr-x 1 root sys 64 0x01000b Mar 19 14:20 lvasm09
brwxrwxr-x 1 root sys 64 0x01000c Mar 19 14:21 lvasm10
crw-r----- 1 root sys 64 0x010001 Mar 8 14:42 rlvu01
crw-r----- 1 root sys 64 0x010002 Mar 8 16:15 rlvu02
crw-r--r-- 1 root sys 64 0x010000 Mar 8 14:19 group
FOR ASM
crw-rw---- 1 oracle dba 64 0x010003 Mar 19 14:19 rlvasm01
crw-rw---- 1 oracle dba 64 0x010004 Mar 19 14:20 rlvasm02
crw-rw---- 1 oracle dba 64 0x010005 Mar 19 14:20 rlvasm03
crw-rw---- 1 oracle dba 64 0x010006 Mar 19 14:20 rlvasm04
crw-rw---- 1 oracle dba 64 0x010007 Mar 19 14:20 rlvasm05
crw-rw---- 1 oracle dba 64 0x010008 Mar 19 14:20 rlvasm06
crw-rw---- 1 oracle dba 64 0x010009 Mar 19 14:20 rlvasm07
crw-rw---- 1 oracle dba 64 0x01000a Mar 19 14:20 rlvasm08
crw-rw---- 1 oracle dba 64 0x01000b Mar 19 14:20 rlvasm09
crw-rw---- 1 oracle dba 64 0x01000c Mar 19 14:21 rlvasm10
And the problem is:
When i run dbca for create diskgroup, that not recognize the disk.
I will set asm_diskstring with the correctly path.
I try to create a diskgroup from command line, but i see this error.
SQL> create diskgroup DG_DATA_01 external redundancy DISK '/dev/vgora/rlvasm01' ;
create diskgroup DG_DATA_01 external redundancy DISK '/dev/vgora/rlvasm01'
ERROR at line 1:
ORA-15018: diskgroup cannot be created
ORA-15031: disk specification '/dev/vgora/rlvasm01' matches no disks
ORA-15025: could not open disk '/dev/vgora/rlvasm01'
ORA-15059: invalid device type for ASM disk
Additional information: 255

[FATAL] [INS-30001] The ASMSNMP password is empty.

I'm receiving the following error during an 11.2.0.3 install on RedHat 5.5. There is no value to pass a password for ASMSNMP in the response file.
INFO: Validating state <ASMInstanceCredentialsGUI>
SEVERE: [FATAL] [INS-30001] The ASMSNMP password is empty.
CAUSE: The ASMSNMP password should not be empty.
ACTION: Provide a non-empty password.
INFO: Advice is ABORT
INFO: Adding ExitStatus INVALID_USER_INPUT to the exit status set
INFO: Completed validating state <ASMInstanceCredentialsGUI>
Any help would be appreciated. Thank you

try this
# oracle.install.asm.monitorPassword=password
oracle.install.asm.monitorPassword=

ASM disk header corruption

Hi.
If the header of an asm disk is corrupted, then I drop the corrupted disk and re-add, will the data in the disk lost?
Thanks.

fschk requires the file system driver to support repairing the file system - in other words, fschk itself does not do the fixing (it does not understand the underlying file system format). Quoting manpage, "+fsck is simply a front-end for the various file system checkers+". So if there is not a fsck.asmcfs (or similar), fsck can not do anything ito fixing invalid structures on that file system.
As for the kernel keeping copies of a file system's superblock - not sure why it would be doing that for ASM. It does not manage it as a file system or service I/O to it (the ASM devices are opened using the O_DIRECT flag).

ORA-15196: invalid ASM block header

asm alert shows:
WARNNING: cache read a corrupted block group=1(CRSDG) dsk=0 blk=2 from disk 0(CRSVOL)
Errors in file /u01/app/11.2.0/grid/log/diag/asm/+asm/+ASM1/trace/+ASM1_rbal_16585.trc:
ORA-15196: invalid ASM block header [kfc.c:25578] [endian_kfbh] [2147483648] [2] [0 != 1]
ORA-15196: invalid ASM block header [kfc.c:25427] [endian_kfbh] [2147483648] [2] [0 != 1]
Here are my challenges to the answer providers and I am going to number my questions. You are welcome to answer any question listed below, just please quota my question number first. Thanks.
1) "cache read a corrupted block group" , what exactly is the "cache" here?
2) "group=1(CRSDG) dsk=0 blk=2 from disk 0(CRSVOL)" we know that ASM is stored in AUs, here only gives dsk=0, blk=2, but without knowing the AU number, how can I use kfed to read the proper block?
3) "kfc.c:25578" what is kfc.c? I can find explanation about kfbh.<>, kfdhdb.<>, but have no clue about what kfc.c is.
4) "[endian_kfbh] [2147483648] [2] [0 != 1]" I know endian_kfbh is about the platform's Endian, but what is 2147483648 referring to here?
5) "[endian_kfbh] [2147483648] [2] [0 != 1]" I am guessing [2] refers to block number 2, is this correct?
6) overall, is all it is trying to tell me is "the plaform should be in small endian (1), but now it is marked as big endian(2) at some header place"?
7) of course, I would appreciate your solutions very much. you solution is ...?
8) Is there any good article reference about these stuff?
lisingt every single questions of mine is my favorite seeking help style. Doing this help learn better. I am expecting your contributions.
Thanks in advance!

1) "cache read a corrupted block group" , what exactly is the "cache" here?
I think I need not ask this question. Cache here simply means reading the block from disk to the cache.
However, questions 2 ~ 7 are still valid.

FATAL [INS-41311] One or more Oracle Cluster Registry (OCR) locations spec

I'm installing 11.2.0.3 Grid Infrastructure on Red Hat 5.7. I'm receiving the following error that I pasted below. There isn't a whole lot of information regarding it. It seems that the install sees an existing CRS install, but the NFS volumes are empty. This is a fresh install. I ran cleanup, but there's nothing to remove. Any help or insight will be appreciated.
Thank you
INFO: Checking path: /u02/udev/devices/ocr1
INFO: Checking path: /u03/udev/devices/ocr2
INFO: Checking path: /u04/udev/devices/ocr3
INFO: Validating for writability
INFO: Validating for valid OCR locations
INFO: Validating OCR locations.
INFO: validating if it is an existing directory.
INFO: Validating for free space
INFO: PATH has :==>/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/lib/amd64/server:/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/lib/amd64:/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/../lib/amd64
INFO: PATH has :==>/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/lib/amd64/server:/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/lib/amd64:/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/../lib/amd64
INFO: PATH has :==>/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/lib/amd64/server:/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/lib/amd64:/tmp/OraInstall2012-03-31_12-30-37AM/jdk/jre/../lib/amd64
SEVERE: [FATAL] [INS-41311] One or more Oracle Cluster Registry (OCR) locations specified are in an existing OCR directory.
CAUSE: One or more Oracle Cluster Registry (OCR) locations specified were in directories with existing OCR files.
ACTION: Specify locations for Oracle Cluster Registry that are not in use.
INFO: Advice is ABORT

user12006502 wrote:
These are NFS mounts off of NetApp NAS. They are volumes that don't contain anything else but an empty .snapshot subdirectory. This is my first NFS RAC implementation. We followed NetApps best practices for the NFS mount options as well as the export options on the NAS. I'm sort of lost as to what the problem could be. Ran the installer with debug and strace, but I'm still not getting any insight into the issue. Thanks for trying to help.
My first reaction to the failed CRS install is to clean it up. I ran the cleanup steps, but the installer didn't get far enough to generate any files.
I'm using the following NFS mount options:
rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,vers=3,timeo=600,noac,suidUse rw,bg,hard,nointr,rsize=32768,wsize=32768,tcp,noac,actimeo=0,vers=3,timeo=600 for Mount points for CRS voting disk and OCR
Doc id - Mount Options for Oracle files when used with NFS on NAS devices [ID 359515.1]

Asm disk removed taking too much time to boot

hi
a local machine is configured with ASM by oracleasm with a total disk.As it was a training purpose so i have removed the disk eg /dev/sdb bluntly ie. just removing it from box.now i tried fsck -c -c -f /dev/ in rescue mode its didnot worked even not mounting the /mnt/sysimage.It claims for ext2fs error and mounting the fs etc.
Then after lots of days has gone.i fed up with this issues and reinstalled OS.
but my question is what exactly to do?obviously re-installation is not the exact way to do.
regards

If the +/dev/sdb+ was an ASM disk, then it should not impact the o/s when it is removed. ASM instance itself will fail with an error saying something like it was not able to mount the disk group.
If your system failed to boot correctly after this disk was removed, then +/dev/sdb+ contained more than just ASM data.
We dynamically add and remove ASM (multipath'ed) disks via kpartx - while o/s is running. No reboot. No problems.
I fail to see how a ASM disk could cause the type of problems you describe - unless it was more than just a disk used by ASM alone.

[FATAL] [INS-30508] Invalid ASM disks.

Similar Messages

Maybe you are looking for