<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Lost disk on diskgroup -ASM. in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/Lost-disk-on-diskgroup-ASM/m-p/113057#M23960</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ASM instance ensures that any disk in a newly created disk group is addressable and is not currently a member of another disk group. You must use FORCE only when adding a disk that was dropped FORCE. If a disk is dropped NOFORCE, then use can add it NOFORCE. For example, a disk might have failed and was dropped from its disk group. After the disk is repaired, it is no longer part of any disk group, but ASM still recognizes that the disk had been a member of a disk group. You must use the FORCE flag to include the disk in a new disk group. In addition, the disk must be addressable, and the original disk group must not be mounted. Otherwise, the operation fails.&lt;/P&gt;&lt;P&gt;Also verify the timeout settings from ASM and the storage system. If your using iSCSI refer to the following KB "&lt;A href="https://kb.netapp.com/support/index?page=content&amp;amp;id=3013731&amp;quot;" target="_blank"&gt;https://kb.netapp.com/support/index?page=content&amp;amp;id=3013731"&lt;/A&gt; (Login Required)&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Fri, 27 Nov 2015 09:47:21 GMT</pubDate>
    <dc:creator>Renifa</dc:creator>
    <dc:date>2015-11-27T09:47:21Z</dc:date>
    <item>
      <title>Lost disk on diskgroup -ASM.</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Lost-disk-on-diskgroup-ASM/m-p/112325#M23813</link>
      <description>&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We have created a new diskgroup (currently empty) &amp;nbsp;with normal redundancy within ASM (3 disks) and it looks like the issue persists on this new diskgroup too.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Sat Nov 07 07:36:49 2015&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;WARNING: Waited 15 secs for write IO to PST disk 0 in group 11.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;WARNING: Waited 15 secs for write IO to PST disk 2 in group 11.&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;WARNING: Waited 15 secs for write IO to PST disk 0 in group 11.&lt;/P&gt;
