Chapter 2. CLI Syntax Reference73 3ware SAS/SATA RAID Controller CLI Guide, Version 9.5.22 = faster I/O; slower verify1 = fastest I/O; slowest verifyFor 9550SX(U) and earlier controllers, and for SE/SA controllers runningfirmware 9.5 and 9.5.0.1, disabling verify with this command turns off theverify schedule. In this case, if a verify is manually started, it should beginright away.For 9650SE and 9690SA controllers running firmware 9.5.1 or later, enablingverify with this command is equivalent to using the /cx set verify=advancedcommand, while disabling verify with this command is equivalent to using the/cx set verify=basic command without specifying a preferred start day andtime (the default of Friday at midnight is used.) For more information, see “/cx set verify=advanced|basic|1..5” on page 73.You can view the verify schedule to be enabled or disabled with the command“/cx show verify” on page 55. You can add verify task slots to the scheduleusing the command “/cx add verify=ddd:hh:duration” on page 67. You canremove verify task slots from the schedule with the “/cx del verify=slot_id”on page 69./cx set verify=advanced|basic|1..5This command only applies to 9650SE and the 9690SA RAID controllersrunning 9.5.1 or later.This command is effectively the same as the set verify command. Settingverify to advanced enables the advanced Verify Task Schedule, which caninclude a series of up to 7 days and times. Setting verify to basic creates aweekly schedule with one specific day and time, and disables the series ofscheduling slots associated with the advanced Verify Task Schedule. For moreabout the basic schedule, see “/cx set verify=basic [pref=ddd:hh]”, below.The priority of verify versus I/O operations is specified with 1..5, where 5 ismore resources and 1 the least. Setting this value to 1 implies fastest I/O, and5 implies fastest verify.Note: In previous versions of the CLI, 1 was incorrectly reported to be the fastestverify rate, and 5 was incorrectly reported to be the slowest—the opposite of theactual settings. In 9.5.2, the scale is reported correctly, as described above, with 5the fastest verify rate.Note: If you want verifications to occur automatically, when enabling the verifyschedule you must also remember to enable the autoverify setting for the units to beverified. For more information see “/cx/ux set autoverify=on|off” on page 92.