ONTAP Hardware

4243 shows "?" for shelf and bay

networkadminz
3,473 Views

Good day!  I am working though a reconfigure of a FAS 2040 + DS4243 (you may recognize this as I was posting other questions under another user ID recently).  I have just finished adding 1TB drives into the DS 4243 and they are all functioning properly in RAID-DP from the shelf.  I haven't been able to clear our the amber warning lights yet although all drives are alive and hosting CIFS data (just test data for now)  All drives "0d" are from the 4243 shelf and "0c" are the internal drives from the 2040.  Whats the best way to figure this one out?

Aggregate aggr0 (online, raid4) (block checksums)

  Plex /aggr0/plex0 (online, normal, active)

    RAID group /aggr0/plex0/rg0 (normal)

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

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

      parity    0c.00.1         0c    0   1   SA:A   -  SATA  7200 423111/866531584  423946/868242816

      data      0c.00.2         0c    0   2   SA:A   -  SATA  7200 423111/866531584  423946/868242816

Aggregate aggr1 (online, raid_dp) (block checksums)

  Plex /aggr1/plex0 (online, normal, active)

    RAID group /aggr1/plex0/rg0 (normal)

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

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

      dparity   0d.01.9         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      parity    0d.01.8         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.10        0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.7         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.6         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.5         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.4         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.3         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.2         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.1         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

      data      0d.01.0         0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816

Spare disks

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

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

Spare disks for block or zoned checksum traditional volumes or aggregates

spare           0c.00.0         0c    0   0   SA:A   -  SATA  7200 423111/866531584  423946/868242816 (not zeroed)

spare           0d.01.11        0d    ?   ?   SA:B   -  SATA  7200 847555/1735794176 847884/1736466816 (not zeroed)

Partner disks

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

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

partner         0c.00.10        0c    0   10  SA:A   -  SATA  7200 0/0               423946/868242816

partner         0c.00.9         0c    0   9   SA:A   -  SATA  7200 0/0               423946/868242816

partner         0c.00.11        0c    0   11  SA:A   -  SATA  7200 0/0               423946/868242816

sv-storage-1a> Thu May 15 12:00:00 CDT [sv-storage-1a: kern.uptime.filer:info]:  12:00pm up  1:05 0 NFS ops, 36 CIF S ops, 0 HTTP ops, 0 FCP ops, 0 iSCSI ops

1 REPLY 1

JGPSHNTAP
3,319 Views

First you should zero your spares..

(disk zero spares)

Try led_off and see if that will hold the service light off

Public