Skip to main content
NetApp Knowledge Base

ONTAP Azure node loses access to blob storage and recovers

Last Updated:

Applies to

  • ONTAP 9
  • Cloud Volumes ONTAP (CVO)
  • Microsoft Azure


  • ONTAP Azure node/cluster loses access to blob storage and quickly recovers
  •  Alert received:

pha.obj.storeUnavailable:ONTAP could not communicate with the object store,"object_store0"

  • EMS logging:

Communication to backend object store is lost...
[<node>: OscHighPriThreadPool: pha.obj.storeUnavailable:EMERGENCY]: ONTAP could not communicate with the object store, "object_store0".
[<node>: PHO_SCAN: pha.obj.scanFailure:error]: ONTAP could not get a list of objects from the object store, "object_store0", at "", using IP address "10.x.x.x" with error: store is inaccessible.
[<node>: pha_main010: scsi.cmd.adapterHardwareErrorEMSOnly:error]: Disk device 0d.1L0: Adapter detected hardware error: HA status 0xb: cdb <CDB>. Disk 0d.1 S/N [SN] UID [UID] Target Address [unknown]


Communication is restored successfully...
[<node>: OscLowPriThreadPool: pha.obj.storeAvailable:notice]: ONTAP successfully communicated with the object store, "object_store0".
[<Node>: pha_main010: scsi.cmd.retrySuccess:debug]: Disk device 0d.1L0: request successful after retry #2/#0: cdb <CDB> (100011).

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.