Skip to main content
NetApp Knowledge Base

ONTAP Select node unexpectedly restarted

Views:
206
Visibility:
Public
Votes:
0
Category:
ontap-select
Specialty:
ontapselect
Last Updated:

Applies to

  • NetApp ONTAP Select
  • VMware ESXi

Description

  • An ONTAP Select (OTS) node/VM unexpectedly restarted and automatically returned online.
  • After reviewing the NetApp AutoSupport (ASUP) event logs, multiple disks went missing, the node failed, and the PLEX went offline.
  • Logs may show:
  • [TEST-ONTAP-1-2: dmgr_thread: raid.disk.missing:info]: Disk 0d.36 S/N [00000000vXHOaJhGtfcm] UID [00000000vXHOaJhGtfcm] is missing from the system [?]
    [TEST-ONTAP-1-2: dmgr_thread: raid.disk.missing:info]: Disk 0d.40 S/N [0VpF0-csxVspEkBpP/VW] UID [0VpF0-csxVspEkBpP/VW] is missing from the system [?]
    [TEST-ONTAP-1-2: dmgr_thread: raid.disk.missing:info]: Disk 0d.42 S/N [00000000lDhW37cEPycq] UID [00000000lDhW37cEPycq] is missing from the system [?]
    [TEST-ONTAP-1-2: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk /aggr0_TEST_ONTAP_1_2_0/plex6/rg0/0d.13 S/N [0VpF0-csRXEBLurW1fN3] UID [0VpF0-csRXEBLurW1fN3] is missing. [?]
    [TEST-ONTAP-1-2: dmgr_thread: raid.disk.missing:info]: Disk 0d.38 S/N [0VpF0-csiAo3Li1jTxw6] UID [0VpF0-csiAo3Li1jTxw6] is missing from the system [?]
    [TEST-ONTAP-1-2: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk /aggr2/plex5/rg0/0d.34 S/N [0VpF0-csScX-sMoWmBo5] UID [0VpF0-csScX-sMoWmBo5] is missing. [?]
    [TEST-ONTAP-1-2: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk /aggr2/plex5/rg0/0d.17 S/N [0VpF0-csxDwZA-4opUVg] UID [0VpF0-csxDwZA-4opUVg] is missing. [?]
    [TEST-ONTAP-1-2: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk /aggr2/plex5/rg0/0d.30 S/N [00000000PC6QgHbIossk] UID [00000000PC6QgHbIossk] is missing. [?]
    [TEST-ONTAP-1-2: cf_takeover: cf.rsrc.transitTime:debug]: Top Takeover transit times disk_assignment=98, lock manager=146, ffo_bdata_cleanup=184, registry_prerc=202, wafl_replay=204 {op_replay_0=147, validate_bkts=23, enable_log=19, prep_log _0=12, init=1, sync_log_0=1, mark_replaying=0, catalog_init=0, replay_log_missing=0, nvfail=0}, registry_postrc_phase1=270 {set_start1=0, start_stop=56 {timed=0, tftpd=0, snmp=0}, set_start2=0, snmpv3_user_init=0, reg_per_check=108, snmp_res_traphost=0}, wafl=352 {paggrs_to_done=212, pvvols_to_done=114, prvol_to_done=24, snapmirror_cg_sync_=0, verify_names=0}, wafl_make_mounted=390 {wait_cp=385, pvols_mnt_end=2, prvol_pre_mnt_end=1, flush_raid_dirty_vo=1, destroy_vvol=0, pvols_pre_mnt_end=0, finish=0}, aure_vnvram_handshake=3047, xl=5032. [?]
    [TEST-ONTAP-1-2: config_failed_disk: callhome.disks.missing:error]: Call home for MULTIPLE DISKS MISSING

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.