If you have CEIP (Customer Experience Improvement Program) enabled and controller vendor utility(storcli/perccli) is available, a vSAN online health check RAID controller configuration validates the recommended controller settings and displays the health status.
Follow the steps below to configure the settings on your controller:
Place the host into maintenance mode with Full Data Migration.
If there are not enough hosts to accommodate Full Data Migration, use Ensure Accessibility (with the various standard warnings about exposure to data loss, etc.)
Delete the disk groups.
Reboot the host.
Reconfigure the storage controller according to the manufacturer’s documentation. Please follow these guidelines below to configure the settings:
No cache (or read cache only if cache cannot be disabled)
Pass-through/JBOD mode
Do not use a mixed RAID+ pass-through personality. Only use the pass-through personality if applicable.
After boot, re-create the disk groups.
Exit maintenance mode.
Repeat as needed on the remaining hosts.
Note: To configure the recommended settings, you can use a CLI command from the corresponding controller vendor, such as storcli for LSI controllers and perccli for the Dell H710 controller.
Creating the RAID0 volumes and configuring the recommended settings:
Follow the steps below to create the RAID0 volumes with the recommended configuration settings. These instructions on how to apply the recommended settings using the LSI storcli CLI utilities. For Dell controllers, use perccli.
Note: The working directory for all the commands listed in this procedure is /opt/lsi/storcli. Therefore, execute the command cd /opt/lsi/storcli on the ESX host before performing step 1.
Determine the adapter number of the HBA on which the logical drive will be created. (For this step, assume that we are using a LSI 9271 HBA):
Run this command:
./storcli /call show
In the output, look for similar entries as shown in this sample output:
Generating detailed summary of the adapter, it may take a while to complete.
Controller = 0 <---------------This gives us the controller number Status = Success Description = None
Product Name = LSI MegaRAID SAS 9271-8i Serial Number = SV40318544 SAS Address = 500605b0075888c0 PCI Address = 00:03:00:00 System Time = 03/18/2015 21:30:06
The sample output shows that the LSI 9271 is controller 0. This is the value being referred to when using the controller_number in the following commands.
Determine the enclosure ID and the slot number of the disks where the HBA is connected:
Run this command:
./storcli /call show
In the output, look for the PD List table as shown in this sample:
PD LIST : ======= ---------------------------------------------------------------------------- EID:Slt DID State DG Size Intf Med SED PI SeSz Model Sp ---------------------------------------------------------------------------- 252:0 9 UGood - 465.25 GB SAS HDD N N 512B ST9500620SS D 252:1 18 Onln 1 185.781 GB SATA SSD N N 512B INTEL SSDSC2BA200G3 U 252:2 15 Onln 2 418.656 GB SAS HDD N Y 512B HUC106045CSS600 U
The first column lists the physical drives in the format enclosure_id:slot_number . This provides the enclosure_id and slot_number you will use in the next steps.
Decide the physical drive to use to create the logical volume:
Refer to the PD List table generated in Step 2.
Any drive with a status of UGood is available for creating a logical volume. Drives with a status of Onln are already in use by logical volumes and unavailable.
Select the drive with status of UGood to use. The slot_numberof that drive is what you will use in step 4.
Create the logical volume with the appropriate configuration:
If it is a HDD, run this command:
./storcli /ccontroller_number add vd type=raid0 name=virtual_drive_name drive=enclosure_id:slot_number ra wt direct strip=256
Example:
Command using the drive in the PD LIST output:
./storcli /c0 add vd type=raid0 name=HDD-S0 drive=252:0 ra wt direct strip=256
Disclaimer: VMware is not responsible for the reliability of any data, opinions, advice, or statements made on third-party websites. Inclusion of such links does not imply that VMware endorses, recommends, or accepts any responsibility for the content of such sites