Virtual Disk considerations for software RAID controllers
The following considerations apply when creating virtual disks:
- Space allocation — When you create a new virtual disk, the software RAID controllers allocate the largest area of free space on the physical disks to the new virtual disk.
- Rebuilding data—If a failed physical disk is used by both redundant and non-redundant virtual disks, only the redundant virtual disks are rebuilt.
For information about controller limitations, see Number of Physical Disks per Virtual Disk.
NOTE: When creating virtual disks using software RAID controllers, the information related to the physical disks linked to the virtual disk is enumerated or displayed on Storage Management after a short delay. This delay in displaying the information does not cause any functional limitation. If you are creating partial virtual disks, it is recommended that you provide Storage Management adequate time between each partial virtual disk creation process.
|
NOTE: On software RAID controllers, if a physical disk (SATA SSD or HDD) is removed from a virtual disk and the same physical disk is reinserted (hot plug) into the virtual disk instantly, within a fraction of a second, then the virtual disk state is displayed as
Ready and the physical disk state is displayed as
Online. However, if the same physical disk is reinserted after a short delay, then the virtual disk state is displayed as
Degraded and the physical disk state is displayed as
Ready.
|
NOTE: On software RAID controllers, Virtual Disks can be created using SATA, NVMe drives, and NVMe HHHL cards. However, mixing of SATA and NVMe drives in a single Virtual Disk is not supported.
|
NOTE: Blinking and unblinking a virtual disk in software RAID is blocked, if any of the participating physical disk is HHHL add- in card. Blink and unblink operation is also blocked for non-RAID HHHL add-in card virtual disk.
|