barren escarp
Disk name shows as <node name>:<0a.1.1> format.
Referred few kb's, suggestions were to update DQP.
But the label remains the same. Planned to try remove ownership and assign to check.
These are new addition to the nodes and isolated to one shef drives. Shelf itself was repurposed.
Pour your taughts, please
undone prism
if the label is simply bad, a disk unfail -s in the nodeshell might do the trick. If the label is, however, from a newer ONTAP you're out of luck. In that case your only chance is to put the disk into a newer ONTAP and mark it as a spare there. Spares can be used in any ONTAP, but if disks still have data on them you cannot plug them into lower-version ONTAP systems. In that case you should see messages about "RAID version mismatch" or something in the log
scenic pilot
The disk id showing as nodename:0a.1.1 can have multiple causes in addition to DQP.
I've seen it when unsupported shelves were on the system (ex IOM3 on modern ONTAP).
IIRC, duplicate shelf IDs show the disk id as nodename:0a.SHELF_SN.1, but I'd double check the shelf id as well.
stiff pivot
It would help to know where the disk came from..
Have you done labelmaint isolate/wipe?
craggy oyster
I’ve read when you see this that a takeover and giveback in both directions may help
undone prism
Have you done labelmaint isolate/wipe?
I'm not sure that is a command that you want your customers to use 😉 it can be quite destructive
stiff pivot
It sure can be, but if you’re getting bad labels it’s sometimes the only option
scenic pilot
I'm not convinced this is actually a bad disk label. I'd like to see a sysconfig -v output and see what it thinks about these disks/shelves.