DISK BAD LABEL - AutoSupport Message
Applies to
- ONTAP 9
- callhome.dsk.label / callhome.fdsk.label / callhome.sdsk.label — DISK / FILESYSTEM / SPARE DISK BAD LABEL
- callhome.dsk.label.v / callhome.fdsk.label.v / callhome.sdsk.label.v — DISK / FILESYSTEM / SPARE DISK BAD LABEL VERSION
- raid.config.disk.bad.label
- raid.config.filesystem.disk.bad.label
- raid.assim.disk.nolabels
- raid.assim.disk.badlabelversion
Event Summary
- This message occurs when a disk drive fails due to unexpected RAID metadata.
- Usually caused by adding non-zeroed drives that were previously used in a different ONTAP OS.
- The drives have not truly failed. Due to the mismatch of ONTAP versions, the disks show up as
bad labelfailed.
[Node Name: config_thread: callhome.dsk.label:alert]: Call home for DISK BAD LABEL
[Node Name: config_thread: callhome.dsk.label.v:error]: Call home for DISK BAD LABEL VERSION
Validate
Event Log
::> event log show -severity * -message-name *bad.label*
bad label example:
[Node Name: config_thread: raid.assim.disk.nolabels:EMERGENCY]: Disk 0d.23.17 ... has no valid labels. It will be taken out of service to prevent possible data loss. [Node Name: config_thread: raid.config.disk.bad.label:notice]: Disk 0d.23.17 ... has bad or missing data on label. [Node Name: config_thread: callhome.dsk.label:alert]: Call home for DISK BAD LABEL
label version example:
[Node Name: config_thread: raid.assim.disk.badlabelversion:alert]: Disk ... has RAID label with version (18), which is not within the currently supported range (5 - 17). [Node Name: config_thread: raid.config.filesystem.disk.bad.label.version:notice]: File system Disk ... has an unsupported label version. [Node Name: config_thread: callhome.fdsk.label.v:error]: Call home for FILESYSTEM DISK BAD LABEL VERSION
Also check for upgrade / mixed-version evidence when the subject contains VERSION:
::> event log show -severity * -message-name *versionMismatch* ::> event log show -severity * -message-name raid.assim.label.upgrade
Command Line
::> storage disk show -broken ::> version ::> cluster image show-update-progress ::> storage failover show ::> storage dqp show
bad label:
::> storage disk show -broken
...
1.1.0 bad label ...
1.2.6 bad label ...
label version:
::> storage disk show -broken
...
10b.3.0 label version ...
10b.3.11 label version ...
Resolution
| The following action plan assumes that the disks are not critical data disks being migrated to the new system. Verify that the disks in question do not store production data. |
- Unfailing the drives
- Unfail the drives to return them to the spare pool
::> priv set advanced
::*> storage disk unfail -s <disk_name>
- Repeat the above steps as many times as needed to unfail the remaining drives
- Check to see if the recently unfailed drives show up in the spare pool
::*> storage aggr status -s
- The next step will be to clear the bad label by Zeroing the drives
::*> storage disk zerospares -owner <nodename>
- The bad labels will clear once the disk zero is complete
Additional Information
Common causes for this AutoSupport Message:
| MetroCluster IP- "Bad Label" immediately after running "metrocluster configuration-settings connection connect" | Disk bad label after "metrocluster configuration-settings connection connect" |