Avago Technologies 3ware SAS 9750-16i4e - Manual (Page 94)

Chapter 2. CLI Syntax Reference
86 3ware SATA+SAS RAID Controller Card CLI Guide, Version 10.2
/cx/ux migrate type=RaidType [disk=p:-p]
[group=3|4|5|6|7|8|9|10|11|12|13|14|15|16]
[stripe=size] [noscan] [nocache] [autoverify]
The /cx/ux migrate command allows you to change the existing
configuration of a unit by using type=RaidType. You can make three types of
changes:
• Increase the capacity
• Change the RAID level (with the same or increased capacity)
• Change the stripe size
The unit that results from the migration is subject to the same rules and
policies that apply when creating a new unit with the /cx add command. For
example, you must specify a valid number of disks and parameters.
The unit to be migrated must be in a normal state (not degraded, initializing,
or rebuilding) before starting the migration.
Note: Rapid RAID Recovery is always disabled for units that are migrated.
The destination unit must use all source disks and potentially augment the
number of disks in the disk=p:-p disk list. (An exception to this is when
migrating a RAID 1 to a Single unit. For details, see the following note.)
Unspecified parameters are assigned the default values, is applicable (stripe
size of 256 KB, write cache enabled, autoverify enabled, and ignoreECC
disabled). Both source name and serial number are carried over to the
destination unit.
type=RaidType specifies the RAID type of the destination unit. Possible unit
types include raid0, raid1, raid5, raid6, raid10, raid50, or single.
For example, type=raid5 indicates the destination unit is RAID 5. The
type=single is a special case of the migrate command. It splits the source unit
RAID 1 into two Single units.
Note: A special case of this command occurs when the source unit has a
type of RAID1 and destination unit has a type of Single. In this case, the
migrate command splits both drives into two identical single disks. (If you
do this, unmount the unit first before splitting the drives). The disk name is
duplicated on the destination units, but the source unit serial number is not
carried over to the new unit. The new destination unit has its own serial
number. In this case, the disk-specifier of the migration command
[disk=p:-p] must not be included in the command because the source
drives are the destination drives. Specifying more drives with the disk=
option returns an error.