UNYOUG

I found a couple of great articles on ASM trouble shooting.

This one talks about migrating RAW to ASMlib and adding a label
http://www.oracle.com/technology/tech/l ... ation.html

This article has some other suggestions include the "od" command to actually dump the data on your lun to see if the label is there.
http://jarneil.wordpress.com/2008/07/07 ... eshooting/

You can also run kfed read /dev/....

This would return a bunch of information with

kfbh.hard: 0 ; 0x001: 0x00
kfbh.type: 0 ; 0x002: KFBTYP_INVALID
kfbh.datfmt: 0 ; 0x003: 0x00

if it's bad or

kfbh.hard: 0 ; 0x001: 0x00
kfbh.type: 0 ; 0x002: KFBTYP_DISKHEADER
kfbh.datfmt: 0 ; 0x003: 0x00

if it's good.

Here's a link to an article telling you what kfed will tell you (that is known).
http://askdba.org/weblog/2008/05/ora-15 ... f-disks-2/

Every little bit helps when having an ASM hiccup.