SupremeRAID™ SE Linux User Guide 2.0.0

Jul. 31, 2026

Version:2.0.0 Rev. 001Date:7/31/26

Info

Copyright © 2021–2026 Graid Technology Inc. All Rights Reserved.
SupremeRAID™ is a registered trademark of Graid Technology Inc. All other trademarks and registered trademarks are the property of their respective owners.
Graid Technology reserves the right to make changes without further notice to any products or content herein to improve reliability, function, or design. Graid Technology makes no warranty as to the accuracy or completeness of the content or information provided herein, which are provided on an “as is” basis.
No license to Graid Technology’s or any third party’s intellectual property rights are conveyed hereunder.

Introduction

SupremeRAID™ SE is the most powerful, high-speed data protection solution specially designed for NVMe SSDs. SupremeRAID™ SE installs a virtual NVMe controller onto the operating system and integrates a high-performance, AI processor-equipped PCIe RAID card into the system to manage the RAID operations of the virtual NVMe controller.

This document explains how to install the SupremeRAID™ SE software package for Linux and how to manage the RAID components using the Graphical Management Console.

SupremeRAID™ SE Linux Specification

Supported models: SR-SE-TU, SR-SE-AM, SR-SE-AD, SR-SE-BW
Supported RAID levels: RAID 0, 1, 5, 10
Recommended minimum drive number for each RAID level:
- RAID 0: at least one drive
- RAID 1: at least two drives
- RAID 5: at least three drives
- RAID 10: at least two drives
Maximum number of physical drives: 8
Maximum number of drive groups: 8
Maximum number of virtual drives per drive group: 1,023
Maximum size of the drive group: Defined by the physical drive sizes
Configurable strip size (RAID 0, RAID 10): 4k, 8k, 16k, 32k, 64k, 128k
Supported modes: Perpetual and Subscription
- Perpetual: For licensing inquiries, please contact our Sales Department.
- Subscription: Please refer to the Activate Subscription section to register and start your subscription with recurring monthly payments.

RAID Components

SupremeRAID™ has four major RAID logical components:

Physical Drive (PD)
Drive Group (DG)
Virtual Drive (VD)
Controller (CX)

Physical Drive (PD)

Since NVMe drives are not directly attached to the SupremeRAID™ SE controller, you must tell the controller which SSDs can be managed. After an SSD is created as a physical drive, the SupremeRAID™ SE driver unbinds the SSD from the operating system, meaning the device node (/dev/nvmeX) disappears and is no longer accessible. At the same time, the SupremeRAID™ SE driver creates a corresponding device node (/dev/gpdX). You can check the SSD information, such as SSD model or SMART logs, using this device node. To control and access the SSD using /dev/nvmeXn1, you must first delete the corresponding physical drive.
SupremeRAID™ SE supports a maximum 8 physical drives in one Drive Group.

Drive Group (DG)

The main component of RAID logic is a RAID group. When the drive group is created, the SupremeRAID™ SE driver initializes the physical drives with the corresponding RAID mode to ensure that the data and parity are synchronized.

There are two types of initialization processes.
- Fast Initialization: When all the physical drives in the drive group (DG) support the de-allocate dataset management command, the SupremeRAID™ SE driver performs fast initialization by default, which optimizes the drive group state immediately.
- Background Initialization: Performance is slightly affected by the initialization traffic, but you can still create the virtual drive and access the virtual drive during a background initialization. SupremeRAID™ supports eight drive groups, with a maximum of 32 physical drives in one drive group.
SupremeRAID™ SE supports a maximum of 8 Drive Groups.

Virtual Drive (VD)

The virtual drive is equivalent to the RAID volume. You can create multiple virtual drives in the same drive group for multiple applications. The corresponding device node (/dev/gdgXnY) appears on the operating system when you create a virtual drive, and you can make the file system or running application directly on this device node.
SupremeRAID™ SE supports a maximum of 1023 Virtual Drives in each Drive Group.

Controller (CX)

The controller is the core component of the RAID system. It provides detailed hardware information such as GPU serial number, temperature, and fan speed. RAID management relies on the controller, so the controller's state directly affects the underlying drive group operations.

