AWS CVO reboot due to multiple disks missing
- Views:
- 118
- Visibility:
- Public
- Votes:
- 0
- Category:
- cloud-volumes-ontap-cvo
- Specialty:
- cloud
- Last Updated:
- 1/31/2025, 6:28:15 PM
Applies to
- Cloud Volumes ONTAP (CVO)
- Amazon Web Services (AWS)
Issue
- An AWS CVO node rebooted with an autopupport from the surviving HA partner: HA Group Notification (MULTIPLE DISKS MISSING) ERROR. From the surviving node's EMS logs, it can be seen that it has lost access to its mirrored Pool1 disks, which are attached to the failed node:
Mon Jun 03 16:23:02 +0000 [CVO-01: monitor: monitor.globalStatus.critical:EMERGENCY]: This node has taken over CVO-02. One or more mirrored aggregates are degraded.
Mon Jun 03 16:22:35 +0000 [CVO-01: dmgr_thread: raid.disk.missing:info]: Disk /aggr1/plex1/rg0/0d.10 S/N [00000000V9NeubcHXfRG] UID [00000000V9NeubcHXfRG] is missing from the system
Mon Jun 03 16:22:35 +0000 [CVO-01: config_thread: raid.config.filesystem.disk.missing:info]: File system Disk /aggr1/plex1/rg0/0d.10 S/N [00000000V9NeubcHXfRG] UID [00000000V9NeubcHXfRG] is missing.
(seen for all disks owned by affected node CVO-02)
- Shortly after this event, and autosupport: HA Group Notification (SYNCMIRROR PLEX FAILED) ALERT will typically also be seen, which is a residual symptom of the missing disks
- After the node rebooted, it was able to reestablish connectivity to the presented AWS disks and giveback was completed successfully