We have identified that when a disk is deleted from the top of the list (e.g., PHYSICALDRIVE0, PHYSICALDRIVE1), the serial number and name of the deleted disk get reassigned or swapped with the disk immediately below it. This results in incorrect tracking of disk identities across monitoring cycles.
However, this issue does not occur when a disk is deleted from the bottom of the list — in such cases, disk mappings remain consistent and accurate.
However, this issue does not occur when a disk is deleted from the bottom of the list — in such cases, disk mappings remain consistent and accurate.