Precautions

System suspension and hibernation are currently unsupported due to a limitation in the NVIDIA driver.
If other SupremeRAID™ products have been installed previously, running the SupremeRAID™ SE installer may prevent the previous product settings from being restored.
For subscription mode, please note that one email account is restricted to a single subscription and GPU. After your subscription expires, you will still be able to access and read your data, but the data cannot be written to the drive.
Only perpetual mode supports NVMe-oF remote target functionality.

Activate Subscription

SupremeRAID™ SE offers subscription-based services, allowing users to select a plan based on their requirements. Subscription payments are made by credit card and billed monthly.

Please go to the SupremeRAID™ SE product page and select Subscription Plan 90-Day Free Trial. Then sign up to create a new account on the SupremeRAID™ SE Portal.
SupremeRAID™ Portal
Choose your preferred subscription plan. You can start using the service after linking your credit card.
Subscription plan
Upon successful subscription, please follow the steps in the next section to proceed with the installation.

Installation

This section describes how to install the SupremeRAID™ SE software package for Linux operating systems.

Prerequisites

Before installing the software package, ensure that the system meets the following requirements:

Minimum system requirements:
- CPU: 2 GHz or faster with at least 8 cores
- RAM: 16 GB
- Supported operating system: See the Supported Operating Systems section on release notes.
- An available PCIe Gen3 or Gen4 x16 slot
The GPU card must be installed into a PCIe x16 slot.
The SupremeRAID™ SE software package, which includes the Pre-Installer and Installer, can be downloaded directly from the Graid Technology website. The Pre-Installer configures all necessary dependencies and environment settings automatically prior to installing the SupremeRAID™ SE driver. The Installer contains the SupremeRAID™ SE driver package and will automatically detect your Linux distributions and install the appropriate files.
Make sure a SupremeRAID™ SE compatible SSD drive is being used. SupremeRAID™ SE supports all form factors of NVMe drives, including M.2, U.2, U.3, EDSFF, and AIC.

BIOS Setting

[OPTIONAL] The IOMMU function (AMD) or VT-d function (Intel) is recommended to be disabled in the system BIOS, typically found on the BIOS Advanced page.
[OPTIONAL] It is highly recommended to disable the UEFI Secure Boot function on the BIOS security page. If UEFI Secure Boot is not applicable in your system, you will need to sign the NVIDIA Kernel Module. For further information and troubleshooting, please refer to the NVIDIA website.

Installing the Driver

The recommended and quickest way to install the SupremeRAID™ SE is by using the pre-installer scripts and installer (described below).

Pre-installer

The SupremeRAID™ SE pre-installer is an executable file that contains the required dependencies and a setup script that installs the NVIDIA driver. The script makes it easy to prepare the environment and install the SupremeRAID™ SE driver on every supported Linux distribution. Use the following steps to prepare the environment and install the SupremeRAID™ SE driver using the pre-installer in supported Linux distributions.

Note

To run the pre-installer, the system must have internet access to download the required dependencies from the official mirror.

Please refer to the Linux release notes to download the latest version of the pre-installer and grant it executable permissions.
Pre-installer
You may also use the following command to perform the installation.
```
sudo wget [filelink]
sudo chmod +x [Filename]
sudo ./[filename]
```

Driver

