Last updated on OCTOBER 31, 2016

Applies to:

Symptoms

ASM instance in 11.2.0.3 discovers the s2 slices of all disks as an available (candidate) for ASM.
The s2 slice starts at cylinder 0 which are getting discovered by ASM.
The first 2 cylinders are used by ASM to write the VTOC.

Document ASM Does Not Discover Disk on Solaris mentions this VTOC related information.

Example disk partition:
==============================
Part      Tag    Flag     Cylinders         Size            Blocks
  0       root    wm       3 - 27303       99.98GB    (27301/0/0) 209671680
  1 unassigned    wu       0                0         (0/0/0)             0
  2     backup    wu       0 - 27303       99.99GB    (27304/0/0) 209694720
  3 unassigned    wm       0                0         (0/0/0)             0
  4 unassigned    wm       0                0         (0/0/0)             0
  5 unassigned    wm       0                0         (0/0/0)             0
  6 unassigned    wm       0                0         (0/0/0)             0
  7 unassigned    wm       0                0         (0/0/0)             0


SQL> Select PATH,HEADER_STATU from v$asm_disk;
PATH                                               HEADER_STATU
-------------------------------------------------- ------------
/dev/rdsk/c3t60060E8005492800000049280000319Dd0s0  MEMBER
/dev/rdsk/c3t60060E8005492800000049280000319Dd0s2  CANDIDATE
/dev/rdsk/c3t60060E8005492800000049280000319Ed0s0  MEMBER
/dev/rdsk/c3t60060E8005492800000049280000319Ed0s2  CANDIDATE
/dev/rdsk/c3t60060E8005492800000049280000319Fd0s0  MEMBER
/dev/rdsk/c3t60060E8005492800000049280000319Fd0s2  CANDIDATE
/dev/rdsk/c3t60060E800549280000004928000031A0d0s0  MEMBER
/dev/rdsk/c3t60060E800549280000004928000031A0d0s2  CANDIDATE

As you can see s2 slices are getting discovered.

Before 11.2.0.3 these slices where skipped by ASM.

Cause