xiRAID Classic 4.1.0 Known issues

  1. Increasing the size of a RAID by replacing its disks 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 disks 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 disks.
    • Increasing the size of a RAID by adding new disks.

  2. xiRAID Classic must be installed on the latest kernel version of the system to function correctly after kernel update.

    xiRAID Classic is installed on the active kernel version of your OS and supports regular kernel updates by automatically rebuilding its kernel module. However, if your system has multiple kernel versions installed and xiRAID Classic is not installed on the latest one, it will not function correctly when switching to the latest kernel version. Make sure you are booted into the correct kernel version if you want to install xiRAID Classic on it. Otherwise, follow the steps listed in xiRAID Classic 4.1.0 Installation Guide to switch to the desired kernel version.

  3. After updating to a newer kernel, the xiRAID Classic kernel module might not update correctly without matching kernel headers.

    After updating the system to a newer kernel, the xiRAID Classic kernel module may not update correctly, which could lead to existing RAID arrays not being restored after reboot, leaving them in the 'none' state.

    To resolve this issue, install new headers and rebuild the xiRAID Classic kernel drivers using DKMS:

    1. Install the header package for your current kernel for your OS using the xiRAID Classic Installation Guide.

    2. Rebuild the xiRAID Classic kernel module with DKMS by running:
      # dkms autoinstall
    3. On success, restart the xiRAID Classic target service by running:
      # systemctl restart xiraid.target

    4. If these steps don't solve the issue, please boot your system on a previous kernel and contact support@xinnor.io.

  4. In a high-availability configuration with Pacemaker, RAID resources cannot be started in parallel.

    If you have configured multiple Pacemaker resources to manage xiRAID RAIDs in a single cluster, these RAIDs may not be available if the corresponding Pacemaker resources are started in parallel. To prevent this issue, add Pacemaker constraints to prevent these RAID resources from starting simultaneously. For on instructions on how to configure these constrains, see RAID and Cluster Resource Creation.