topic Re: Disk replacement, init failed, no physical data in ONTAP Discussions

Disk replacement, init failed, no physical data

JRasi — Wed, 04 Jun 2025 15:23:42 GMT

Replaced a broken disk with a new one.

Now can't recognize MB/blks, RPM or type of the new disk.

Thus, can't assign it.

Disks I'm using are ST3600057SS

> sysconfig -r
Aggregate aggr0 (online, raid_dp) (block checksums)
  Plex /aggr0/plex0 (online, normal, active, pool0)
    RAID group /aggr0/plex0/rg0 (normal)

      RAID Disk Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
      --------- ------          ------------- ---- ---- ---- ----- --------------    --------------
      dparity   0c.00.3         0c    0   3   SA:A   0  SAS  15000 560000/1146880000 560208/1147307688
      parity    0c.00.6         0c    0   6   SA:A   0  SAS  15000 560000/1146880000 560879/1148681096
      data      0c.00.5         0c    0   5   SA:A   0  SAS  15000 560000/1146880000 560208/1147307688
      data      0c.00.10        0c    0   10  SA:A   0  SAS  15000 560000/1146880000 560208/1147307688
      data      0c.00.11        0c    0   11  SA:A   0  SAS  15000 560000/1146880000 560208/1147307688
      data      0c.00.8         0c    0   8   SA:A   0  SAS  15000 560000/1146880000 560208/1147307688
      data      0c.00.9         0c    0   9   SA:A   0  SAS  15000 560000/1146880000 560208/1147307688
      data      0c.00.7         0c    0   7   SA:A   0  SAS  15000 560000/1146880000 560208/1147307688


Pool1 spare disks (empty)

Pool0 spare disks (empty)

Broken disks

RAID Disk       Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------          ------------- ---- ---- ---- ----- --------------    --------------
init failed     0c.00.1         0c    0   1   SA:A   0    ?    ?   ?/?               ?/?

Partner disks

RAID Disk       Device          HA  SHELF BAY CHAN Pool Type  RPM  Used (MB/blks)    Phys (MB/blks)
---------       ------          ------------- ---- ---- ---- ----- --------------    --------------
partner         0c.00.0         0c    0   0   SA:A   0  SAS  15000 0/0               560208/1147307688
partner         0c.00.2         0c    0   2   SA:A   0  SAS  15000 0/0               560208/1147307688
partner         0c.00.4         0c    0   4   SA:A   0  SAS  15000 0/0               560208/1147307688

My Ontap version:

> version -b
/cfcard/x86/freebsd/image1/kernel: OS 8.0.1P5
/cfcard/backup/x86_elf/kernel/primary.krn: OS 7.3.4
/cfcard/x86_elf/diag/diag.krn:  5.4.7
/cfcard/x86_elf/firmware/deux/firmware.img: Firmware 3.1.0
/cfcard/x86_elf/firmware/SB_XIV/firmware.img: BIOS/NABL Firmware 3.0
/cfcard/x86_elf/firmware/SB_XIV/bmc.img: BMC Firmware 1.3
/cfcard/x86_elf/firmware/SB_XVII/firmware.img: BIOS/NABL Firmware 6.1
/cfcard/x86_elf/firmware/SB_XVII/bmc.img: BMC Firmware 1.3
/cfcard/common/firmware/zdi/zdi_fw.zpk: PAM II Firmware 1.10 (Build 0x201012200653)
/cfcard/common/firmware/zdi/zdi_fw.zpk: X1936A FPGA Configuration PROM 1.0 (Build 0x200706131558)

How do I make Ontap see the new disk correctly?

Re: Disk replacement, init failed, no physical data

Naveenpusuluru — Thu, 02 Mar 2017 12:51:57 GMT

Hi @JRasi

You have to update your disk qualification package in-odrder to identify the new version of drives by dataontap. Please go through the below link.

http://mysupport.netapp.com/NOW/download/tools/diskqual/

It contains steps for 7-mode and c-mode and also contains new disk qual pkg to download.

Re: Disk replacement, init failed, no physical data

JRasi — Thu, 02 Mar 2017 13:17:26 GMT

Ok, now I think I've found the correct issue.

There's a more detailed output from: sysconfig -a

        slot 0: SAS Host Adapter 0c (LSI Logic 1068E rev. B3, SAS, <UP>)
                Firmware rev:      1.26.03.00
                Base WWN:          5:00a098:00029d1:00
                Phy State:         [0] Enabled, 3.0 Gb/s
                                   [1] Enabled, 3.0 Gb/s
                                   [2] Enabled, 3.0 Gb/s
                                   [3] Enabled, 3.0 Gb/s
                00.0 : NETAPP   X290_S15K7560A15 NA00 560.0GB 520B/sect (xxxxxxxx)
                00.1 : SEAGATE  ST3600057SS      000B 423.1GB 512B/sect (xxxxxxxx)
                00.2 : NETAPP   X290_S15K7560A15 NA00 560.0GB 520B/sect (xxxxxxxx)
                00.3 : NETAPP   X290_S15K7560A15 NA03 560.0GB 520B/sect (xxxxxxxx)
                00.4 : NETAPP   X290_S15K7560A15 NA00 560.0GB 520B/sect (xxxxxxxx)
                00.5 : NETAPP   X290_S15K7560A15 NA00 560.0GB 520B/sect (xxxxxxxx)
                00.6 : NETAPP   X290_HVIPC560A15 NA01 560.0GB 520B/sect (xxxxxxxx)
                00.7 : NETAPP   X290_S15K7560A15 NA00 560.0GB 520B/sect (xxxxxxxx)
                00.8 : NETAPP   X290_S15K7560A15 NA00 560.0GB 520B/sect (xxxxxxxx)
                00.9 : NETAPP   X290_S15K7560A15 NA00 560.0GB 520B/sect (xxxxxxxx)
                00.10: NETAPP   X290_S15K7560A15 NA03 560.0GB 520B/sect (xxxxxxxx)
                00.11: NETAPP   X290_S15K7560A15 NA00 560.0GB 520B/sect (xxxxxxxx)
                Shelf   0: ESAS  Firmware rev. SAS A: 05 SAS B: 05

The new drive at 00.1 is otherwise identical to the rest of the drives, but has a wrong bytes per sector. The standard 512 Bytes instead of the NetApp proprietary 520 Bytes

It seems I can't use any of these new drives I ordered. ( I ordered a lot to have some in stock in case of the next failure )

So I need to order yet again new ones.