Download the latest driver version from the Driver Package section and grant it executable permissions.
Note
Please select the appropriate driver based on your GPU architecture.
Driver Package
You may also use the following command to perform the installation.
```
sudo wget [filelink]
sudo chmod +x [Filename]
sudo ./[filename]
```
At the Welcome page, select Next and press Enter to view the end-user license agreement.
Driver welcome page
In the end-user license agreement page, you can scroll down to read the license content. After reviewing the license, accept the agreement, and click Next to proceed.
Driver EULA page
Complete the installation. You can access the SupremeRAID™ SE Management Console by clicking the link. The SupremeRAID™ SE Management Console requires port 50060 to be open for proper functionality. If this port is not enabled, the web interface may not work correctly.
Driver installation successful page
If port 50060 is occupied by another application, you can set up your own port and IP. Please edit the configuration file /etc/graidmgr/service.conf.
For example, if you want to set the port and IP to 8888 and 172.16.12.34 respectively, it would look as follows:
```
[common]
web_port=8888
web_addr="172.16.12.34"
```
Enter the host token into the SupremeRAID™ SE Management Console.
Management Console Host Token
If you have lost the host token, please use the following command to retrieve the host token.
```
sudo graid-mgr host_token gen
```
Select your preferred mode. SupremeRAID™ SE offers two different modes: Perpetual and Subscription.
- Perpetual: License key is required to activate the perpetual service. Please note that if you are installing the 2.0 driver package, you will need a V2 license key to activate the service. For licensing inquiries, please contact our Sales Department.
- Subscription: Start your subscription with recurring monthly payments.
Select SupremeRAID™ SE Mode
If you choose Subscription mode, please log in to the SupremeRAID™ SE Management Console using the email address and password you used to sign up for the SupremeRAID™ SE Portal.
Subscription Mode
If you choose Perpetual mode, please set up a password. Please note that Perpetual mode requires the purchase of a license. Please contact our Sales team for assistance.
Perpetual Mode
Bind your GPU and start the RAID setup.
GPU binding

Uninstalling the Driver

Open the Linux terminal.

Issue the command for your distribution:

Ubuntu & Debian

sudo systemctl stop graid graid-mgr
sudo dpkg -r graid-sr graid-mgr
sudo reboot

# or

sudo systemctl stop graid graid-mgr
sudo apt remove graid-sr -y
sudo reboot

RHEL & SUSE

sudo systemctl stop graid graid-mgr
sudo rpm -e graid-sr graid-mgr
sudo reboot

# or

sudo systemctl stop graid graid-mgr
sudo dnf remove -y graid-sr
sudo reboot

Upgrading the Driver

Upgrading to Driver 2.0

Subscription Mode

If your current driver version is earlier than 1.7.2 Update 67 (for example, 1.7.2 Update 61), you must install the 1.7.2 Update 67 driver before upgrading to Driver 2.0. Please follow the steps below:
1. Install the 1.7.2-67 driver package.
2. At this stage, the virtual drives and drive groups may temporarily enter a TRANSFORMING state. Please make sure both the VDs and DGs return to an OPTIMAL state before proceeding.
3. Uninstall the 1.7.2-67 driver package. Please refer to the Uninstalling the Driver section.
4. Run the 2.0.x SupremeRAID™ SE Pre-installer.
5. Install the 2.0.x SupremeRAID™ SE driver package.
If your current driver version is 1.7.2 Update 67 or later (for example, 1.7.2 Update 70 in the future), please follow the steps below:
1. Confirm that the virtual drives and drive groups are in an OPTIMAL state.
2. Uninstall the existing 1.7.2-67 or later driver package. Please refer to the Uninstalling the Driver section.
3. Run the 2.0.x SupremeRAID™ SE Pre-installer.
4. Install the 2.0.x SupremeRAID™ SE driver package.

Perpetual Mode

Note

Please note that if you are installing the 2.0 driver package, you will need a V2 license key to activate the service. For licensing inquiries, please contact our Sales Department.

If your current driver version is earlier than 1.7.2 Update 67 (for example, 1.7.2 Update 61), you must install the 1.7.2 Update 67 driver before upgrading to Driver 2.0. Please follow the steps below.
1. Install the 1.7.2-67 driver package.
2. At this stage, the virtual drives and drive groups may temporarily enter a TRANSFORMING state. Please make sure both the VDs and DGs return to an OPTIMAL state before proceeding.
3. Apply V2 license key. Please open the Linux Terminal, then enter the following command:
```
sudo graidctl apply license [LICENSE_KEY]
```
4. Uninstall the 1.7.2-67 driver package. Please refer to the Uninstalling the Driver section.
5. Run the 2.0.x SupremeRAID™ SE Pre-installer.
6. Install the 2.0.x SupremeRAID™ SE driver package.
If your current driver version is 1.7.2 Update 67 or later (for example, 1.7.2 Update 70 in the future), please follow the steps below:
1. Confirm that the virtual drives and drive groups are in an OPTIMAL state.
2. Apply V2 license key. Please open the Linux Terminal, then enter the following command:
```
sudo graidctl apply license [LICENSE_KEY]
```
3. Uninstall the 1.7.2-67 driver package. Please refer to the Uninstalling the Driver section.
4. Run the 2.0.x SupremeRAID™ SE Pre-installer.
5. Install the 2.0.x SupremeRAID™ SE driver package.

