Medium error

Lore & Background

Medium errors are most commonly detected by checking read data against a checksum, which is itself typically stored on the same device. A mismatch between data and its supposed checksum is assumed to be caused by data corruption. The locations of medium errors can be either temporary, as in bit rot where the medium is undamaged but data is lost, or permanent, as in scratching where the physical location becomes unusable. Devices can sometimes recover from medium errors by retrying or by reconciling data with the checksum. If permanent damage has occurred, the device may remap the logical address to a different, undamaged physical location. Medium errors are often associated with long latency for input/output operations due to the device retrying and attempting recovery.

Reader's Guide

Medium errors represent a fundamental distinction in storage reliability: they separate physical-layer problems from logical or protocol issues. Their significance lies in how storage systems handle them—through retries, checksum reconciliation, and address remapping—which directly affects data integrity and system performance. The long latency associated with medium errors can cascade into system-level slowdowns, making them a critical concern for storage administrators. The classification of medium errors into temporary (bit rot) and permanent (physical damage) categories guides recovery strategies: temporary errors may be resolved by rewriting data, while permanent errors require address remapping or device replacement. This error class is notable because it bridges the gap between raw physical media behavior and the logical abstraction layers that operating systems and applications rely upon. Understanding medium errors is essential for designing resilient storage systems, as they are a primary mechanism through which physical media degradation manifests in higher-level storage operations.

Did You Know?

• Locations of medium errors can be temporary (bit rot) or permanent (physical damage like scratching).
• Devices may recover from medium errors by retrying or reconciling data with the checksum.
• Medium errors are often associated with long latency due to device retrying and recovery attempts.