The partition disk is broken with the label version
Applies to
- ONTAP 9
- ADP (Advanced Drive Partitioning)
Issue
- This typically occurs when a newly installed disk shows a failed status because its RAID label version is not compatible with the currently supported range.
::*> disk show -broken
Original Owner: node-01
Checksum Compatibility: block
Drawer Usable Physical
Disk Outage Reason HA Shelf Bay /Slot Chan Pool Type RPM Size Size
--------------- ------------- --- ----- --- ------ ---- ------ ----- ------ -------- --------
1.0.10 label version 0n 0 11 -/- A Pool0
SSD-NVM - 3.49TB 3.49TB
1 entries were displayed.
- The container is not owned by the same node that owns the partitions
*> aggr status -f
Broken disks
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)--------- ------ ------------- ---- ---- ---- ----- -------------- --------------label version 0n.10P3 0n 0 10 NV:B 0 SSD-NVM N/A 95764/24515712 95772/24517760label version 0n.10P2 0n 0 10 NV:B 0 SSD-NVM N/A 1783385/456546688 1783393/456548736 (fast zeroed)label version 0n.10P1 0n 0 10 NV:B 0 SSD-NVM N/A 1783385/456546688 1783393/456548736 (fast zeroed)
- Unable to unfail partitioned drive 'Reason: Disk not found.'
::*> disk unfail -disk 1.0.10 -spare true
Warning: Failed disk "1.0.10" might have aggregate labels and file system data present. Releasing this disk as a spare disk will lead to permanent loss of file system data that might be on this disk, and it might prevent recovery of a failed aggregate. Are you sure you want to continue with disk unfail? {y|n}: y
Error: command failed: Failed to unfail the disk. Reason: Disk not found.