RAID Management

Managing Physical Drives

Creating a Physical Drive

To create physical drives, please log in to the SupremeRAID™ SE Management Console, then navigate to the RAID management / Physical Drives section on the sidebar menu and click the “Create” button.

Physical Drive State:

State	Description
ONLINE	Physical drive was added to a drive group and is ready to work.
HOTSPARE	Physical drive is configured as a hot spare drive.
FAILED	Physical drive is detected, but it is not operating normally.
OFFLINE	Physical drive is marked as offline.
REBUILD	Physical drive is being rebuilt.
MISSING	Physical drive cannot be detected.
UNCONFIGURED_GOOD	Physical drive did not join a drive group.
UNCONFIGURED_BAD	Physical drive did not join a drive group and is not operating normally.
COPYBACK	Physical Drive is performing copyback.

Deleting a Physical Drive

To delete physical drives, please select the physical drives you want to delete and click the “Delete” button.

Info

You cannot delete a physical drive which is used by drive group.

Making a Physical Drive Online/Offline/Good/Bad

To mark a physical drive as Online/Offline/Good/Bad, please select the physical drives you want to change and click the “Marker” button.

Assigning a Hot Spare Drive

To assign a physical drive as a hot spare, please select the physical drives you want to assign and click the “Hot spare” button.

Managing Drive Groups

Creating a Drive Group

To create a drive group, please log in to the SupremeRAID™ SE Management Console, then navigate to the RAID management / Drive Group section on the sidebar menu and click the “Create” button.

Drive Group State:

State	Description
OFFLINE	Drive group is not working properly. This condition usually occurs when the number of damaged physical drives exceeds the limit.
OPTIMAL	Drive group is in optimal state.
OPTIMAL (!)	Drive group is in optimal state but found inconsistency data.
OPTIMAL (cc)	Drive group is in optimal state and the consistency check task is ongoing.
OPTIMAL (cp)	Drive group is performing copyback.
OPTIMAL (cc!)	Drive group is in optimal state and the consistency check task is ongoing but found inconsistent data.
DEGRADED	Drive group is available and ready for use, but the number of missing or failed physical drives has reached the limit.
PARTIALLY_DEGRADED	Drive group is available and ready for use, but some physical drives are missing or failed.
RECOVERY	Drive group is recovering.
FAILED	Drive group is not working normally.
INIT	Drive group is initializing.
RESYNC	Drive group is resynchronizing and remains available and ready for use. This condition usually occurs when the system encounters an abnormal crash. Do not replace the physical drive in this state until the resynchronization process completes.
RESCUE	Drive group is in rescue mode and can only be read.

Deleting a Drive Group

To delete a drive group, please log in to the SupremeRAID™ SE Management Console, then navigate to the RAID management / Drive Group section on the sidebar menu. Please select the drive group you want to delete and click the “Delete” button.

Info

You cannot delete a drive group that contains a virtual drive.

Degradation and Recovery

If multiple drive groups require simultaneous recovery, the drive groups recover individually. If multiple physical drives in the same drive group require rebuilding, the physical drives are rebuilt simultaneously.

Rescue Mode

If a damaged drive group is initialized or a recovering drive group encounters an abnormal system crash, the data integrity of the drive group is affected. In this event, the drive group is forced offline to prevent data from being written to the drive group. To read the data from the drive group, force the drive group to go online using Rescue mode.

Info

A drive group in Rescue mode is read-only. Rescue mode cannot be disabled.

Managing Virtual Drives

Creating a Virtual Drive

