Skip to main content
NetApp Knowledge Base

What are the conditions for disk auto-assign failure to automatically assign disk ownership to storage systems?

Last Updated:


Applies to

Clustered Data ONTAP 8


Although disk.auto_assign option (storage disk option modify - autoassign in clustered Data ONTAP) is set to ON, Data ONTAP is unable to automatically assign a newly-inserted disk to the storage system.


The following conditions prevent Data ONTAP from automatically assigning disk ownership to a storage system:

When the disk to be assigned ownership is on a fiber channel loop, SAS stack, or fabric that contains disks that are:

  • Owned by multiple systems (more than one node has ownership of disks on this loop or stack)

    The following message will indicate that the auto-assign has failed:

    Wed Feb 20 12:51:36 GMT [FilerA: sanown_reservation: diskown.AutoAssign.MultipleOwners: warning]: Automatic assigning failed for disk 0a.01.5 (S/N WD-AAAA12345678) because the disks on the loop are owned by multiple systems. Automatic assigning failed for all unowned disks on this loop.

  • Assigned to different pools (this loop or stack contains disks assigned to Pool0 and Pool1)


  • Not owned by any system (all disks on this loop or stack are unowned) 

Should any of these conditions exist, disk.auto_assign option though set to ON, fails to work and Data ONTAP will not be able to determine the storage system to assign disk ownership.

For 7-Mode controllers, if auto_assign failed to assign the disk manually, verify with disk show -n to see which disk is not assigned. Then use the disk assign command. For details, see the Storage Management Guide of your Data ONTAP release

For clustered Data ONTAP, run the storage disk show command to verify the unassigned disks. See the clustered Data ONTAP Physical storage Management Guide for further details.


Additional Information