The Intel® VROC production package for Windows* is broken into Pre-OS components, F6 (or Load Driver) components, an operating system installer (Intel® VROC Installation Utility) and a Command Line Interface (CLI) component (Intel® VROC CLI Utility). Whereas the operating system installer and the CLI components are common for all Intel® VROC sub-products, there are specific Pre-OS and F6 components for the Intel® VROC (SATA RAID) environment.
The Pre-OS components for the Intel® VROC (SATA RAID) environment are described below. To learn about the Pre-OS components for Intel® VROC (VMD NVMe* RAID), refer to Intel® Virtual RAID on CPU (Intel® VROC) VMD NVMe* RAID Pre-OS Components.
Intel® VROC Package Components | The Intel® VROC Pre-OS components are part of the Intel® VROC software package for Windows*. Learn about other package components in the Intel® Virtual RAID on CPU (Intel® VROC) Technical Product Specification for Windows*. |
These are the UEFI device drivers to support the SATA/sSATA controller when configured for RAID mode. These files are to be included in the platform BIOS. When properly incorporated, they will provide the ability to manage SATA/sSATA/tSATA drives (create/delete RAID volumes) connected to the SATA/sSATA/tSATA controller. Other features included are:
These are UEFI based tools that can be used to test SGPIO LED connections to determine if the hardware is set up correctly. These utilities must be copied to and executed from a USB key in a UEFI shell.
These tools must match the major release version of the Intel® VROC (SATA RAID) UEFI driver. To find the release version:
By using a FAT32 formatted USB device, users can download any release of this tool that matches the major release of Intel® VROC (SATA RAID) UEFI driver found in the previous steps:
The tool syntax is described below. Each parameter is described in the following table.
Parameter | Description |
/?, /HELP | Displays the help screen. Other options are ignored. |
/D | Send the specified state to all ports. /D0-5 option will be ignored. |
/D0-5 | Send the specified state to the selected port. Valid state numbers are from 0 to 5, and they are interpreted as follows: 0 = NO_DISK, 1 = NO_ACTIVITY, 2 = ACTIVITY, 3 = LOCATE, 4 = FAIL, 5 = REBUILD. |
/TIMEOUT | After sending the states, it waits the specified number of seconds and then turns off all LEDs and performs a reset of the message sending logic. |
Note | After a reset, the first sent state will turn on all other LEDs. |
An example command is the following:
This command will set the state NO_DISK on port 2 and the state ACTIVITY on port 0. After a 2-seconds delay, messages will be reset.
These utilities can be used by platform manufacturers to manage/test Intel® VROC (SATA RAID) capabilities from a UEFI shell environment. These utilities must be copied to and executed from a USB key in a UEFI shell.
These tools must match the major release version of the Intel® VROC (SATA RAID) UEFI driver. By using a FAT32 formatted USB device, users can download any release of this tool that matches the major release of Intel® VROC (SATA RAID) UEFI driver found in the section above:
The output from this EFI tool can also be saved in a text file (such as RCfgSata.efi /I > RCfgSata_Output.txt).
These are debug utilities to help verify that the SATA/sSATA/tSATA EFI drivers have been properly configured and incorporated into the BIOS. When reporting an issue to Intel, the output from this file will most likely be asked by the Intel representative. These utilities must be copied to and executed from a USB key in a UEFI shell.
These tools must match the major release version of the Intel® VROC (SATA RAID) UEFI driver. By using a FAT32 formatted USB device, users can download any release of this tool that matches the major release of Intel® VROC (SATA RAID) UEFI driver found in the section above:
The output from this EFI tool can also be saved in a text file (such as RCmpSata.efi > RCmpSata_Output.txt).
These utilities will clear off any RAID metadata from a SATA drive attached to the SATA/sSATA/tSATA controller. This will basically wipe out any data that is on the drive that this tool is executed on. So great care must be taken. These utilities must be copied to and executed from a USB key in a UEFI shell.