Applies to: Pro, Enterprise, and Audit
Supported target
Use SCSI Sanitize – Block Erase for a compatible directly attached SAS solid-state drive or supported SCSI direct-access block device. The controller or HBA must pass the required SCSI sanitize command to the target.
Operation
The device performs its internal block-erase sanitization operation and reports status through the SCSI command path. DriveErase monitors the operation and records the returned result.
Controller considerations
Enterprise SAS storage is frequently presented through RAID controllers or HBAs. These components can:
- Expose a logical volume instead of the physical drive;
- Hide serial or media information;
- Block sanitize commands;
- Require controller-specific pass-through modes;
- Intercept status or error responses.
A physical disk displayed by a controller-management utility is not automatically exposed as a sanitizable physical disk to DriveErase.
Compliance interpretation
A completed supported SCSI block-erase operation can have Purge potential under applicable sanitization guidance. The final report considers the actual command, device type, completion status, and available evidence. Do not state Purge solely because SCSI Sanitize was selected.
Recommended workflow
- Confirm that the target is an individually exposed SAS SSD.
- Record enclosure, bay, model, serial, and capacity.
- Confirm HBA or controller pass-through support.
- Use Firmware + Fallback only where the fallback’s logical scope is acceptable.
- Preserve controller and DriveErase evidence when the asset-disposition process requires independent identity mapping.