Skip to main content
NetApp Knowledge Base

Azure CVO HA nodes fails to boot and in boot loop

  1. Last updated
  2. Save as PDF
Views:
34
Visibility:
Public
Votes:
0
Category:
cloud-volumes-ontap-cvo
Specialty:
ds_cvo
Last Updated:

Applies to

  • Cloud Volumes ONTAP (CVO)
  • Microsoft Azure
  • CVO HA deployments using Page Blobs
  • Azure Key Vault (AKV)

Issue

  • Azure CVO HA (Page Blobs deployment) nodes fail to boot both with errors below:
Disk/device attach operation failing:

[PM-LOG] netapp_tpm_init: Begin Tue Mar 31 12:56:55 CEST 2026
A [src/rdb/quorum/rpccom.cc 82 (0x808e09000)]: _initQMClientCreateTimeout: QM default clnt_create timeout: 2.
A [src/rdb/quorum/quorumimpl.cc 61 (0x808e09000)]: _initQMNumRpcThreads: QM using default number of voter threads: 7.
Mar 31 12:56:04 [MSPrdNetappCvoNe-01:daasync.periph.alloc.fail:error]: Unable to attach new device  due to status 0x6.
rlib_rport_alloc: enabling unsafe global rkey

Adapter Errors and I/O Operations time out increase and failure against the Page Blob Disk:
[scsi.cmd.adapterHardwareErrorEMSOnly:error]: Disk device 0d.8L0: Adapter detected hardware error: HA status 0xb: cdb 0x25. Disk 0d.8 S/N [] UID [sa7a2mmjblbcontainerg0xxzcyzcjos] Target Address [unknown]
[scsi.cmd.floatTimeout:notice]: "Disk" device "0d.5L0": The page blob I/O operation timeout increased to "20" seconds: HA status "0xb": OSC Error "12": retry count "1": elapsed time "9884" milliseconds: cdb 0x25. Disk 0d.5 S/N [] UID [sa7a2mmjblbcontainer01RootBlob-M] Target Address [unknown]
[scsi.cmd.floatTimeout:notice]: "Disk" device "0d.8L0": The page blob I/O operation timeout increased to "30" seconds: HA status "0xd": OSC Error "98": retry count "2": elapsed time "29638" milliseconds: cdb 0x25. Disk 0d.8 S/N [] UID [sa7a2mmjblbcontainerg0xxzcyzcjos] Target Address [unknown]
[scsi.cmd.adapterHardwareErrorEMSOnly:error]: Disk device 0d.15L0: Adapter detected hardware error: HA status 0xb: cdb 0x25. Disk 0d.6 S/N [] UID [sa7a2mmjblbcontainergwe8gjwlbzbq] Target Address [unknown]
[scsi.cmd.adapterHardwareErrorEMSOnly:error]: Unknown device 0d.26: Adapter detected hardware error: HA status 0x6: cdb 0x12. 
[diskown.errorReadingOwnership:notice]: error 19 (disk not ready for requested operation) while reading ownership on disk 0d.0 (S/N )
[diskown.errorDuringIO:error]: error 19 (disk not ready for requested operation) on disk 0d.0 (S/N ) while reading individual disk ownership area
[config.noPartnerDisks:error]: No disks were detected for the partner; this node cannot perform takeover correctly.
  • CVO cluster is already running on apatch version for Azure MANA Hardware.
  • Azure CVO using Azure Key Vault to protect NetApp Volume Encryption (NVE) keys 
  • No IP Address change observed on Azure Storage accounts used by the CVO HA cluster.
  • ONTAP maintenance mode console showing the right Private IPs for all Storage Account Object Storage Configs on ONTAP object store DNS cache.

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.