Other volume states

Incompatible

Cause 1

Indicates that the volume was moved to another system that does not support the volume type and configuration.

Solution 1

In this situation, volume data is accessible to the operating system and can be backed up, but the volume cannot operate because the user’s system does not support its RAID configuration.

Here are the user’s options:

  • Reconnect the volume to the computer where the volume was originally created, and continue using it.

  • Delete the volume, and then create a new volume with a RAID configuration that is supported by the current system. Follow the procedure described above to delete the volume.

WARNING:

When a volume is deleted, all existing data on the member disks of the selected volume is permanently erased. It’s recommended that the user backup all valuable data prior to beginning this action.

Cause 2

Indicates that the Intel VROC Upgrade Key is incorrect or missing.

Solution 2

In this situation, volume data may not be accessible to the operating system. The user’s option is to install the proper Intel VROC Upgrade Key.

Unknown

Cause

The volume is in an unexpected state due to a configuration error.

Solution

The application is unable to detect the exact nature of the problem. Try restarting the user’s computer. If the error persists, back up all valuable data and delete the volume using the option ROM user interface. See the user’s manual accessible from the Online Support area for details on using the option ROM.

Missing volume

Cause

A driver upgrade or downgrade was performed while a data migration was in progress.

Solution

The driver cannot recognize the volume or read its data if a driver upgrade or downgrade was performed during a volume migration. Volume migrations occur after one of the following operations was initiated:

  1. Creation of a system volume or data volume while preserving data.

  2. Volume type change combined with disk addition to the new RAID configuration.

  3. Volume size increase.

  4. Disk addition to an existing array.

Troubleshooting a data volume

  1. If the data migration involved a data volume, the user will need to reverse the driver upgrade or downgrade operation and return to the original driver version. This will restore driver and volume compatibility.

  2. Once the operation has completed, restart the user’s computer.

  3. Open the application and make sure that the volume displays again in the storage system view. Data migration operation should resume immediately.

Troubleshooting a system disk

If the data migration involved a system disk or volume, it is highly likely that the user will not be able to start the user’s system because the driver cannot read the system files. The following options may allow the user to load the operating system again:

  1. Restore to the last known good configuration.

  2. Boot from a flash drive that supports NTFS partitioning and includes the storage driver files.

  3. Bring the corrupt disk to another system, and then replace the storage driver files from a compatible driver version. Return the disk to the original system and try booting.

Troubleshooting a system volume

If the data migration involved a system disk or volume, it is highly likely that the user will not be able to start the user’s system because the driver cannot read the system files. The following options may allow the user to load the operating system again:

  1. Restore the last known good configuration.

  2. Bring all corrupted volume disks to another system, and then replace the storage driver files from a compatible driver version. Return the corrupted volume disks to the original system and try booting.