ONTAP Discussions

OLD SCHOOL HELP PLEASE! Replacement disk has no valid labels. It will be taken out of service....

BeeKay
6,611 Views

Anyone have steps on how to prep a previously used (NetApp) disk with the v7.2.4 ONTAP ?

I am looking for the steps to relabel replacement "used" disks, under ONTAP 7.2.4.  (I know, I know!)

 

Sure enough, I lost two disks in two separate arrays (all within a 4 day time period!)

The Controller shut itself down before I could fly out to replace the disks.

 

I swapped out the disks with "refurbished" ones from ServerSupply, and went into Maintenance Mode.

Performed "disk assign all" and restarted.

 

I ran "aggr status -f" because all of the new disks complain about not having any valid labels!

*> aggr status -f
Thu Apr 4 20:31:14 GMT [raid.assim.disk.nolabels:error]: Disk 0c.35 Shelf 2 Bay 3 [NETAPP X279_HVIPB288F15 NA01] S/N [J8WM0PEC] has no valid labels. It will be taken out of service to prevent possible data loss.
Thu Apr 4 20:31:14 GMT [raid.assim.disk.nolabels:error]: Disk 0b.59 Shelf 3 Bay 11 [NETAPP X279_HVIPB288F15 NA01] S/N [J8WEGPHC] has no valid labels. It will be taken out of service to prevent possible data loss.
Thu Apr 4 20:31:15 GMT [raid.assim.disk.nolabels:error]: Disk 0b.54 Shelf 3 Bay 6 [NETAPP X279_HVIPB288F15 NA01] S/N [J8WHSSPC] has no valid labels. It will be taken out of service to prevent possible data loss.
Thu Apr 4 20:31:15 GMT [raid.assim.disk.nolabels:error]: Disk 0b.42 Shelf 2 Bay 10 [NETAPP X279_HVIPB288F15 NA01] S/N [J8WKVY2C] has no valid labels. It will be taken out of service to prevent possible data loss.
Thu Apr 4 20:31:15 GMT [raid.config.disk.bad.label:error]: Disk 0c.35 Shelf 2 Bay 3 [NETAPP X279_HVIPB288F15 NA01] S/N [J8WM0PEC] has bad label.
Thu Apr 4 20:31:15 GMT [raid.config.disk.bad.label:error]: Disk 0b.59 Shelf 3 Bay 11 [NETAPP X279_HVIPB288F15 NA01] S/N [J8WEGPHC] has bad label.
Thu Apr 4 20:31:15 GMT [raid.config.disk.bad.label:error]: Disk 0b.54 Shelf 3 Bay 6 [NETAPP X279_HVIPB288F15 NA01] S/N [J8WHSSPC] has bad label.
Thu Apr 4 20:31:15 GMT [raid.config.disk.bad.label:error]: Disk 0b.42 Shelf 2 Bay 10 [NETAPP X279_HVIPB288F15 NA01] S/N [J8WKVY2C] has bad label.

Broken disks

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- -------------- --------------
bad label 0b.42 0b 2 10 FC:B - FCAL 15000 272000/557056000 274845/562884296
bad label 0b.54 0b 3 6 FC:B - FCAL 15000 272000/557056000 274845/562884296
bad label 0b.59 0b 3 11 FC:B - FCAL 15000 272000/557056000 274845/562884296
bad label 0c.35 0c 2 3 FC:A - FCAL 15000 272000/557056000 274845/562884296
No root aggregate or root traditional volume found.
You must specify a root aggregate or traditional volume with
"aggr options <name> root" before rebooting the system.

 

I don't know what the commands should be to force a new label, my Pool is Pool0, my owner is file01.

Not sure what else it is looking for.

 

IMPORTANT - I AM IN MAINTENANCE MODE, and unable to work, so a quick response would be very welcome!

 

Thanks everyone!

 

 

4 REPLIES 4

cedric_renauld
6,533 Views

Hello, 

You can find some informations in theis KB : https://kb.netapp.com/app/answers/answer_view/a_id/1006225/~/disk-label-version-error-or-bad-label-version-error-

 

The right question is wath's your actual Ontap version ? before 8.0.2 ? or after ...

And, have you some data on your disk ?

 

Cedric

 

BeeKay
6,381 Views

@cedric_renauld wrote:

Hello, 

You can find some informations in theis KB : https://kb.netapp.com/app/answers/answer_view/a_id/1006225/~/disk-label-version-error-or-bad-label-version-error-

 

The right question is wath's your actual Ontap version ? before 8.0.2 ? or after ...

And, have you some data on your disk ?

 

Cedric

 


My version is 7.2.4.  The replacement drive versions are "unknown."  Is there any other workaround to getting these disks operational?

cedric_renauld
6,334 Views

Hello, 

 

you can try this workaround :

disk assign <diskid>

priv set diag

labelmaint isolate <diskid>

label wipe <diskid>

label wipev1 <diskid>

label makespare <diskid>

labelmaint unisolate

priv set

 

Be carefull about disk number 🙂

 

See in this post :

https://community.netapp.com/t5/FAS-and-V-Series-Storage-Systems-Discussions/Bad-Disk-Label/td-p/74706 

liuh
111 Views

hi

The reason why the controller shuts down is that if two or more faulty disks exist, the system will break down. You need to restart the device, check whether the system is running properly, and replace the hard disk with a new one. Then check the system running status to ensure that the system is running properly

Public