- Notes, cautions, and warnings
- Overview
- Physical Disks
- Virtual Disks
- Cabling the drives for S140
- BIOS Configuration Utility
- Entering the BIOS configuration utility
- Exiting the BIOS Configuration Utility
- Initializing the physical disks
- Creating the virtual disks
- Deleting the virtual disks
- Swapping two virtual disks
- Managing the hot spare disks
- Viewing the physical disks details
- Viewing the virtual disks details
- Rescan disks
- Controller Options
- Continue to boot
- UEFI RAID configuration utility
- Installing the drivers
- Troubleshooting your system
- Precautions for hot removal or hot insertion of NVMe drives
- Unable to configure Linux RAID using UEFI Configuration Utility
- Performance degradation after disabling SATA physical disk write cache policy
- Unable to modify any feature settings in UEFI or OPROM
- Extra reboot during OS installation
- After enabling Hypervisor, system displays Blue Screen of Death
- After enabling node interleaving in BIOS, system displays Blue Screen of Death
- OS installation failing on NVMe PCIe SSD with third-party driver
- System startup issues
- System does not boot
- Controller mode is set incorrectly at system setup
- Boot mode, boot sequence, and or boot sequence retry are set incorrectly
- Bootable virtual disk is in a failed state
- The boot order is incorrect for a bootable virtual disk
- A Non-RAID virtual disk is no longer in first position in the BIOS configuration utility list after a system reboot
- The BIOS configuration utility option does not display
- Configuring RAID using the ROM Utility option is disabled
- Warning Messages
- Other errors appearing on the BIOS screen
- BSOD is observed while booting on the NVMe configuration server
- Failure of dump file creation
- S140 does not display greater than ten virtual disks in the BIOS Configuration Utility or CTRL R
- Unable to delete virtual disks when there are more than 30 virtual disks present in the system
- Virtual disk rebuild status in the BIOS Configuration Utility (<CTRL><R>) or in UEFI HII
- Physical disk - related errors
- The physical disk fails
- Cannot initialize a physical disk
- Behavior of a faulty drive is undefined
- Status LED is not working
- Blinking and unblinking feature not working on PowerEdge R740
- Cannot update NVMe PCIe SSD firmware by using Dell Update Package or DUP
- Third-party driver installation for NVMe PCIe SSD failing
- The vendor's name is not displayed in Physical Disk Properties when using Micron RI and MU drives
- Unable to find the NVMe PCIe SSD for operating system installation
- Virtual disks - related errors
- Stale partitions are listed on creating a virtual disk for Linux
- Rebuilding a virtual disk the global hot spare is not listed as online in HII or iDRAC
- Virtual disk size in decimals is not supported while creating a VD
- Cannot create a virtual disk
- A virtual disk is in a degraded state
- Cannot assign a dedicated hot spare to a virtual disk
- Cannot create a global hot spare
- A dedicated hot spare fails
- Failed or degraded virtual disk
- Cannot create a virtual disk on selected physical disks
- RAID disk created from the NVMe PCIe SSDs not appearing in operating system environment, showing as partitioned disks
- Cannot perform an online capacity expansion or reconfigure on a virtual disk
- Unable to configure RAID on NVMe PCIe SSD using a third party RAID configuration utility
- S140 config driver is not installed after S140 DUP is run
- Getting help
- Documentation resources
Dell PowerEdge RAID Controller S140 User’s Guide
Consistency check
Consistency check (CC) is a background operation that verifies and corrects the mirror or parity data for fault-tolerant physical disks. It is recommended that you periodically run a consistency check on the physical disks.
By default, CC corrects mirror or parity inconsistencies. After the data is corrected, the data on the primary physical disk in a mirror set is assumed to be the correct data and is written to the secondary physical disk mirror set.
The CC operation reports data inconsistencies through an event notification. A CC cannot be user-initiated in the BIOS configuration utility, accessed using Ctrl + R. However, CC can be initiated using OpenManage Server Administrator Storage Management. For more information, see the OMSA User’s Guide on the support site.
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\