To create virtual drives, please log in to the SupremeRAID™ SE Management Console, then navigate to the RAID management / Virtual Drives section on the sidebar menu. Click the “Create” button to select the drive group you want to use for the virtual drives.

Virtual Drive State:

State	Description
OFFLINE	Drive group is not working normally. This condition is usually caused when the number of damaged physical drives exceeds the limit.
OPTIMAL	Drive group is in the optimal state.
PARTIALLY_DEGRADED	Drive group is available and ready for use, but some physical drives are missing or failed.
RECOVERY	Drive group is recovering.
FAILED	Drive group is not working normally.
INIT	Drive group is initializing.
RESYNC	Drive group is resynchronizing and remains available and ready for use. This condition usually occurs when the system encounters an abnormal crash. Do not replace the physical drive in this state until the resynchronization process completes.
RESCUE	Drive group is in rescue mode and can only be read.

Stripe-cache state:

State	Description
OFFLINE	Stripe cache drive group is OFFLINE.
CLEAN	Stripe cache write-back has finished.
PURGE	Stripe cache is writing data into the virtual drive.
ACTIVE	Stripe cache is in optimal state.

Deleting a Virtual Drive

To delete a virtual drive, please log in to the SupremeRAID™ SE Management Console, then navigate to the RAID management / Virtual Drives section on the sidebar menu. Please select the virtual drive you want to delete and click the “Delete” button.

Feature Overview

Consistency Checks

The consistency check operation verifies that the data is correct in Drive Groups that use RAID levels 1, 5, and 10. In a system with parity, for example, checking consistency calculates the data on one drive and compares the results to the contents of the parity drive.

To start the consistency check, please log in to the SupremeRAID™ SE Management Console, then navigate to the RAID management/Drive Group section on the sidebar menu. Select the drive group you want to perform the Consistency Check on and click the “Consistency Check” button.

Info

You cannot perform a consistency check on RAID 0 because it does not provide data redundancy. Additionally, a consistency check can only run when the DG is in OPTIMAL or PARTIALLY_DEGRADED state.

Drive Copyback

The Drive Copyback feature allows users to manually initiate data migration from one drive to another without affecting the overall Drive Group state. This operation is user-controlled and can be performed for various reasons, such as replacing an aging drive, preparing for hardware upgrades, or managing storage configurations.

To start the Copyback, please log in to the SupremeRAID™ SE Management Console, then navigate to the RAID management / Drive Group section on the sidebar menu. Select the drive group you want to perform the Copyback on and click the Physical Drives tab. Choose the physical drive first and click the “Actions” button to conduct Copyback.

Double Failure Protection with Distributed Journaling

SupremeRAID™ SE incorporates a distributed journaling mechanism specifically designed to safeguard data during abnormal shutdowns in double-failure scenarios. This system ensures data integrity by logging data in a dedicated journaling space before writing it to the storage area. Any incomplete I/O operations are replayed upon service restart to maintain data consistency.

This journaling feature is automatically enabled in degraded mode to uphold data integrity. Additionally, users still have the flexibility to bypass journaling space reservation when creating a drive group.

Info

Only RAID5 can enable the journal function. If the user bypasses the creation of the journal space, it cannot be recreated.

Dataset Management (DSM) Deallocate

The SupremeRAID™ SE driver introduces support for the NVMe DSM deallocate (trim) command on virtual drives, improving the efficiency of unused storage space management on NVMe SSDs. This feature allows filesystems or applications to issue deallocate commands on virtual drives, which are then translated by the driver and sent directly to the SSDs. By enabling the drives to manage deallocated blocks internally, this reduces write amplification, optimizes storage efficiency, and enhances overall performance.

When a discard command is issued to a virtual drive, it triggers a corresponding deallocate command to the underlying NVMe SSDs. The system supports a minimum discard range of 4KB, aligned with the logical block addressing (LBA) size, and can handle a maximum deallocate range of approximately 400 GiB per command. For larger discard operations, and the filesystem and block layer handle the process seamlessly.

This feature is automatically enabled on NVMe SSDs that support the deallocate command and guarantee that deallocated blocks return zeros. For SSDs without this guarantee, the system defaults to a "write zeros" command to ensure data consistency. This flexible approach ensures broad compatibility across different SSDs while optimizing their individual capabilities.

To ensure the filesystem can take advantage of this capability and issue discard commands when files are deleted, it must be mounted with the discard option.

Attachments

Events

Category	Severity	Description
Physical Drive	Warning	Physical Drive <PD_ID> state has transitioned from <STATE_OLD> to unconfigured bad.
Physical Drive	Critical	Physical Drive <PD_ID> state has transitioned from <OLD_STATE> to failed.
Physical Drive	Warning	Physical Drive <PD_ID> state has transitioned from <OLD_STATE> to offline.
Physical Drive	Critical	Physical Drive <PD_ID> state has transitioned from <OLD_STATE> to missing.
Physical Drive	Info	Physical Drive <PD_ID> state has transitioned from <OLD_STATE> to online.
Physical Drive	Info	Physical Drive <PD_ID> state has transitioned from <OLD_STATE> to rebuild.
Physical Drive	Info	Physical Drive <PD_ID> state has transitioned from <OLD_STATE> to unconfigured good.
Physical Drive	Info	Physical Drive <PD_ID> has been successfully created.
Physical Drive	Info	Physical Drive <PD_ID> has been deleted.
Physical Drive	Info	Physical Drive <PD_ID> has been hot-plugged.
Physical Drive	Warning	Physical Drive <PD_ID> has been hot-removed.
Physical Drive	Warning	The temperature of Physical Drive <PD_ID> is currently <CURRENT_TEMP> degrees, which exceeds the Warning threshold of <THRESHOLD_TEMP> degrees. Critical Warning error code: ERROR_CODE.
Physical Drive	Critical	The temperature of Physical Drive <PD_ID> is currently <CURRENT_TEMP> degrees, which exceeds the Critical threshold of <THRESHOLD_TEMP> degrees. Critical Warning error code: ERROR_CODE.
Physical Drive	Critical	The available spare capacity <AVAIL_SPARE> of Physical Drive <PD_ID> has fallen below the threshold <SPARE_THRESHOLD>. Critical Warning error code: <ERROR_CODE>.
Physical Drive	Critical	The NVM subsystem reliability of Physical Drive <PD_ID> has been degraded due to significant media related errors or any internal error that degrades NVM subsystem reliability. Critical Warning error code: <ERROR_CODE>.
Physical Drive	Critical	All of the media of Physical Drive <PD_ID> has been placed in read only mode. Critical Warning error code: <ERROR_CODE>.
Physical Drive	Critical	The volatile memory backup device of Physical Drive <PD_ID> has failed. Critical Warning error code: <ERROR_CODE>.
Physical Drive	Critical	The Persistent Memory Region of Physical Drive <PD_ID> has become read-only or unreliable. Critical Warning error code: <ERROR_CODE>.
Physical Drive	Warning	Physical Drive <PD_ID> is currently experiencing a wearout level of WEAROUT, surpassing the Warning threshold of <THRESHOLD_WEAROUT>.
Physical Drive	Critical	Physical Drive <PD_ID> is currently experiencing a wearout level of WEAROUT, surpassing the Critical threshold of <THRESHOLD_WEAROUT>.

Category	Severity	Description
Drive Group	Fatal	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to failed.
Drive Group	Critical	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to offline.
Drive Group	Critical	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to degraded.
Drive Group	Warning	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to rescue.
Drive Group	Warning	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to partially degraded.
Drive Group	Info	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to optimal.
Drive Group	Info	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to recovery.
Drive Group	Info	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to init.
Drive Group	Info	Drive Group <DG_ID> state has transitioned from <OLD_STATE> to resync.
Drive Group	Info	Drive Group <DG_ID> has been successfully created.
Drive Group	Info	Drive Group <DG_ID> has been deleted.
Drive Group	Info	Consistency Check for Drive Group <DG_ID> has been manually aborted.
Drive Group	Info	Consistency Check for Drive Group <DG_ID> has been aborted due to the deletion of the Drive Group.
Drive Group	Info	Consistency Check for Drive Group <DG_ID> was aborted due to the Drive Group migrating from Controller <CX_OLD> to <CX_NEW>.
Drive Group	Info	Consistency Check for Drive Group <DG_ID> has been aborted due to the Drive Group's state transitioning to <DG_STATE>.
Drive Group	Info	Manual Consistency Check for Drive Group <DG_ID> has been completed.
Drive Group	Info	Scheduled Consistency Check for Drive Group <DG_ID> has completed.
Drive Group	Info	Manual Consistency Check for Drive Group <DG_ID> has started.
Drive Group	Info	Scheduled Consistency Check for Drive Group <DG_ID> has started.
Drive Group	Info	Inconsistency in Drive Group <DG_ID> has been fixed at: Drive Group block range: <DG_INTERS>.
Drive Group	Critical	Inconsistency detected in Drive Group <DG_ID> at: Drive Group block range: <DG_INTERS>.
Drive Group	Critical	Consistency Check for Drive Group <DG_ID> has been aborted due to the 'stop_on_error' policy.
Drive Group	Critical	Consistency Check for Drive Group <DG_ID> has been aborted due to numerous inconsistencies found and fixed.
Drive Group	Info	Journal Replay for Drive Group <DG_ID> has started.
Drive Group	Info	Journal Replay for Drive Group <DG_ID> has been completed. Entry replayed <REPLAYNR>.
Drive Group	Critical	Journal Replay for Drive Group <DG_ID> has been waiting Physical Drive <PD_ID> to be active.
Drive Group	Critical	Journal Replay for Drive Group <DG_ID> has been aborted due to inconsistency detected on journal.

Category	Severity	Description
Virtual Drive	Info	Inconsistency for Virtual Drive <VD_ID> within Drive Group <DG_ID> has been fixed at: Virtual Drive block range: <VD_OFFSETS>.
Virtual Drive	Critical	Inconsistency found in Virtual Drive VD_ID of Drive Group <DG_ID> at: Virtual Drive block range: <VD_OFFSETS>.
Virtual Drive	Info	Virtual Drive VD_ID for Drive Group <DG_ID> has been created successfully.
Virtual Drive	Info	Virtual Drive VD_ID for Drive Group <DG_ID> has been deleted.
Virtual Drive	Info	Stripe cache for Virtual Drive <VD_ID> on Drive Group <DG_ID> has been deleted.
Virtual Drive	Info	Stripe cache for Virtual Drive <VD_ID> on Drive Group <DG_ID> has been created successfully.

Category	Severity	Description
Controller	Warning	The temperature of Controller <CX_ID> is currently <CURRENT_TEMP> degrees, which exceeds the GPU threshold of <THRESHOLD_TEMP> degrees.
Controller	Warning	The temperature of Controller <CX_ID> is currently <CURRENT_TEMP> degrees, which exceeds the GPU memory threshold of <THRESHOLD_TEMP> degrees.
Controller	Warning	The temperature of Controller <CX_ID> is currently <CURRENT_TEMP> degrees, it will cause controller slowdown.
Controller	Critical	The temperature of Controller <CX_ID> is currently <CURRENT_TEMP> degrees, it will cause controller shutdown.

FAQ

Product & Service

Question	Answer
What should I do if I want to switch to another SupremeRAID™ product after using the SupremeRAID™ SE	Currently, SupremeRAID™ SE only supports data migration to SupremeRAID™ SR. You must first cancel the SE subscription in the user portal and purchase an SR license before installing and using SupremeRAID™ SR. Please note that once SupremeRAID™ SR is installed, you will not be able to revert to the previous SupremeRAID™ SE configuration. If you have previously installed other SupremeRAID™ products, executing the SupremeRAID™ SE installation will prevent the restoration of previous product settings.
Is there a performance difference between Quadro/RTX and GTX series cards	Performance Advantage: Quadro/RTX cards support larger BAR1 memory, enabling direct communication between the GPU and NVMe drives. This significantly benefits performance, especially in Linux environments.
Does the SupremeRAID™ SE driver support system suspension or hibernation	System suspension and hibernation are currently unsupported. Please ensure that the machine does not enter suspension or hibernation mode.
What language versions does SupremeRAID™ SE offer	Currently, only the English version is available.
Does SupremeRAID™ SE support SAS/SATA drives	SAS and SATA drives are not supported by the Windows driver.
Does SupremeRAID™ SE support Remote Target for NVMe-oF	Only SupremeRAID™ SE Perpetual Mode supports Remote Target for NVMe-oF in Linux environments.
If my GPU fails during the subscription period and needs to be replaced, what is the proper procedure	Please contact us.

