RE: CVU reporting error when checking for ASM storage

From: Hameed, Amir <>
Date: Fri, 16 Jan 2015 20:13:52 +0000
Message-ID: <>

Thanks Mladen.
I am following Red Hat's note titled "How to create Oracle ASM disks using DM Multipath devices in Red Hat Enterprise Linux?" to define UDEV rules on block devices. What Tim has documented uses SCSI device names in the rule instead of Device Mapper. This is the first time I am doing ASM. I am going to carry on with the installation to see how it goes and it might be an issue with CVU. This is what is listed in Red Hat's document.
  1. udevadm info --query=all --name=/dev/mapper/mpathN |grep -i DM_UUID
  2. ACTION=="add|change", ENV{DM_UUID}=="mpath-<UUID>", SYMLINK+="oracleasm/asm01", GROUP="dba", OWNER="oracle", MODE="0660"

From: [] On Behalf Of Mladen Gogala Sent: Friday, January 16, 2015 2:47 PM
Subject: Re: CVU reporting error when checking for ASM storage

Amir, you cannot just add Linux block devices to ASM. You need to "scsify" them. The best brief description is on Tim Hall's ORACLE-BASE site:

On 01/16/2015 02:00 PM, Hameed, Amir wrote: Hi,
I am installing Oracle Grid on RHEL 6.5. When the Prerequisite Checks phase of OUI, it reported PRVF -5150 on ASM disks. When run CVU on the ASM disks, it reports an error as shown below. Below is an out from CVU with debugging enabled when it was run for one RAC node only: CV_TRACELOC=/tmp/cvutrace
./ comp ssa -n <node-name> -s /dev/oracleasm/grid/asmgrid02

Verifying shared storage accessibility

Checking shared storage accessibility...

ERROR: /dev/oracleasm/grid/asmgrid02
Storage operation failed

Shared storage check failed on nodes "usa0300lx566"

Verification of shared storage accessibility was unsuccessful on all the specified nodes.

The CVU trace file shows the following error: OUTPUT><CV_ERR><SLOS_LOC>CVU00101</SLOS_LOC><SLOS_OP></SLOS_OP><SLOS_CAT>OTHEROS</SLOS_CAT><SLOS_OTHERINFO>Cannot locate disk for '/dev/dm-50'</SLOS_OTHERINFO></CV_ERR><CV_VRES>0</CV_VRES><CV_LOG>Exectask:getstorage success.</CV_LOG><CV_CMDLOG><CV_INITCMD>/tmp/CVU_12. -getstorage /dev/oracleasm/grid/asmgrid02 </CV_INITCMD><CV_CMD>realpath /dev/oracleasm/grid/asmgrid02</CV_CMD><CV_CMDOUT> /dev/dm-50</CV_CMDOUT><CV_CMDSTAT>0</CV_CMDSTAT><CV_CMD>stat /dev/dm-50</CV_CMD><CV_CMDOUT> stat.st_mode:61B0</CV_CMDOUT><CV_CMDSTAT>0</CV_CMDSTAT><CV_CMD>fopen /proc/partitions</CV_CMD><CV_CMDOUT> 8 0 291991552 sda

I am using udev rules and the rule defined is shown below: ACTION=="add|change", ENV{DM_UUID}=="mpath-360000970000192606068533031464134", SYMLINK+="oracleasm/grid/asmgrid02", GROUP="asmadmin", OWNER="oracle", MODE="0660"

The Device alias exists as shown below:
$ ls -ltr /dev/oracleasm/grid/asmgrid02

The multipath device has proper permissions set: cd /dev/oracleasm/grid
$ ls -ltr

total 0
lrwxrwxrwx 1 root root 11 Jan 16 13:37 asmgrid02 -> ../../dm-50

$ ls -ltr ../../dm-50

brw-rw---- 1 oracle asmadmin 253, 50 Jan 16 13:37 ../../dm-50

Any idea what might be wrong here?



Mladen Gogala

Oracle DBA

Received on Fri Jan 16 2015 - 21:13:52 CET

Original text of this message