KB 703359 - RAID Card Detection Validation Procedure
This document outlines the standard technical steps to
validate whether a RAID controller card is installed and detected correctly in
a server system. These steps should be followed by field engineers and support
teams whenever RAID detection issues are reported.
Physical Layer Validation
- RAID card is installed in the correct PCIe slot
as per SOP.
- The RAID card is firmly seated and properly
secured.
- All SAS/SATA cables are connected correctly
between the RAID card and backplane.
- Correct cable model and routing are used as per
vendor guidelines.
- Power indicators on the RAID card (if available)
are ON.
Verification in System BIOS
Steps to confirm RAID card detection in system BIOS:
- Reboot the server.
- Press DEL or F2 to enter BIOS setup.
- Navigate to: Advanced → PCIe / PCI
Configuration.
- Verify that the RAID controller is listed as a
detected PCIe device.
- Confirm that the device name matches the
installed RAID card model.
Expected Result: The RAID controller should appear as a
detected PCIe device. If it is not listed, the card is not detected at the
hardware level and further troubleshooting is required.
RAID Controller BIOS Validation
Most RAID controllers include their own BIOS utility which
loads during system POST.
- Reboot the server and observe RAID controller
initialization messages.
- Look for prompts such as CTRL+R, CTRL+C, or
CTRL+H to enter RAID BIOS.
- Enter the RAID configuration utility.
- Verify RAID card model, firmware version, and
connected physical drives.
- Check whether logical volumes are created and
visible.
Expected Result: RAID BIOS should load successfully and
display connected disks. Failure to access this utility indicates detection or
firmware issues.
Operating System Level Validation
Windows Validation:
- Log into Windows operating system.
- Open Device Manager.
- Navigate to Storage Controllers.
- Confirm that the RAID controller is listed
without errors.
- Install and open RAID management software (e.g.,
MegaRAID Storage Manager) to verify health status.
Linux Validation:
- Run the command: lspci | grep -i raid
- Verify RAID controller appears in the output.
- Check disk visibility using: lsblk
- Use RAID utilities such as storcli or megacli to
confirm array status.
For proper documentation, the following evidence should be
included in any support ticket:
- BIOS screenshot showing RAID controller
detection.
- RAID BIOS configuration screenshot.
- Operating system device manager or command
output.
- Logs from RAID management utilities.
- Photos confirming physical installation and
cabling.
Troubleshooting if RAID Card is Not Detected
- Reseat the RAID card and verify slot placement.
- Test the card in another PCIe slot.
- Cross-test the card in a different server if
possible.
- Replace SAS/SATA cables and retest.
- Update server BIOS and RAID card firmware.
- If issue persists, initiate RMA for the RAID
controller.
Recent Articles
KB-630208 | How to use Find and Locate to search for files in Linux
Purpose To provide Linux administrators and Field Engineers with guidance on using the find and locate utilities to efficiently search for files and directories within a Linux filesystem based on criteria such as name, type, size, timestamps, ...
KB-630164 | How to use rsync to Synchronize Files
Purpose To provide a clear and practical procedure for using the rsync utility to synchronize files and directories between local systems and remote hosts, including push and pull operations, while preserving file attributes and optimizing data ...
KB-630107 | How to create a Linux swap file
Purpose To provide Field Engineers and Linux administrators with a standardized procedure for creating, configuring, and validating a Linux swap file. This procedure helps ensure sufficient virtual memory is available when physical RAM is exhausted ...
MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims
MSI All-in-One (AIO) PC – Physical Damage Policy for Warranty Claims MSI's standard warranty does not cover physical or accidental damage to an All-in-One (AIO) PC. If the damage is determined to be caused by external factors rather than a ...
KB 134833 - Troubleshooting NVSM Alert NV-CPU-XX – Unrecoverable CPU Internal Error
Purpose This document provides a general troubleshooting procedure for the NVIDIA System Management (NVSM) alert NV-CPU-XX, which indicates that a CPU has reported an internal error. The article outlines how to verify whether the alert represents an ...
Popular Articles
CP Plus Camera and NVR Configuration
NVR Configuration The CP Plus Pro Series of NVRs have been meticulously designed for providing you with upgraded performance and higher recording quality in your IP video surveillance solution. The robust processor that has been inculcated in this ...
KB 775235 - Kerberos Authentication – Overview
What is Kerberos? Kerberos is a secure authentication method used in our Active Directory (AD) environment (mbuzztech.com). It allows users to: Access multiple systems without re-entering passwords (Single Sign-On – SSO) Log in once Where We Use It ...
How to Remove and Reinstall NVIDIA Drivers on Ubuntu
This article provides step by step guide to completely remove existing NVIDIA drivers and reinstall specific version of the NVIDIA driver on the Ubuntu system Prerequisites Administrative (sudo) access to the Ubuntu system. Internet access to ...
KB 692001 - Personal Computers and Servers - Classification and Point of Contact
We can classify the computers that MBUZZ handles based on their form-factor as below: Tower Workstations, Desktops, Gaming PCs and SFF (Small form factor) PCs fall under this category. These are computers people would use on a desk and rarely move. ...
KB 298031 - M.2 SSD Tier List
The sequential read and write speeds, which are usually the most advertised number, are not a proper benchmark of real-world performance or the quality of an SSD. This article categorizes and tiers SSDs based on factors like the type of NAND flash, ...