OS administrator might claim the candidate disks prepared for you to install ASM are newly created and very clean. But if they are not, then, you will meet failure during installing ASM, and never know the reason.
Maybe you can mount the ASM diskgroup through ASMCA if you decide to ignore the error, but you will still meet failure in the successive database installation.
At this moment, please recheck your candidate disks are clean or not, you may try pvcreate or fdisk, but they won't save you out of the trap. The problem is still there.
Now, let's actually clean the candidate disks by command dd, don't bother to recreate physical volumes.
# dd if=/dev/zero of=/dev/rdisk/disk01 bs=1024k count=1000
# dd if=/dev/zero of=/dev/rdisk/disk02 bs=1024k count=1000
# dd if=/dev/zero of=/dev/rdisk/disk03 bs=1024k count=1000
# dd if=/dev/zero of=/dev/rdisk/disk04 bs=1024k count=1000
In this case, every candidate disk is near 120GB, but you don't need to set the count too large, just clean the front part of every disks, in which it is usually problematic.
With the same logic, if you want to reinstall ASM, dd the candidate disks before installation.