Re: CVU reporting error when checking for ASM storage

From: Kevin Closson <>
Date: Tue, 27 Jan 2015 16:29:43 +0000
Message-ID: <>

Hi Amir,
   So are you still having these difficulties? Did you go with a single partition perhaps just to ensure proper alignment? 

      From: "Hameed, Amir" <>  To: Riyaj Shamsudeen <>; "" <> Cc: "" <>; "" <>  Sent: Thursday, January 22, 2015 10:09 AM  Subject: RE: CVU reporting error when checking for ASM storage    

#yiv4273292093 #yiv4273292093 -- _filtered #yiv4273292093 {panose-1:2 4 5 3 5 4 6 3 2 4;} _filtered #yiv4273292093 {font-family:Calibri;panose-1:2 15 5 2 2 2 4 3 2 4;} _filtered #yiv4273292093 {font-family:Consolas;panose-1:2 11 6 9 2 2 4 3 2 4;}#yiv4273292093 #yiv4273292093 p.yiv4273292093MsoNormal, #yiv4273292093 li.yiv4273292093MsoNormal, #yiv4273292093 div.yiv4273292093MsoNormal {margin:0in;margin-bottom:.0001pt;font-size:12.0pt;}#yiv4273292093 a:link, #yiv4273292093 span.yiv4273292093MsoHyperlink {color:blue;text-decoration:underline;}#yiv4273292093 a:visited, #yiv4273292093 span.yiv4273292093MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv4273292093 p {margin-right:0in;margin-left:0in;font-size:12.0pt;}#yiv4273292093 pre {margin:0in;margin-bottom:.0001pt;font-size:10.0pt;}#yiv4273292093 span.yiv4273292093HTMLPreformattedChar {font-family:Consolas;}#yiv4273292093 span.yiv4273292093EmailStyle20 {color:#1F497D;}#yiv4273292093 .yiv4273292093MsoChpDefault {} _filtered #yiv4273292093 {margin:1.0in 1.0in 1.0in 1.0in;}#yiv4273292093 div.yiv4273292093WordSection1 {}#yiv4273292093 I would like to add that I got the same CVU error when I tried the same command on a partitioned disk. I am not sure if I am the only one who has seen this CVU error or others have also encountered it.  

From: Riyaj Shamsudeen [] Sent: Thursday, January 22, 2015 12:29 PM To:
Cc: Hameed, Amir;; Subject: Re: CVU reporting error when checking for ASM storage   There is no requirement to partition the disk, AFAIK, for Grid install. Amir and I worked this problem offline, and it seems that CVU has a bug. Proceeding with that useful "ignore all" button during Grid installation, completes successfully.

However,  in Solaris platform, disk must be partitioned though.  Cheers

Riyaj Shamsudeen
Principal DBA,
Ora!nternals - Specialists in Performance, RAC and EBS Blog: Oracle ACE Director and OakTable member Co-author of the books: Expert Oracle Practices, Pro Oracle SQL, Expert RAC Practices 12c. Expert PL/SQL practices     On Fri, Jan 16, 2015 at 12:26 PM, David Barbour <> wrote: Amir - You missed what Mladen and Tim are pointing out.  /dev/<whatever>/dm-50 is a block device.  What Mladen refers to as "scusify", Tim shows with the output: udev_rules_get_name: add symlink 'disk/by-path/pci-0000:00:0d.0-scsi-1:0:0:0-part1' Partition the disk using parted or (deprecated) fdisk.  You can make the name available either through udev rules or via friendly names in the multipath.conf file. By the way - welcome back Mladen.

    On Fri, Jan 16, 2015 at 2:13 PM, Hameed, Amir <> wrote: 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   1. ACTION=="add|change", ENV{DM_UUID}=="mpath-<UUID>", SYMLINK+="oracleasm/asm01", GROUP="dba", OWNER="oracle", MODE="0660" []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---- 1oracle asmadmin 253, 50 Jan 16 13:37 ../../dm-50   Any idea what might be wrong here?   Thanks, Amir 

Received on Tue Jan 27 2015 - 17:29:43 CET

Original text of this message