Also, was this perhaps the first whole machine reboot since the LUNs were configured? If so, check permissions and that the order of boot sequence did not mount them as owned by root instead of oracle or with the wrong group before oracle tries to mount them correctly for ASM. Those errors would be in the system logs if oracle is trying to mount something that is already mounted. You mentioned that this is a zone, so the overall machine reboot may grab the resources differently than just restarting a zone. Your sysadmin should be helpful with the details about whether this is possibly your problem. -----Original Message----- From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Peter Hitchman Sent: Friday, August 03, 2012 6:35 AM To: oracle-l Subject: Re: ASM cannot locate disks Hi, My experience with problems on Solaris with ASM have either been with device permissions or a failure to partition the LUNs in the first place. Have you checked that nothing odd has happened to the partition tables on the LUNs seen as RAW? Regards Pete -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l