{{indexmenu_n>10}}

====== Check the Virtual Disk for Errors ======
LaCie RAID Manager can help you maintain optimal performance on a virtual disk using //Consistency check// and //Consistency fix//.

A consistency check scans and reports the integrity of parity or mirrored data on the virtual disk. Periodic consistency checks are highly recommended as part of regular maintenance for virtual disks. Users should also run a consistency check when a virtual disk is not performing as expected.

A consistency fix scans, reports, and fixes parity or mirrored data on the virtual disk. You can choose to run the consistency fix instead of the consistency check if you suspect that your virtual disk is experiencing problems. A consistency fix can take longer to run than a consistency check.

~~pgbreak~~

===== Running a full initialization before running a consistency check/fix =====

As described in [[create|]], LaCie RAID Manager runs an initialization on a virtual disk when it is first created. Similar to a consistency fix, the initialization scans the virtual disk’s hard drives for errors and performs repairs if necessary. There are two types of initialization:
  * **Fast initialization:**  Fast initialization is a destructive process that erases all data on the virtual disk, including the Master Boot Records (MBR) on all physical disks. This is a good option if you wish to perform a cursory consistency check before starting a project.
  * **Full initialization:** A through consistency check of the virtual disk’s hard drives. A full initialization can take many hours to several days based upon the total capacity of the virtual disk.

The option to run a consistency check/fix is available only after a full initialization has been performed on a virtual disk.

~~pgbreak~~

==== Full initializations: background and foreground ====

A full initialization can be run as one of the following: 
  * **Background initialization:** A thorough, non-destructive consistency check of the physical disks. Since it runs in the background, the demand on the processor is reduced when compared with a foreground initialization. However, performance can be impacted, especially when working on high-end video or graphic projects. A background initialization can take many hours to several days based upon the total capacity of the virtual disk.
  * **Foreground initialization:** This option is similar to a fast initialization since the MBR for all the physical disks are erased. Therefore, it is also a destructive process. Since it performs a thorough consistency check, this option can take many hours to several days based upon the total capacity of the virtual disk. As its name indicates, a foreground initialization runs in the foreground and can take a good amount of processing power which will affect performance. Choose foreground initialization when you want you want to wipe the hard drives and you do not anticipate starting high-end video or graphic projects within the week.

~~pgbreak~~

===== Performing a consistency check/fix =====

Follow the instructions below to run a consistency check/fix:
  - Choose the virtual disk in the Storage pane and roll over the Operation tab. \\ {{:products:raid-manager:screenshots:ss-lrm-consistency-check-01.jpg?700|}} \\ 
  - Choose **Consistency Check**.
  - In the pull-down menu, select **Consistency Check** or **Consistency Fix**. \\ {{:products:raid-manager:screenshots:ss-lrm-consistency-check-02.jpg?700|}} \\ 
  - Choose **Submit**

The consistency check/fix will take many hours to several days based upon the total capacity of the virtual disk. You can continue to use the hard drives but performance can be affected by the consistency check/fix. \\ {{:products:raid-manager:screenshots:ss-lrm-consistency-check-02.jpg?700|}}

~~pgbreak~~

===== Scheduling a consistency check/fix or background initialization =====

LaCie RAID Manager gives you the option to schedule regular consistency checks/fixes and background initializations. Regular maintenance on the hard drives can help to prevent data errors and improve the health of the virtual disk.
  - Choose the virtual disk in the Storage pane and roll over the Operation tab. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-01.jpg?700|}} \\ 
  - Choose **Initialization** or **Consistency Check**.
  - Click on the pull-down menu to choose:
    * **Consistency Check** or **Consistency Fix**. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-02a.jpg?700|}} \\ 
    * **Background Initialization**. **Note:** The option for a foreground initialization is not available when a full initialization has been performed on the virtual disk. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-02b.jpg?700|}} \\ 
  - Choose **Schedule**. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-03.jpg?700|}} \\ 
  - Select the frequency and choose **Submit**. See below for scheduling options.

~~pgbreak~~

==== Scheduling options ====
{{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-04.jpg?700|}} \\ 

Consistency checks/fixes and initializations can be scheduled:
  * **Only once:** Click on the calendar icon to choose a time and enter the time in the **Start time** field. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-04a.jpg?700|}} \\ 
  * **Daily:** Choose the frequency and enter the time in the **Start time** field. For example, //Recur every **1** day(s)// or //Recur every **3** day(s)//. The former will run each day and the latter will run every three days. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-04b.jpg?700|}} \\ 
  * **Weekly**: Choose the frequency, day of the week, and enter the time in the **Start time** field. For example, //Recur every **1** week(s)// or //Recur every **3** week(s)//. The former will run once a week and the latter will run once every three weeks. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-04c.jpg?700|}} \\ 
  * **Monthly**: Choose the day of the month, the frequency, and enter the time in the **Start time** field. For example, //Recur day **1** of every **1** month(s)// or //Recur day **28** of every **3** month(s)//. The former will run once a month on the first day of the month. The latter will run once every three months on the twenty-eighth day of the month. To avoid potential confusion with certain months, it is recommended that you choose a date between 1 - 28. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-04d.jpg?700|}}

~~pgbreak~~

===== Reviewing scheduled consistency checks/fixes and initializations =====
To see scheduled operations, go to the Storage pane and choose **Management > BGA Schedule Setting**. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-05.jpg?700|}} \\ 

==== Deleting scheduled consistency checks/fixes and initializations ====
  - Go to the Storage pane and choose **Management > BGA Schedule Setting**.
  - Click on the check box for the operation you want to delete. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-05.jpg?700|}} \\ 
  - Choose **Delete**. \\ {{:products:raid-manager:screenshots:ss-lrm-schedule-consistency-06.jpg?700|}}