Equating Full Scans with Statistical Scans

Why does a full scan of SSD/NVMe result in lower analytical precision? SSD/NVMe drives have algorithms set by firmware between flash memory and the controller. The algorithm decides not to perform read/write operations on the flash for accesses deemed unnecessary. This has significantly sped up SSD/NVMe drives. However, it has also complicated fault determination.

Indeterminate sectors appear in clusters

Specific to flash, indeterminate sectors appear. These are sectors where reading fails, but writing may partially succeed or fail.

Structural Differences Unaddressable by Mere Adjustment of Full Scans

Due to simultaneous issues with firmware and flash-specific problems, minor adjustments to full scans are insufficient. This issue will undoubtedly become more problematic with data recovery in larger capacity SSD/NVMe drives. SSD/NVMe drives have already entered the terabyte era, and the time to store crucial data is approaching. Therefore, we sought early solutions and developed statistical scans. A while ago, when SSD/NVMe drives were around 256GB, the need for data recovery was low as they mostly contained system files. But now, with 2.0TB drives… it’s common to store and operate data beyond the system.

↑ Full Scan (Existing since v1 era, an inspection that calls every sector)
↑ 完全スキャン (v1時代からある、全セクタを呼び出す検査です)

↑ Reflecting Full Scan Results in Statistical Scans (Results from Full Scan → Reflected in Statistical Scan [Equated])
↑ 完全スキャンの結果を統計スキャンへ反映 (完全スキャンの結果→統計スキャンに反映[同一視])