Re: ASM cannot locate disks
- From: Jeremy Schneider <jeremy.schneider@xxxxxxxxxxxxxx>
- To: dedba@xxxxxxxxxx
- Date: Fri, 03 Aug 2012 08:08:03 -0500
Just thought about this, and realized I should add one important
disclaimer on the public list -- remember to backup the first few blocks
before re-labeling the disk! [Easy to forget sometimes!!] :)
-J
--
Jeremy Schneider
Chicago
+1 312-725-9249
http://www.ardentperf.com
On 08/03/2012 07:40 AM, Jeremy Schneider wrote:
> It sounds to me like someone else busted the VTOC on the disks while ASM
> was running. Solaris probably didn't re-read the VTOC until the
> reboot. It's possible that ASM is still there, starting around the
> second block or second MB or something, and just "invisible" without the
> VTOC.
>
> You might check the VTOC details on the working REDO disk, assume that
> the DATA disks were setup in the same way, then re-label the DATA
> disks. I know more about linux than solaris... I've fixed partition
> tables lots of times, and I'm pretty sure that it's the same on Solaris
> -- updating the VTOC shouldn't do anything at all to the actual data on
> the disk. If you're lucky, whoever busted the disk headers didn't mess
> up the ASM headers and then the ASM disks will magically re-appear after
> fixing the VTOC. However if the ASM headers were also damaged then it's
> a much more complicated recovery.
>
> -Jeremy
>
--
//www.freelists.org/webpage/oracle-l
Other related posts:
