Release Notes

Support Added for New Versions of RHEL and Proxmox

The following Linux distributions are now supported:

RHEL, Rocky Linux, and Alma Linux versions 9.7 and 10.1
Proxmox version 9.1

Bug Fixes

Addressed a rare issue discovered during internal laboratory testing that could potentially lead to the generation of incorrect syndromes during write operations. While no instances of this issue have been reported in production environments, we are releasing a corrective patch. This update includes a mandatory resync for all RAIDs to validate data integrity. To ensure total data integrity, this update automatically triggers a mandatory resync across all RAID groups.

Known Issues

xicli raid show, xicli raid unload and xicli raid destroy behavior after destroying or unloading a RAID
When the commands xicli raid show, xicli raid unload, or xicli raid destroy are issued shortly after a xicli raid destroy or xicli raid unload command, they may fail because the initial destroy/unload process is still completing. This does not lead to data corruption or any other issues. Simply repeating the commands will ensure they are successful.
Disabling CPU Cores
Do not disable CPU cores on a system with xiRAID Classic as this not supported.
GPG errors after running apt update
On Ubuntu and Proxmox, you may encounter errors related to the expiry of the pkg.xinnor.io GPG keys (the next expiry is on November 26, 2029) when running apt update or updating from xiRAID Classic 4.3.0. For instructions on how to resolve these errors, refer to Updating GPG Keys.
Information about device wear cannot be displayed for SATA and SAS drives

The wear value in the output of the xicli raid show -e command will likely show N/A for SATA and SAS devices. At the moment, information about device wear is available only for NVMe drives.
Unavailable drives in spare pools
If xiRAID Classic attempts to use a drive from a spare pool and the drive is unavailable, it will be permanently removed from the spare pool. The drive will not be automatically added back when it becomes available again. To use the drive in the spare pool again, you must manually add it back.
Issues with kernel updates on Proxmox
A bug in DKMS versions 3.0.9 and 3.0.10 prevents the proper installation of new kernel packages on Proxmox systems with xiRAID Classic. This issue occurs if your system has DKMS modules that use the BUILD_EXCLUSIVE_KERNEL parameter.
To work around this issue, users should disable DKMS autoinstall globally on their system by creating a special marker file:
```
touch /etc/dkms/no-autoinstall
```
This will cause future kernel package installations to skip the process of building DKMS modules, including the xiRAID Classic kernel module. As a result, to keep xiRAID Classic operational on new kernels, the DKMS autoinstall procedure must be run manually each time a new kernel is installed. For example:
```
dkms autoinstall --kernelver 6.8.12-7-pve
```
In the example above, 6.8.12-7 is the version of the recently installed kernel update.
Increasing the size of a RAID by replacing its drives with larger ones can introduce defects that may affect the system's functionality
A critical defect has been discovered in all xiRAID Classic 4.0.x versions related to the feature of increasing the size of a RAID by replacing its drives with larger ones (vertical scaling RAID operation). It is strongly advised not to use this feature. This bug will be addressed and fixed in the upcoming release.
This defect does not affect the following possibilities:
- Changing the RAID level with the addition of new drives.
- Increasing the size of a RAID by adding new drives.