Handling NetApp Disk Label Version Too High

1. When the disk label version is too high, the following prompt appears when adding the disk:

Tue May 22 00:30:10 CST [sc-gxfc2050-A: raid.assim.disk.badlabelversion:error]: Disk 0c.01.14 Shelf 1 Bay 14 [NETAPP   X287_HVPBP288A15 NA00] S/N [JLVA02EC] has raid label with version (9), which is not within the currently supported range (5 - 8). Please contact Network Appliance Global Services.

Tue May 22 00:30:10 CST [sc-gxfc2050-A: raid.config.disk.bad.label.version:error]: Disk 0c.01.14 Shelf 1 Bay 14 [NETAPP   X287_HVPBP288A15 NA00] S/N [JLVA02EC] has an unsupported label version.

1. After modifying sysid and running the sysconfig –r command, the following bad disk information is displayed:

Broken disks

RAID Disk       Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)

---------       ------          ------------- ---- ---- ---- ----- --------------    --------------

label version   0c.01.12        0c    1   12  SA:1   -  SAS  15000 272000/557056000  274845/562884296

label version   0c.01.13        0c    1   13  SA:1   -  SAS  15000 272000/557056000  274845/562884296

label version   0c.01.14        0c    1   14  SA:1   -  SAS  15000 272000/557056000  274845/562884296

label version   0c.01.16        0c    1   16  SA:1   -  SAS  15000 272000/557056000  274845/562884296

label version   0c.01.17        0c    1   17  SA:1   -  SAS  15000 272000/557056000  274845/562884296

1. Cause

According to documentation, this occurs because the current Data ONTAP system version is lower than the system version currently used by the disk. For example, DOT 8.0 corresponds to value 10, 7.3 corresponds to value 9, and versions below 7.3 correspond to values 5–8.

The disk label version you are currently seeing is 9, which indicates the disk was previously used on a system running 7.3 or later and was removed directly without clearing the RAID label version.

For instance, if your current system is 7.2.6 or 7.2.4, the aforementioned disks cannot be recognized normally.

1. Solutions include:
2. Upgrade the existing DOT 7.2.4/DOT 7.2.6 system to directly support disks with label version 9. (Depending on your production environment, this method may not be feasible.)
3. Downgrade the disk's label version. (When a disk is added to an aggregate, it writes a RAID label version value; when the disk becomes a spare, the RAID label version becomes 0.) Refer to the detailed method below:
4. Find a system running version 7.3 or higher, such as 7.3.5 (which supports label version 9), and insert the disk into an empty slot of the same disk type (e.g., your company's FAS2050 test machine).
5. >sysconfig (view sysid)
6. >disk assign disk_id –s new_sysid –f (assign the disk to the new head unit)
7. >sysconfig –r (verify that the disk is now a spare)

-----At this point, in priv set diag mode, you can also view the spare disk label version as 0 via label summary.

v5.20:  :Invalid Label!

CRC 0x9d94b571, mgc 0x0, lbl V0, sz 0 , flags 0x0

        SPARE

1. >disk remove_ownership disk_id (remove the disk's ownership)
2. >disk remove disk_id (remove the spare disk)
3. Remove the spare disk.
4. If there are multiple disks, repeat the steps above.
5. Another method is to perform operations in system maintenance mode:
6. Find a system running version 7.3 or higher, such as 7.3.5 (which supports label version 9), and insert the disk into an empty slot of the same disk type (e.g., your company's FAS2050 test machine).
7. Shut down the system, then boot up. When prompted with Ctrl+C for boot menu, press Ctrl + C to enter the boot menu, then press number 5 to enter maintenance mode.
8. >label makespare disk_id (force the disk to become a spare; this command can be repeated for multiple newly added disks)
9. >label summary (verify whether the label version has become 0)
10. >disk remove_ownership (remove ownership)
11. >disk remove disk_id (remove the spare disk)
12. Remove the disk.