Supported OS & Devices

Question	Answer
What kind of GPU does SupremeRAID™ SE support	NVIDIA GPUs. Please refer to the Release Notes to view the complete list of supported GPUs.
What form factor of NVMe drives can I use with SupremeRAID™ SE	SupremeRAID™ SE supports all form factors of NVMe drives, including M.2, U.2, U.3, EDSFF, and AIC.
What kind of Operating Systems does SupremeRAID™ SE support	SupremeRAID™ SE supports both Windows and Linux. Please refer to the Release Notes and select the software version to view the complete list of supported Operating Systems.
Does SupremeRAID™ SE support cross-device usage	Cross-device usage is supported when using the same user account and the same GPU.

Subscription Plans

Question	Answer
How to subscribe SupremeRAID™ SE	1. Prepare Hardware: Ensure you have a compatible GPU card and NVMe SSDs. Please refer to the Release Notes and select the software version to view the complete list of supported devices. 2. Sign up for a trial by creating an account with your email in the User Portal. Please note that one user account is restricted to a single subscription, machine, and GPU. Cross-device usage is not supported. 3. Installation: Follow the instructions in the User Guide to install SupremeRAID™ SE.
What subscription plans are currently available for SupremeRAID™ SE	There are currently two subscription plans available for SupremeRAID™ SE: the Standard Plan and the Premium Plan. The primary difference between the two lies in the number of supported NVMe SSDs. The Standard Plan supports up to four NVMe SSDs, while the Premium Plan supports up to eight.
Can I upgrade my subscription plan from Standard to Premium	The upgrade feature is not yet available, but it will be gradually rolled out in the future. If you wish to upgrade your plan to support more physical drives, please contact us.
How to cancel my subscription	You may cancel your subscription at any time by logging into the User Portal.
What will happen to my data once the subscription is canceled	After canceling your subscription, the system will stop charging you on the next billing date. Your data will not be lost. Instead, it will be placed in read-only mode. You will still be able to access and read the data within the folder; however, you will no longer be able to write or add new data to the folder.

Billing & Payments

Question	Answer
What payment methods are available for subscribing to SupremeRAID™ SE	Currently, we only accept credit card payments.
What is the billing cycle	SupremeRAID™ SE is based on a monthly billing cycle.
When is the billing date	You will be automatically charged once a month. For example, if your first payment is on July 5, the renewal charge will be processed automatically on August 5 (depending on the time difference, there may be a difference of one day earlier or later), unless you cancel your subscription plan prior to that date.
Are there any processing fees associated with credit card payments	You may be charged a Cross-Border Fee (CBF). This fee is charged by the credit card issuing organizations (such as Visa or Mastercard). It may apply when the cardholder makes a purchase with an overseas merchant, regardless of whether the transaction currency is the local currency or the cardholder’s home currency.
Where can I view my billing records	You can log in to the User Portal to view the billing amount and billing history.
How can I update my payment information	You can log in to the User Portal to update your credit card information.
Why did my payment fail	Please ensure that the credit card information you provide are correct and that there is sufficient credit available.
What happens after a payment failure	After a payment failure, we will attempt to charge your card again after one day. If the payment still cannot be processed successfully, we will automatically cancel your subscription. You can reactivate your subscription at any time using a valid credit card.

Account Management

Question	Answer
How can I update my account information	You can log in to the User Portal to update your account information.
Can a single user account subscribe to more than one SupremeRAID™ SE plan	Currently, each user account is limited to a single subscription plan.
Can the same account be logged in on different machines	Cross-device usage is supported when using the same user account and the same GPU. Each user account is limited to one subscription and one GPU.