|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
6.9.1 RAIDFebruary 16th, 2026 RBAC required: bear: Physical storage configuration RAID devices in BEAR are created a bare block devices with no file system until one is assigned to them. Remember, RAID provides redundancy not resiliency. Even RAID levels 1 and 10 should never be considered as a backup. They provide high availability through drive fault tolerance but if the data on the array is corrupted or the array is damaged in some way, the data is lost. Always have an offline backup for important data. This article covers the following procedures: 6.9.1.1 RAID Levels and Disk RequirementsAlthough RAID can be flexible about matching devices of different sizes and performance, this should never be done on a production system. Performance and storage capacity will be limited by the least performant device. The table below describes the minimum requirements for different RAID levels.
BEAR will not let you create an array from different disk technology types. An array must be comprised of all NVMe, SSD, or HDD. An attempt to mix types will result in an error. 6.9.1.2 Preparing for FailuresRAID levels 1 and 10 are tolerant of device failures without downtime. RAID0 has no tolerance and a failure will destroy the data requiring a new array to be built and data recovered from the last good backup (if any). When purchasing disks for use in RAID1/10, always allow for a reasonable failure rate over the expected life of the array. The table below is a rough guide to help plan the array sensibly ahead of time.
6.9.1.3 Creating a RAID Array
Only unused disks which are not part of any existing RAID array or file system will be shown.
6.9.1.4 Check a RAID ArrayIn most cases it is not required to force a manual check of the status of a RAID array. The operating system will monitor the health actively and the know status will be available in the Health tab. However, if you have reason to suspect a RAID array may not be healthy, you can force a full scan of the array as follows:
Depending on the size of the array, a scan job may take several hours or even days as the integrity of mirrored block or stripe is verified. ACHE will run a scan of a RAID1/10 array automatically each Sunday. In most cases, this is enough to maintain a healthy array or detect problems that need manual intervention. 6.9.1.5 Repairing a RAID ArrayRepairing a RAID array is an online (zero downtime) operation so that application availability is maintained. However, there may be a noticeable performance impact while the operation is ongoing. If a RAID1/10 array had a failed device, it can be replaced online (no downtime) as follows:
No failure details or selection option will appear for RAID arrays that are not in use for a file system.
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||