SupremeRAID™ Linux Driver 2.1.0 Beta Release Notes, Software, and Documentation

Beta Program Disclaimer

The features described in this release are part of the SupremeRAID™ 2.1.0 Beta Program and are provided for evaluation purposes only. Performance figures, functionality, and compatibility may change before the official release. Participants are encouraged to provide feedback to help us refine and stabilize the final version. Graid Technology Inc. makes no guarantee of production readiness for beta features at this stage.

New Features

Unified Driver Installer

Starting with version 2.1.0, SupremeRAID™ uses one driver package for all supported GPU architectures and Linux distributions. You no longer need to select a separate installer for each GPU architecture or license variant. The installer detects your GPU architecture and Linux distribution and selects the required components automatically.

Use the package in the Driver Package section for any GPU and Linux distribution listed in this release's support tables.

Drive Group Expansion

Expand an existing RAID 5 or RAID 6 drive group (DG) by adding physical drives (PDs). After expansion completes, enlarge a virtual drive (VD) to use the additional capacity.

Warning

Drive group expansion cannot be canceled after it starts.

CLI Usage

1. Check the drive group and available physical drives.

   $ sudo graidctl list dg
   $ sudo graidctl list pd
   

   The DG must be OPTIMAL. Select unconfigured PDs that meet the requirements below.

2. Add physical drives to the drive group.

   The new physical drive being added must be in the UNCONFIGURED_GOOD state.
   For example, add PDs 12 through 19 to DG 0:

   $ sudo graidctl expand dg <DG ID> <PD IDs>
   $ sudo graidctl expand dg 0 12-19
   

   Alternatively, specify PD IDs with --pd-ids. Use commas for individual IDs:

   $ sudo graidctl expand dg <DG ID> --pd-ids <PD IDs>
   $ sudo graidctl expand dg 0 --pd-ids 12,13,14,15,16,17,18,19
   

3. Monitor expansion and optionally adjust its speed.

   $ sudo graidctl edit dg <DG ID> transform_speed <low|normal|high|extreme>
   $ sudo graidctl edit dg 0 transform_speed high
   

   The DG state displays expansion progress, and added PDs are marked ONLINE (EXPAND). Available speed settings are low, normal, high, and extreme.

4. Enlarge the virtual drive size after expansion completes.

   For example, resize VD 0 in DG 0 to a total size of 1 TiB:

   $ sudo graidctl resize vd <DG ID> <VD ID> <Size>
   $ sudo graidctl resize vd 0 0 1TiB
   

   To use the maximum available size instead:

   $ sudo graidctl resize vd <DG ID> <VD ID> -max
   $ sudo graidctl resize vd 0 0 -max
   

   A VD can only grow into contiguous free space immediately following its allocation.

Requirements and Limitations

• Drive Group Expansion

  • Only DGs with the type SR support expansion.
  • Only RAID 5 and RAID 6 DGs can be expanded, with a maximum of 32 PDs per DG.
  • Expansion runs only while the DG is OPTIMAL. Expansion cannot start during copyback, and additional PDs cannot be added while expansion is in progress.
  • Only one DG expansion can run per controller/CX.
  • Expansion is not supported for SPDK DGs.
  • DGs created with driver versions earlier than 1.3.x cannot be expanded.
  • DGs containing mixed PD types, such as SATA and NVMe, cannot be expanded.
  • Rebuild journal space is required, and the rebuild journal is forced on during expansion.
  • Manual consistency checks (CC) are unavailable during expansion; scheduled consistency checks are aborted.

• Adding new PDs to an existing DG.

  • Only PDs with attributes that match the DG can be added to it.
  • New PDs must be the same type as the existing PDs in the DG. For example, SCSI PDs cannot be added to an NVMe DG, and NVMe-oF PDs cannot be added to a local NVMe DG.
  • New PDs must be UNCONFIGURED_GOOD. Assigned drives, OS drives, and hot spare PD cannot be added to an existing DG.
  • New PDs must have at least the same capacity as the existing PDs in the DG.

• Virtual Drive Resizing

  • VD resizing is not supported for SPDK DGs.
  • VDs cannot be resized during DG expansion.
  • Cached VDs and rescue VDs cannot be resized.
  • The size of VDs can only be increased and cannot be reduced.

Support for 128 Physical Drives

SupremeRAID™ now supports up to 128 physical drives system-wide, increased from 32, across up to 8 drive groups. Each DG still supports a maximum of 32 PDs. Example configurations include four DGs with 32 PDs each or eight DGs with 16 PDs each.

License Requirement

A license with 128-PD capability is required, please contact your sales representative..

CLI Usage

Existing graidctl management commands remain unchanged. Use the same commands to create and manage DGs, including PD IDs above 31.

For example, on a system with 128 eligible, unconfigured PDs numbered 0 through 127, create four RAID 6 DGs with 32 PDs each:

$ sudo graidctl create drive_group raid6 0-31
$ sudo graidctl create drive_group raid6 32-63
$ sudo graidctl create drive_group raid6 64-95
$ sudo graidctl create drive_group raid6 96-127

Verify the physical drives and drive groups:

$ sudo graidctl list pd
$ sudo graidctl list dg

RAID 0, 1, 5, 6, and 10 remain supported. Unrecoverable read error (URE) handling, rebuild, resync, and copyback behavior remain unchanged.

OS and Platform Support

Supported Operating Systems

Linux Distribution	x86_64
AlmaLinux	8.5-8.10 (Kernel 4.18), 9.0-9.8 (Kernel 5.14), 10.0-10.2 (Kernel 6.12)
Debian	12 (Kernel 6.1), 13-13.7 (Kernel 6.12)
openSUSE Leap	16 (Kernel 6.12)
Oracle Linux	8.7-8.10 (RHCK 4.18 and UEK 5.15), 9.1-9.6 (RHCK 5.14 and UEK 5.15), 9.7-9.8 (RHCK 5.14 and UEK 6.12), 10.0-10.2 (RHCK 6.12 and UEK 6.12)
RHEL	7.9 (Kernel 3.10 or 4.18), 8.10 (Kernel 4.18), 9.6-9.8 (Kernel 5.14), 10.0-10.2 (Kernel 6.12)
Proxmox VE	9.0 (Kernel 6.14), 9.1 (Kernel 6.17), 9.2-1 (Kernel 7.0)
Rocky Linux	8.5-8.10 (Kernel 4.18), 9.0-9.8 (Kernel 5.14), 10.0-10.2 (Kernel 6.12)
SLES	15 SP4-SP5 (Kernel 5.14), 15 SP6 (Kernel 6.4)
Ubuntu	20.04.0-20.04.4 (Kernel 5.4 and 5.15), 22.04.0-22.04.2 (Kernel 5.15), 22.04.3-22.04.4 (Kernel 6.2), 24.04 (Kernel 6.8 and 6.14), 24.04.4 (Kernel 7), 24.04.5 (Kernel 6.8), 26.04-26.04.1 (Kernel 7.0)

Dependencies and Utilities

Driver Package

Compatible GPU Cards

Product Segment	GPU Architecture	Card Model
SupremeRAID™ Ultra	Blackwell/Ada Lovelace	NVIDIA RTX PRO 2000, NVIDIA RTX 2000 Ada, NVIDIA RTX 2000E Ada
SupremeRAID™ Pro	Ampere	NVIDIA RTX A1000
SupremeRAID™ Core	Ampere	NVIDIA RTX A400
SR-1010	Ampere	NVIDIA RTX A2000
SR-1000	Turing	NVIDIA RTX T1000
SR-1001	Turing	NVIDIA RTX T400