Re: ORA-15042: ASM disk "xx" is missing

From: Fergal Taheny <ftaheny_at_gmail.com>
Date: Thu, 3 Jan 2013 10:09:35 +0000
Message-ID: <CAOuMUT6xN_bQ7zVhD1nii1N2S3gOWqhD0OHT=ium7fPT88=F9Q_at_mail.gmail.com>



Hi,
I had tried kfed but not kfod. Still no joy the 5 missing disks don't show up.

> kfod asm_diskstring='/dev/oradsk/*' disks=all


 Disk          Size Path                                     User     Group
================================================================================
   1:     204760 Mb /dev/oradsk/ASMDA1                       oracle   dba
   2:     204760 Mb /dev/oradsk/ASMDA10                      oracle   dba
   3:     204760 Mb /dev/oradsk/ASMDA11                      oracle   dba
   4:     204760 Mb /dev/oradsk/ASMDA12                      oracle   dba
   5:     204760 Mb /dev/oradsk/ASMDA13                      oracle   dba
   6:     204760 Mb /dev/oradsk/ASMDA14                      oracle   dba
   7:     204760 Mb /dev/oradsk/ASMDA15                      oracle   dba
   8:     204760 Mb /dev/oradsk/ASMDA16                      oracle   dba
   9:     204760 Mb /dev/oradsk/ASMDA17                      oracle   dba
  10:     204760 Mb /dev/oradsk/ASMDA18                      oracle   dba
  11:     204760 Mb /dev/oradsk/ASMDA2                       oracle   dba
  12:     204760 Mb /dev/oradsk/ASMDA4                       oracle   dba
  13:     204760 Mb /dev/oradsk/ASMDA7                       oracle   dba
  14:     409576 Mb /dev/oradsk/ASMDATA1                     oracle   dba
  15:     409576 Mb /dev/oradsk/ASMDATA2                     oracle   dba
  16:     409576 Mb /dev/oradsk/ASMDATA3                     oracle   dba
  17:     409576 Mb /dev/oradsk/ASMDATA4                     oracle   dba
  18:     409576 Mb /dev/oradsk/ASMDATA5                     oracle   dba
  19:     409576 Mb /dev/oradsk/ASMDATA6                     oracle   dba
  20:     409576 Mb /dev/oradsk/ASMDATA7                     oracle   dba
  21:     409576 Mb /dev/oradsk/ASMDATA8                     oracle   dba
  22:     409576 Mb /dev/oradsk/ASMDATA9                     oracle   dba
  23:     204760 Mb /dev/oradsk/ASMFL2                       oracle   dba
  24:     204760 Mb /dev/oradsk/ASMFL3                       oracle   dba
  25:     204760 Mb /dev/oradsk/ASMFL4                       oracle   dba
  26:     204760 Mb /dev/oradsk/ASMFL5                       oracle   dba
  27:     204760 Mb /dev/oradsk/ASMFL6                       oracle   dba
  28:     204760 Mb /dev/oradsk/ASMFL8                       oracle   dba
  29:     307176 Mb /dev/oradsk/ASMFLSH1                     oracle   dba
  30:     307176 Mb /dev/oradsk/ASMFLSH2                     oracle   dba
  31:     307176 Mb /dev/oradsk/ASMFLSH3                     oracle   dba
  32:     307176 Mb /dev/oradsk/ASMFLSH4                     oracle   dba
  33:     307176 Mb /dev/oradsk/ASMFLSH5                     oracle   dba
  34:      25594 Mb /dev/oradsk/ASMREDO1                     oracle   dba
  35:      25594 Mb /dev/oradsk/ASMREDO2                     oracle   dba
  36:      25594 Mb /dev/oradsk/ASMREDO3                     oracle   dba
  37:      25594 Mb /dev/oradsk/ASMREDO4                     oracle   dba
--------------------------------------------------------------------------------
ORACLE_SID ORACLE_HOME

      +ASM /u02/app/oracle/product/11.1.0.7/asm

Also, I trussed the rbal process while attempting to mount the disk group in another session.

See here. http://pastebin.com/pLnNNAin

Not much use though. Yes there are some errors like this

  1. stat("/dev/oradsk/ASMDA3", 0xFFFFFFFF7FFFCCC0) Err#2 ENOENT

Now we know that /dev/oradsk/ASMDA3 is indeed one of the missing disks as per the old alert log. But all that the truss proves is that the process can't read from these devices that it finds in the asm_diskstring. These could just have been devices that were just left behind by a sloppy administrator!

Regards,
Fergal

On 3 January 2013 09:13, Luis <lcarapinha_at_gmail.com> wrote:

> I'm also curious about this issue :-)
>
> Not sure if you tried kfod that is normally used with disk discovery
> problems.I'd say that kfod will perform the same discovery as asm instance
> in startup using asm_diskstring.
>
> Can you try this:
>
> kfod asm_diskstring='/your_disk_string/*' disks=all
>
>
> Luis Marques
>
>
> On Thu, Jan 3, 2013 at 8:57 AM, Fergal Taheny <ftaheny_at_gmail.com> wrote:
>
>> /dev/oradsk/ASMDA1
>
>
> --
> Cumprimentos,
> Lu�s Marques
>

-- 
Fergal Taheny
Pentec IT Limited
2 knightsbrook court, Dublin Road, Trim, Co. Meath.
+353 (0) 87 9823137
ftaheny_at_gmail.com

This email and any files transmitted with it are confidential and intended
solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify us immediately.  It
is possible for data transmitted by email to be deliberately or
accidentally corrupted or intercepted. For this reason, where the
communication is by email, Pentec IT does not accept any responsibility for
any breach of confidence which may arise through the use of this medium.
Pentec IT Limited is Registered in Ireland: No 443280 with a registered
office at 2 Knightsbrook Court, Dublin Road, Trim, Co. Meath. Company
Directors: Fergal Taheny, Caitriona Ni Riain.

--
http://www.freelists.org/webpage/oracle-l
Received on Thu Jan 03 2013 - 11:09:35 CET

Original text of this message