Firmware + Fallback allows DriveErase to attempt firmware-based sanitization first and use an overwrite method if the firmware operation cannot complete. This approach is available in Pro, Enterprise, and Audit for compatible storage devices.
It can be useful when you are processing SSDs that normally support firmware sanitization but may encounter device-specific restrictions. For example, a SATA SSD may reject the requested ATA operation because of its security state, or an NVMe controller may refuse the required Format NVM command.
Fallback provides another way to attempt data removal, but the two methods do not necessarily provide the same coverage.
Configuring the fallback
When you select Firmware + Fallback, DriveErase identifies the applicable firmware method for the device and allows you to specify the overwrite profile to use if the firmware attempt fails.
Choose the fallback profile before starting the job. The method should be appropriate for the storage device and the outcome you require.
For a device where a logical overwrite is an acceptable alternative, a modern single-pass profile may be suitable. Selecting a large historical pass count does not resolve the limitations of flash memory areas that cannot be reached through ordinary logical writes.
What happens during execution
DriveErase first attempts the configured firmware operation. If the device accepts and completes that operation, the job proceeds according to the successful firmware result.
If the firmware method cannot complete, DriveErase records the available failure information and attempts the selected overwrite profile when the device remains accessible.
The fallback processes the logical storage range exposed through the controller and applies the selected overwrite method’s execution and verification requirements.
If neither method can complete, the final result records the unsuccessful operation.
Understanding the final outcome
A job using Firmware + Fallback can finish in several different ways. The preferred firmware method may succeed, the firmware method may fail while the overwrite succeeds, or both operations may fail or remain incomplete.
These outcomes have different implications. A successful logical overwrite after firmware failure can be useful, but it does not establish that the firmware operation was successful or that the same device-level coverage was achieved.
This distinction is especially important with SSDs. The overwrite fallback may reach the accessible logical range without reaching retired or remapped flash memory locations managed internally by the controller.
When fallback is appropriate
Use Firmware + Fallback when an overwrite is an acceptable alternative if the firmware method cannot be completed. This can be practical for general refurbishment workflows where the selected overwrite result meets the required conditions.
Do not rely on fallback when a successful device-level Purge is mandatory and logical overwriting is insufficient. In that situation, the firmware failure should lead to another suitable sanitization procedure or physical destruction.
After execution, review the final method, error information, verification evidence, and Actual Compliance result. The outcome must describe what was completed, not merely what DriveErase originally attempted.
