hesela.devPatrol read
Patrol read is a controller-managed background scan of eligible physical drives for media read errors.
Eligibility may include array members and hot spares while excluding unconfigured drives. Recovery depends on the error and array configuration, and concurrent maintenance can prevent a scan. This does not promise verification of every attached device. [1]
SSD participation depends on the implementation. A management interface can accept a start request that later fails because no virtual disk exists, so request acceptance alone does not establish that scanning began. [2]
Overlapping consistency checking can interrupt patrol read; automatic restart depends on firmware. Retain completion, interruption and repair evidence, not only a schedule. Patrol read is distinct from comparing mirrored data or parity. [3] [4]
Relations
Limitations
- Media readability does not establish application-content correctness. [5]
Citations
- Dell PERC 11 User's Guide: Patrol Read, eligibility and concurrent operations
- Dell iDRAC10 1.20.xx: controller properties, patrol eligibility and job-start limitations
- Intel article 000023659: RS25/RMS25 patrol-read interruption and firmware-dependent restart
- Dell KB 000139796: PERC Check Consistency, mirror and parity correction
- Hesela: patrol read, RAID consistency and verification boundaries
Sources & caveats
- Dell PERC 11 supplies the configured-member, hot-spare and maintenance restrictions; other controllers need their own eligibility check. [1]
- Dell iDRAC10 1.20.xx lists SSDs as excluded and describes a job-start failure without a virtual disk; the SSD rule must not be generalized. [2]
- Intel article 000023659 describes firmware-dependent interruption and restart on the RS25/RMS25 families. [3]
- Documentation review, not a controller experiment, optimal-interval calculation or measured reduction in data loss.