SAN bits

Seeing is believing, knowing is everything

Disk issues in Netapp

Leave a comment

Disk issues in Netapp ,where a disk fails and we replace, there are few issues which we face regularly during a disk failure.

we can check a disk failure in Netapp with the following command.

1)filer1>aggr status -f

Broken disks

RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
——— —— ————- —- —- —- —– ————– ————–
failed 2a.33 2a 2 1 FC:B 0 FCAL 15000 418000/856064000 420156/860480768
filer1> priv set advanced
Warning: These advanced commands are potentially dangerous; use
them only when directed to do so by NetApp
personnel.
filer1*> blink_on 2a.33 ( this command makes the failed disk ( which is 2a.33 in this case) to blink with indication.

2)Disk does not get auto assigned after failure.

options disk.auto_assign to on( default)

This does not happen when the auto_assign to off.

you can check the ownership of the disk assignments by using the following command

disk show -o owner_name -v

If you want Data ONTAP to automatically assign disk ownership at the shelf level, set on both the disk.auto_assign and disk.auto_assign_shelf options.

3) disk show -n ( shows unowned disk)
DISK OWNER POOL SERIAL NUMBER HOME
———— ————- —– ————- ————-
2d.71 Not Owned NONE x343xxc43sds43222
filer1> disk assign 2d.71( assigns disk to filer1)
Thu Jul 12 13:07:03 IST [filer1: diskown.changingOwner:info]: changing ownership for disk 2d.71 (S/N x343xxc43sds43222) from unowned (ID 4432423232) to filer1 (ID 15143434)

assigns disk to controller filer1: disk assign 1a.20 -o filer1

Author: kumaraysun

Loves SAN, Learns and works mainly on netapp

Leave a comment