ONTAP Hardware

Bad Disk Label

albertocerpa
82,994 Views

Hi,

I have a FAS250 filer with 14 Seagate 144 GB disks (Drive Part Number: X274_SCHT6146F10). Recently two of the disks failed, so I replaced them with Hitachi 144 GB disks (Drive Part Number: X274_HPYTA146F10), which has the same specs of X274_SCHT6146F10. But when the new disks were inserted, I got the following error messages:

Mon Nov 29 17:37:47 PST [ses.channel.rescanInitiated:info]: Initiating rescan on channel 0b.
Mon Nov 29 17:38:05 PST [raid.disk.inserted:info]: Disk 0b.18 Shelf 1 Bay 2 [NETAPP   X274_HPYTA146F10 NA03] S/N [V5Y692RA] has been inserted into the system
Mon Nov 29 17:38:05 PST [sfu.firmwareUpToDate:info]: Firmware is up-to-date on all disk shelves.
Mon Nov 29 17:38:05 PST [raid.assim.disk.nolabels:error]: Disk 0b.18 Shelf 1 Bay 2 [NETAPP   X274_HPYTA146F10 NA03] S/N [V5Y692RA] has no valid labels. It will be taken out of service to prevent possible data loss.
Mon Nov 29 17:38:05 PST [raid.config.disk.bad.label:error]: Disk 0b.18 Shelf 1 Bay 2 [NETAPP   X274_HPYTA146F10 NA03] S/N [V5Y692RA] has bad label.
Mon Nov 29 17:38:05 PST [disk.fw.downrevWarning:warning]: 2 disks have downrev firmware that you need to update.
Mon Nov 29 17:38:08 PST [asup.post.sent:notice]: System Notification message posted to NetApp: System Notification from fs1 (DISK BAD LABEL) ERROR

I checked the volume status with the command "vol status -r", which outputs the following:

fs1> vol status -r
Volume vol0 (online, raid4) (block checksums)
  Plex /vol0/plex0 (online, normal, active)
    RAID group /vol0/plex0/rg0 (normal)

      RAID Disk    Device    HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      ---------    ------    ------------- ---- ---- ---- ----- --------------    --------------
      parity      0b.28    0b    1   12  FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.17    0b    1   1   FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.22    0b    1   6   FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.19    0b    1   3   FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.20    0b    1   4   FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.21    0b    1   5   FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.29    0b    1   13  FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.23    0b    1   7   FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.24    0b    1   8   FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.25    0b    1   9   FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.26    0b    1   10  FC:B   -  FCAL 10000 136000/278528000  137104/280790184
      data        0b.27    0b    1   11  FC:B   -  FCAL 10000 136000/278528000  137104/280790184


Spare disks (empty)

Broken disks

RAID Disk    Device    HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------    ------    ------------- ---- ---- ---- ----- --------------    --------------
bad label    0b.16    0b    1   0   FC:B   -  FCAL 10000 136000/278528000  137422/281442144
bad label    0b.18    0b    1   2   FC:B   -  FCAL 10000 136000/278528000  137422/281442144

I tried to update the disk firmware with "disk_fw_update", but it gives this error message:

fs1> disk_fw_update 0b.16

    ***** 2 disks have been identified as having an incorrect
    ***** firmware revision level.
    ***** Please consult the man pages for disk_fw_update
    ***** to upgrade the firmware on these disks.

Disk Firmware: No disks in primary FC loop eligible for download

I read the man page as well as the online manual, and I don't seem to find how to resolve the bad disk label error. Is there any way to fix the problem and use the new disks as spares?  Or perhaps these disks are completely incompatible?

Thanks for any help you may provide.

Best regards,

-Al

1 ACCEPTED SOLUTION

scottgelb
82,694 Views

are these netapp oem drives or did you source elsewhere?  "priv set advanced ; disk unfail -s 0b.18" should resolve the bad label  ... then "disk zero spares" to zero the drive so it can be used immediately if needed... if you add to an aggregate it will zero the drive for you but I prefer to pre-zero a disk if not zeroed already.

View solution in original post

14 REPLIES 14
Public