[Linux][2.0] Physical Drive Becomes Missing After Drive Group Creation on Intel P4510 or other Gen3 SSDs

Environment

• RAID Model:
  SupremeRAID SR1000 / SR1010 (and related models)

• Operating System:
  Linux (RHEL / Rocky / Alma / Ubuntu supported distributions)

• SupremeRAID Driver Version:
  Linux Driver 2.0

• SSD Model:

  • Intel P4510

  • Other PCIe Gen3 NVMe SSD
    

Issue

When creating a Drive Group using SupremeRAID Linux Driver 2.0, the Physical Drive (PD) may unexpectedly change to Missing status after creation.

This issue is commonly observed on Intel P4510 and certain PCIe Gen3 NVMe SSDs.

---

Symptoms

• Drive Group creation completed and then turn to OFFLINE

• One or more Physical Drives show Missing

• The issue occurs only on Linux Driver 2.0

• The same SSD may work normally with older driver versions

---

Root Cause

SupremeRAID Linux Driver 2.0 introduces stricter I/O queue handling requirements.

Some Gen3 NVMe SSDs (including Intel P4510) do not fully comply with the default queue configuration expected by the 2.0 driver.

As a result:

• The SSD queue configuration becomes incompatible

• The PD is marked as Missing after Drive Group creation
  

Resolution

Important Note

⚠️ The required workaround cannot be configured via SupremeRAID Manager (GUI).
You must create the Physical Drive (PD) using the CLI.

---

Step 1: Create Physical Drive (PD) via CLI with -l Parameter

When creating the Physical Drive, add the -l parameter to explicitly adjust the queue behavior for Gen3 SSDs.

Example command:

graidctl create pd /dev/nvmeX-Y -l

The -l parameter ensures the SSD queue configuration is compatible with SupremeRAID Linux Driver 2.0.

⚠️ If the -l parameter is not specified, the PD may become Missing after Drive Group creation.

---

Step 2: Verify PD Status

After creating the PD, verify that it is in a healthy state:

graidctl list pd

Confirm that:

• PD status is Online

• PD is no longer marked as Missing

---

Step 3: Continue Configuration via GUI

Once the PD is successfully created via CLI:

• You may return to SupremeRAID Manager (GUI)

• Proceed with:

  • Drive Group creation

  • Virtual Drive configuration

  • Additional management tasks

The -l parameter is only required during PD creation.

Additional Notes

• This workaround applies specifically to:

  • Linux Driver 2.0

  • Intel P4510 and certain Gen3 NVMe SSDs

• Newer Gen4 / Gen5 SSDs are typically not affected

• Related Articles

• [Linux] Controller Shows "MISSING" After License Application#

  Environment RAID Models: SupremeRAID SR-1000, SR-1010, SR-1001 Host Hardware: Any Operating System: Linux Issue On certain Linux systems, after applying the SupremeRAID license, the controller may be reported as "MISSING" in the output of graidctl or ...

• Graid Performance Benchmarking 2025 - Linux #

  Environment RAID Model: All Host Hardware: AMD/Intel Operating System: Linux Storage Performance Testing on Linux This document provides quick and straightforward instructions for performing storage performance testing using the FIO benchmarking tool ...

• Performance evaluation by using FIO benchmark tool(linux)#

  Environment RAID Model: All Host Hardware: All Operating System: Linux Issue Running performance tests can take a long time if done manually. This scripts automates this process. Resolution Download link ...

• How to Configure Proxmox with SupremeRAID RAID as a Datastore for Virtual Machines #

  Environment RAID Model: All Supreme RAID model Host Hardware: AMD/Intel Operating System: Linux Proxmox Description Virtualization has become an essential tool for modern computing, enabling multiple virtual machines (VMs) to operate on a single ...

• How to Configure QEMU with SupremeRAID RAID as a Datastore for Virtual Machines #

  Environment RAID Model: All Supreme RAID model Host Hardware: AMD/Intel Operating System: Linux RHEL QEMU Description Virtualization has become an essential tool for modern computing, enabling multiple virtual machines (VMs) to operate on a single ...