Re: Root.sh Disk group creation failed

From: Andrew Kerber <andrew.kerber_at_gmail.com>
Date: Mon, 26 Nov 2018 09:30:39 -0600
Message-ID: <CAJvnOJZL_z7F1LWeiC4_S-tRbpaKEYpAhPJ0xHnLTRC=0SbZ5g_at_mail.gmail.com>



Everything should be the default Linux sector size, which is 512. I didnt change anything on that. And I did partition them first. I initially partitioned with parted gpt partitions, and when I got the error I went back and cleaned them off and partitioned them with fdisk. It didnt make a difference.

The fun part of that process was disabling AFD by the way, that is something else that is poorly documented, and needs to be documented for a failed installation.

On Thu, Nov 22, 2018 at 3:18 AM Jose Rodriguez <jrodriguez2_at_pythian.com> wrote:

> Is the disk physical sector size 512 or 4K. In the latter case, ASM may
> not be able to create small block size files, like controfiled and probably
> OCR files.
> I had to force ASMLib in the past to use the logical sector size of the
> disks (512) to be able to create controfiles during a RMAN duplicate.
>
> I just found out that I haven't blogged about it yet, so I have a pending
> task here.
>
> I hope this gives you a clue on the issue.
>
> On Thu, 22 Nov 2018, 03:05 Stefan Knecht <knecht.stefan_at_gmail.com wrote:
>
>> ORA-59012: Disk %0!s uses an invalid physical sector size (%1!s).
>>
>> Cause: The disk used a physical sector size value that is not standard
>> or is not currently supported.
>>
>> Action: The disk cannot be used for an ASM disk group.
>>
>> Have you partitioned the disks? If not, that'd be the next thing I'd try
>> - just do a standard partitioning using fdisk.
>>
>> Also, the joys of using the latest release - search MoS for the Oracle
>> error number and you get zero results :)
>>
>>
>>
>> On Thu, Nov 22, 2018 at 12:06 AM Andrew Kerber <andrew.kerber_at_gmail.com>
>> wrote:
>>
>>> I am building an oracle 18.3 cluster in vmware workstation on oracle
>>> linux 7.5 in order to compose a blog. I have done this several times on
>>> multiple oracle versions, but I am getting an error out of root.sh on my
>>> latest build. Any thoughts on this? I was using the gui gridSetup.sh, and
>>> it didnt have any problems finding the disks.
>>>
>>> [INFO] [DBT-30161] Disk label(s) created successfully. Check
>>> /u01/app/grid/12.2.0/grid_base/cfgtoollogs/asmca/asmca-181121AM105258.log
>>> for details.
>>> [FATAL] [DBT-30002] Disk group OCR creation failed.
>>> ORA-15018: diskgroup cannot be created
>>> ORA-59012: Disk AFD:OCR4 uses an invalid physical sector size (2560).
>>> ORA-59012: Disk AFD:OCR3 uses an invalid physical sector size (2560).
>>> ORA-59012: Disk AFD:OCR2 uses an invalid physical sector size (2560).
>>> ORA-59012: Disk AFD:OCR1 uses an invalid physical sector size (2560).
>>>
>>> The full output of root.sh is below (this is the 3rd run with the same
>>> output):
>>>
>>> [root_at_oelafd1 grid]# ./root.sh
>>> Performing root user operation.
>>>
>>> The following environment variables are set as:
>>> ORACLE_OWNER= grid
>>> ORACLE_HOME= /u01/app/grid/12.2.0/grid
>>>
>>> Enter the full pathname of the local bin directory: [/usr/local/bin]:
>>> The contents of "dbhome" have not changed. No need to overwrite.
>>> The contents of "oraenv" have not changed. No need to overwrite.
>>> The contents of "coraenv" have not changed. No need to overwrite.
>>>
>>> Entries will be added to the /etc/oratab file as needed by
>>> Database Configuration Assistant when a database is created
>>> Finished running generic part of root script.
>>> Now product-specific root actions will be performed.
>>> Relinking oracle with rac_on option
>>> Using configuration parameter file:
>>> /u01/app/grid/12.2.0/grid/crs/install/crsconfig_params
>>> The log of current session can be found at:
>>>
>>> /u01/app/grid/12.2.0/grid_base/crsdata/oelafd1/crsconfig/rootcrs_oelafd1_2018-11-21_10-48-53AM.log
>>> 2018/11/21 10:49:05 CLSRSC-594: Executing installation step 1 of 20:
>>> 'SetupTFA'.
>>> 2018/11/21 10:49:05 CLSRSC-4001: Installing Oracle Trace File Analyzer
>>> (TFA) Collector.
>>> 2018/11/21 10:49:05 CLSRSC-4002: Successfully installed Oracle Trace
>>> File Analyzer (TFA) Collector.
>>> 2018/11/21 10:49:05 CLSRSC-594: Executing installation step 2 of 20:
>>> 'ValidateEnv'.
>>> 2018/11/21 10:49:05 CLSRSC-363: User ignored prerequisites during
>>> installation
>>> 2018/11/21 10:49:06 CLSRSC-594: Executing installation step 3 of 20:
>>> 'CheckFirstNode'.
>>> 2018/11/21 10:49:10 CLSRSC-594: Executing installation step 4 of 20:
>>> 'GenSiteGUIDs'.
>>> 2018/11/21 10:49:18 CLSRSC-594: Executing installation step 5 of 20:
>>> 'SaveParamFile'.
>>> 2018/11/21 10:49:22 CLSRSC-594: Executing installation step 6 of 20:
>>> 'SetupOSD'.
>>> 2018/11/21 10:49:22 CLSRSC-594: Executing installation step 7 of 20:
>>> 'CheckCRSConfig'.
>>> 2018/11/21 10:49:23 CLSRSC-594: Executing installation step 8 of 20:
>>> 'SetupLocalGPNP'.
>>> 2018/11/21 10:49:25 CLSRSC-594: Executing installation step 9 of 20:
>>> 'CreateRootCert'.
>>> 2018/11/21 10:49:43 CLSRSC-594: Executing installation step 10 of 20:
>>> 'ConfigOLR'.
>>> 2018/11/21 10:49:47 CLSRSC-594: Executing installation step 11 of 20:
>>> 'ConfigCHMOS'.
>>> 2018/11/21 10:49:47 CLSRSC-594: Executing installation step 12 of 20:
>>> 'CreateOHASD'.
>>> 2018/11/21 10:49:50 CLSRSC-594: Executing installation step 13 of 20:
>>> 'ConfigOHASD'.
>>> 2018/11/21 10:50:08 CLSRSC-594: Executing installation step 14 of 20:
>>> 'InstallAFD'.
>>> 2018/11/21 10:50:13 CLSRSC-594: Executing installation step 15 of 20:
>>> 'InstallACFS'.
>>> 2018/11/21 10:50:24 CLSRSC-594: Executing installation step 16 of 20:
>>> 'InstallKA'.
>>> 2018/11/21 10:50:41 CLSRSC-594: Executing installation step 17 of 20:
>>> 'InitConfig'.
>>> CRS-2791: Starting shutdown of Oracle High Availability Services-managed
>>> resources on 'oelafd1'
>>> CRS-2673: Attempting to stop 'ora.asm' on 'oelafd1'
>>> CRS-2673: Attempting to stop 'ora.ctssd' on 'oelafd1'
>>> CRS-2673: Attempting to stop 'ora.evmd' on 'oelafd1'
>>> CRS-2673: Attempting to stop 'ora.drivers.acfs' on 'oelafd1'
>>> CRS-2673: Attempting to stop 'ora.mdnsd' on 'oelafd1'
>>> CRS-2677: Stop of 'ora.ctssd' on 'oelafd1' succeeded
>>> CRS-2677: Stop of 'ora.evmd' on 'oelafd1' succeeded
>>> CRS-2677: Stop of 'ora.drivers.acfs' on 'oelafd1' succeeded
>>> CRS-2677: Stop of 'ora.mdnsd' on 'oelafd1' succeeded
>>> CRS-2677: Stop of 'ora.asm' on 'oelafd1' succeeded
>>> CRS-2673: Attempting to stop 'ora.cluster_interconnect.haip' on 'oelafd1'
>>> CRS-2677: Stop of 'ora.cluster_interconnect.haip' on 'oelafd1' succeeded
>>> CRS-2673: Attempting to stop 'ora.cssd' on 'oelafd1'
>>> CRS-2677: Stop of 'ora.cssd' on 'oelafd1' succeeded
>>> CRS-2673: Attempting to stop 'ora.driver.afd' on 'oelafd1'
>>> CRS-2673: Attempting to stop 'ora.gipcd' on 'oelafd1'
>>> CRS-2673: Attempting to stop 'ora.gpnpd' on 'oelafd1'
>>> CRS-2677: Stop of 'ora.driver.afd' on 'oelafd1' succeeded
>>> CRS-2677: Stop of 'ora.gipcd' on 'oelafd1' succeeded
>>> CRS-2677: Stop of 'ora.gpnpd' on 'oelafd1' succeeded
>>> CRS-2793: Shutdown of Oracle High Availability Services-managed
>>> resources on 'oelafd1' has completed
>>> CRS-4133: Oracle High Availability Services has been stopped.
>>> CRS-4123: Oracle High Availability Services has been started.
>>> CRS-2672: Attempting to start 'ora.driver.afd' on 'oelafd1'
>>> CRS-2672: Attempting to start 'ora.evmd' on 'oelafd1'
>>> CRS-2672: Attempting to start 'ora.mdnsd' on 'oelafd1'
>>> CRS-2676: Start of 'ora.driver.afd' on 'oelafd1' succeeded
>>> CRS-2672: Attempting to start 'ora.cssdmonitor' on 'oelafd1'
>>> CRS-2676: Start of 'ora.cssdmonitor' on 'oelafd1' succeeded
>>> CRS-2676: Start of 'ora.evmd' on 'oelafd1' succeeded
>>> CRS-2676: Start of 'ora.mdnsd' on 'oelafd1' succeeded
>>> CRS-2672: Attempting to start 'ora.gpnpd' on 'oelafd1'
>>> CRS-2676: Start of 'ora.gpnpd' on 'oelafd1' succeeded
>>> CRS-2672: Attempting to start 'ora.gipcd' on 'oelafd1'
>>> CRS-2676: Start of 'ora.gipcd' on 'oelafd1' succeeded
>>> CRS-2672: Attempting to start 'ora.cssd' on 'oelafd1'
>>> CRS-2672: Attempting to start 'ora.diskmon' on 'oelafd1'
>>> CRS-2676: Start of 'ora.diskmon' on 'oelafd1' succeeded
>>> CRS-2676: Start of 'ora.cssd' on 'oelafd1' succeeded
>>>
>>> [INFO] [DBT-30161] Disk label(s) created successfully. Check
>>> /u01/app/grid/12.2.0/grid_base/cfgtoollogs/asmca/asmca-181121AM105258.log
>>> for details.
>>> [FATAL] [DBT-30002] Disk group OCR creation failed.
>>> ORA-15018: diskgroup cannot be created
>>> ORA-59012: Disk AFD:OCR4 uses an invalid physical sector size (2560).
>>> ORA-59012: Disk AFD:OCR3 uses an invalid physical sector size (2560).
>>> ORA-59012: Disk AFD:OCR2 uses an invalid physical sector size (2560).
>>> ORA-59012: Disk AFD:OCR1 uses an invalid physical sector size (2560).
>>>
>>>
>>>
>>> 2018/11/21 10:55:05 CLSRSC-184: Configuration of ASM failed
>>> 2018/11/21 10:55:19 CLSRSC-258: Failed to configure and start ASM
>>> Died at /u01/app/grid/12.2.0/grid/crs/install/crsinstall.pm line 2471.
>>>
>>>
>>>
>>> --
>>> Andrew W. Kerber
>>>
>>> 'If at first you dont succeed, dont take up skydiving.'
>>>
>>
>>
>> --
>> //
>> zztat - The Next-Gen Oracle Performance Monitoring and Reaction Framework!
>> Visit us at zztat.net | _at_zztat_oracle | fb.me/zztat | zztat.net/blog/
>>
>
> --
>
>
>
>

-- 
Andrew W. Kerber

'If at first you dont succeed, dont take up skydiving.'

--
http://www.freelists.org/webpage/oracle-l
Received on Mon Nov 26 2018 - 16:30:39 CET

Original text of this message