Surveillance Drive Firmware Internals: AllFrame, Workload Rate Limit, and SMR Translator Mechanics
Most WD Purple troubleshooting writeups online repeat the same marketing summary: 24/7 duty, AllFrame, TLER, 180 TB/year. None of those phrases describe what the firmware actually does to the drive when an NVR runs into a fault. This section bridges marketing terminology to firmware reality. It also corrects a misconception that has spread through legacy donor-matching forums: the "AC-family" designation sometimes attached to surveillance drives refers to 1990s Western Digital Caviar IDE models such as the AC-2420, not modern surveillance hardware. Modern WD Purple drives run on Marvell V2 SoCs for standard CMR models on the Carmel and Venice platforms, with Module 190 acting as the T2 Translator on the related VeniceR and CarmelR platforms used for DM-SMR variants in the wider 3.5-inch WD line, or on the HGST Command Code Based platform inherited from the HGST acquisition for 12TB and larger helium-sealed Purple Pro drives.
AllFrame and the ATA Streaming Command Set
AllFrame is WD's branding for an implementation of the ATA Streaming Command Set published in the ATA-8 ACS specification. The underlying commands are READ STREAM EXT, WRITE STREAM EXT, and CONFIGURE STREAM. The streaming feature set imposes a strict time budget on the firmware error-recovery state machine so the NVR write buffer never overflows while the drive is retrying a marginal sector.
The deliberate trade-off: when a write error occurs, the firmware skips the deeper ECC retry passes that a desktop WD Blue, Black, or Red drive would perform. A surveillance stream cannot afford a sector retry that lasts longer than the ring buffer can hold, so the firmware moves on. The side effect of that trade-off is that SMART attribute 5 (Reallocated Sectors Count) and SMART attribute 197 (Current Pending Sector Count) stay artificially clean while the platter degrades. By the time SMART 197 ticks up on a Purple, the underlying platter damage is usually well beyond the early-warning point a desktop drive would have surfaced.
The practical consequence for NVR operators: SMART status on a WD Purple is a lagging indicator, not a leading one. Audible clicking, dropped channels, or footage that stutters at fixed playback positions are usually the first real warnings that the drive needs to come out of service.
Workload Rate Limit and Head Wear Acceleration
Standard WD Purple is rated 180 TB/year and Purple Pro is rated 550 TB/year. These figures appear on the WD Purple datasheet and are not arbitrary marketing. They are statistical engineering thresholds tied to MTBF and AFR projections at the design workload. WRL is not a hard firmware lockout. The drive does not throttle, does not refuse writes, and does not log a "WRL exceeded" SMART attribute when the limit is crossed. Nothing in the firmware tells the operator the threshold has been passed.
What WRL exhaustion does cause is mechanical: continuous write current produces thermal fatigue on the magneto-resistive write elements; sustained write throughput elevates operating temperatures and continuous localized heating from the write element can accelerate depletion of the perfluoropolyether lubricant layer on the platters; rotational vibration in multi-bay enclosures compounds the effect by pushing the actuator into corrective oscillation. The combination of suppressed SMART surfacing through AllFrame and silent WRL exhaustion through the absence of any firmware warning is why surveillance Purples often arrive at the lab with several heads already degraded but no SMART flags raised.
DM-SMR WD Variants and the Module 190 T2 Translator
DM-SMR (Drive-Managed Shingled Magnetic Recording) variants of WD's 3.5-inch drives sit on platforms such as VeniceR and CarmelR, and store the indirect logical-to-physical mapping in Module 190, the T2 Translator. SMR drives group writes into shingled bands, and modifying any sector inside a band requires a read-modify-write of the entire band via the media-cache flush. If wall power drops during a flush, Module 190 loses synchronization between the LBA-to-PBA map and the actual platter state. The drive identifies normally and reports correct capacity, but read attempts return UNC or the drive holds the SATA bus in BSY.
The PC-3000 Express and Portable III workflow for a corrupted Module 190 follows a specific order. Apply a RAM patch to unlock the Service Area. Back up every accessible firmware module, with Module 190 prioritized so any usable copy is preserved before any modification. Engage the "Lock User Area writing" feature to freeze the corrupted translator and prevent the drive's background garbage collection from rewriting bands during diagnostics. Run the "Repair Module 190" function to reconstruct corrupted entries from band metadata. Load the rebuilt Module 190 into RAM so the patient operates from RAM rather than the corrupted on-platter copy. Image the drive via Physical Block Access (PBA), bypassing logical addressing entirely.
One non-obvious risk on PBA imaging of a partially flushed band: the dump can recover stale data the application thought it had committed, because the LBA-to-PBA map was mid-update when power dropped. NVR proprietary filesystems that distribute multiplexed video frames non-linearly across the disk benefit from a PBA dump followed by frame carving; HIKBTREE and DHFS index reconstruction is performed against the PBA image after the fact, never against the live drive.
Marvell Donor Matching Beyond the Family Code
Most published donor-matching guides stop at family code, capacity, and head count. For modern Marvell V2 Purple drives that is not enough. Four additional axes determine whether a donor will calibrate against the patient at all. Preamp vendor and revision must match exactly: Renesas, Broadcom, and Texas Instruments parts each ship with revision IDs that the read channel coefficients in the patient's adaptive tables are bound to. The microjog calibration values stored in Module 47 must fall within roughly 200 to 300 points of the patient's microjogs, or the read channel will not lock once the donor heads are installed. The Drive Configuration Matrix (DCM) character codes must align on the chassis and spindle markers, with the 5th character (typically a J or a 2) indicating the head stack vendor and serving as a critical mismatch flag. Firmware revision band compatibility determines whether the donor's Service Area module formats can be paired with the patient at all without a deeper firmware migration.
ROM adaptives are stored in the U12 SPI flash on the PCB and contain unique servo calibration and voltage settings for the original head stack. A donor PCB will not initialize the heads even if all four axes above match, because the servo coefficients and voltage offsets are bound to the patient. ROM extraction and rewrite is performed on a dedicated SPI programmer with the chip in a stable thermal state; it is never done by reflowing or hot-swapping the chip. The full donor-matching axis set is documented on how donor drives are matched in modern hard drive recovery, and the underlying recording-layer differences that drive the Module 190 workflow are covered on CMR vs SMR hard drives and translator implications.