&lt;P&gt;WARNING: Waited 15 secs for write IO to PST disk 2 in group 11.&lt;/P&gt;
&lt;P&gt;Sat Nov 07 07:36:49 2015&lt;/P&gt;
&lt;P&gt;NOTE: process _b000_+asm1 (26349) &lt;STRONG&gt;initiating offline&lt;/STRONG&gt; of disk 0.2452385562 (ASMGRP_0000) with mask 0x7e in group 11&lt;/P&gt;
&lt;P&gt;NOTE: process _b000_+asm1 (26349) initiating offline of disk 2.2452385560 (ASMGRP_0002) with mask 0x7e in group 11&lt;/P&gt;
&lt;P&gt;NOTE: checking PST: grp = 11&lt;/P&gt;
&lt;P&gt;GMON checking disk modes for group 11 at 80 for pid 29, osid 26349&lt;/P&gt;
&lt;P&gt;ERROR: no read quorum in group: required 2, found 1 disks&lt;/P&gt;
&lt;P&gt;NOTE: checking PST for grp 11 done.&lt;/P&gt;
&lt;P&gt;NOTE: initiating PST update: grp = 11, dsk = 0/0x922c6f1a, mask = 0x6a, op = clear&lt;/P&gt;
&lt;P&gt;NOTE: initiating PST update: grp = 11, dsk = 2/0x922c6f18, mask = 0x6a, op = clear&lt;/P&gt;
&lt;P&gt;GMON updating disk modes for group 11 at 81 for pid 29, osid 26349&lt;/P&gt;
&lt;P&gt;ERROR: no read quorum in group: required 2, found 1 disks&lt;/P&gt;
&lt;P&gt;WARNING: Offline for disk ASMGRP_0000 in mode 0x7f failed.&lt;/P&gt;
&lt;P&gt;WARNING: Offline for disk ASMGRP_0002 in mode 0x7f failed.&lt;/P&gt;
&lt;P&gt;Sat Nov 07 07:36:49 2015&lt;/P&gt;
&lt;P&gt;NOTE: cache dismounting (not clean) group 11/0x098C9F83 (ASMGRP)&lt;/P&gt;
&lt;P&gt;NOTE: messaging CKPT to quiesce pins Unix process pid: 26351, image: &lt;A href="mailto:oracle@dcdb75.corp.cyta.gr" target="_blank"&gt;oracle@dcdb75.local.domain&lt;/A&gt; (B001)&lt;/P&gt;
&lt;P&gt;Sat Nov 07 07:36:49 2015&lt;/P&gt;
&lt;P&gt;NOTE: halting all I/Os to diskgroup 11 (ASMGRP)&lt;/P&gt;
&lt;P&gt;Sat Nov 07 07:36:58 2015&lt;/P&gt;
&lt;P&gt;WARNING: dirty detached from domain 11&lt;/P&gt;
&lt;P&gt;NOTE: cache dismounted group 11/0x098C9F83 (ASMGRP)&lt;/P&gt;
&lt;P&gt;NOTE: cache deleting context for group ASMGRP 11/0x098c9f83&lt;/P&gt;
&lt;P&gt;SQL&amp;gt; alter diskgroup ASMGRP dismount force /* ASM SERVER:160210819 */&lt;/P&gt;
&lt;P&gt;GMON dismounting group 11 at 82 for pid 30, osid 26351&lt;/P&gt;
&lt;P&gt;NOTE: Disk ASMGRP_0000 in mode 0x7f marked for de-assignment&lt;/P&gt;
&lt;P&gt;NOTE: Disk ASMGRP_0001 in mode 0x7f marked for de-assignment&lt;/P&gt;
&lt;P&gt;NOTE: Disk ASMGRP_0002 in mode 0x7f marked for de-assignment&lt;/P&gt;
&lt;P&gt;SUCCESS: diskgroup ASMGRP was dismounted&lt;/P&gt;
&lt;P&gt;SUCCESS: alter diskgroup ASMGRP dismount force /* ASM SERVER:160210819 */&lt;/P&gt;
&lt;P&gt;Sat Nov 07 07:36:58 2015&lt;/P&gt;
&lt;P&gt;NOTE: diskgroup resource ora.ASMGRP.dg is offline&lt;/P&gt;
&lt;P&gt;SUCCESS: ASM-initiated MANDATORY DISMOUNT of group ASMGRP&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Note.&lt;/P&gt;
&lt;P&gt;We have two-node&amp;nbsp; asm cluster&amp;nbsp; with&amp;nbsp; Oracle 11.2.0.4&amp;nbsp; and Oracle linux 6.3.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jun 2025 22:49:47 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Lost-disk-on-diskgroup-ASM/m-p/112325#M23813</guid>
      <dc:creator>vkritsimas</dc:creator>
      <dc:date>2025-06-04T22:49:47Z</dc:date>
    </item>
    <item>
      <title>Re: Lost disk on diskgroup -ASM.</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/Lost-disk-on-diskgroup-ASM/m-p/113057#M23960</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The ASM instance ensures that any disk in a newly created disk group is addressable and is not currently a member of another disk group. You must use FORCE only when adding a disk that was dropped FORCE. If a disk is dropped NOFORCE, then use can add it NOFORCE. For example, a disk might have failed and was dropped from its disk group. After the disk is repaired, it is no longer part of any disk group, but ASM still recognizes that the disk had been a member of a disk group. You must use the FORCE flag to include the disk in a new disk group. In addition, the disk must be addressable, and the original disk group must not be mounted. Otherwise, the operation fails.&lt;/P&gt;&lt;P&gt;Also verify the timeout settings from ASM and the storage system. If your using iSCSI refer to the following KB "&lt;A href="https://kb.netapp.com/support/index?page=content&amp;amp;id=3013731&amp;quot;" target="_blank"&gt;https://kb.netapp.com/support/index?page=content&amp;amp;id=3013731"&lt;/A&gt; (Login Required)&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 27 Nov 2015 09:47:21 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/Lost-disk-on-diskgroup-ASM/m-p/113057#M23960</guid>
      <dc:creator>Renifa</dc:creator>
      <dc:date>2015-11-27T09:47:21Z</dc:date>
    </item>
  </channel>
</rss>

