In the CLI, this task is performed with  charray  (see Example 6-19). Select  Delete  to remove the array from the storage pool and delete it. An array MDisk does  not exist outside of a storage pool. Therefore, an array cannot be removed from the pool  without being deleted. All drives that belong to the deleted array return into  Candidate . If there are no volumes that use extents from this array, the command runs immediately  without additional confirmation. If there are volumes that use extents from this array, you are  prompted to confirm the action, as shown in Figure 6-45. Your confirmation of the action triggers the migration of the volumes to extents from other  MDisks that remain in the pool. After the action is completed, the array is removed from the  storage pool and deleted.  Note:  The command fails if you don’t have enough available capacity remaining in the  storage pool to allocate the data that is being migrated from the removed array. To delete the array with the CLI, use  rmarray . The - force  parameter is required if volume  extents need to be migrated to other MDisks in a storage pool. Volumes are entities that are made of extents from a storage pool. The extents of the storage  pool come from various MDisks. A volume can then be spread over multiple MDisks, and  MDisks can serve multiple volumes. Clicking the Dependent Volumes  Action  menu of an  MDisk lists the volumes that are depending on that MDisk as shown in Figure 6-46 on  page 226. Dependent Volumes Chapter 6. Storage pools  225 Figure 6-45 Deleting an array from a non-empty storage pool Example 6-19 Adjusting array goals with charray (some columns are not shown) IBM_Storwize:ITSOV7K:superuser>lsarray mdisk_id mdisk_name status mdisk_grp_id mdisk_grp_name distributed 0 mdisk0 online 0 mdiskgrp0 no 16 Distributed_array online 1 mdiskgrp1 yes IBM_Storwize:ITSOV7K:superuser>charray -sparegoal 2 mdisk0 IBM_Storwize:ITSOV7K:superuser>charray -rebuildareasgoal 0 Distributed_array Delete