Intel® Virtual RAID on CPU (Intel® VROC) Troubleshooting Tips for Various Volume States in Windows* Environments

Use this information to troubleshoot issues related to volumes reporting various states other than Degraded or Failed by Intel® VROC in Windows* environments. See additional troubleshooting tips in Troubleshooting Tips for Intel® Virtual RAID on CPU (Intel® VROC) in Windows* Environments.

Degraded or Failed States

Refer to the resources below for troubleshooting tips specifically for failed or degraded RAID volumes:

• Intel® Virtual RAID on CPU (Intel® VROC) Troubleshooting Tips for Failed Volumes in Windows* Environments
• Intel® Virtual RAID on CPU (Intel® VROC) Troubleshooting Tips for Degraded Volumes in Windows* Environments

Incompatible State

Follow the below recommendations for the given scenario.

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

In this situation, the volume data is accessible to the operating system and can be backed up, but the volume cannot operate because the system does not support its RAID configuration. In such a scenario, the available options to proceed are:

• 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. When a volume is deleted, all existing data on the member disks of the selected volume is permanently erased. It is recommended that the user backup all valuable data prior to beginning this action.

Indicates that the Intel® VROC upgrade key is incorrect or missing

In this situation, the volume data may not be accessible to the operating system. In such a scenario, the available option to proceed is:

• Install the proper Intel® VROC upgrade key. See more information in Intel® Virtual RAID on CPU (Intel® VROC) SKUs and Licensing.

Unknown State

Follow the below recommendations for the given scenario.

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

The application is unable to detect the exact nature of the problem. Try restarting the system. If the error persists, back up all valuable data and delete the volume from the UEFI HII. Refer to the system vendor manual for details on navigating through the UEFI HII menus.

Missing Volume State

Follow the below recommendations for the given scenario.

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

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:

• Creation of a system volume or data volume while preserving data
• Volume type change combined with disk addition to the new RAID configuration
• Volume size increase
• Disk addition to an existing array

Depending on the type of drive/volume (data or system), follow the recommendations below.

Troubleshooting a Data Volume

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. Once the operation has completed, restart the system. Use the Intel® VROC Graphical User Interface (GUI) application to 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 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 with a compatible driver version.
4. 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 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.
3. Return the corrupted volume disks to the original system and try booting.