Sanitize Drive
Overview
This function starts a data sanitization process for drives.
A data sanitization process is not complete with the execution of this function. This function is completed when the data deletion process for the selected drive is successfully started.
Perform the start maintenance operation by using the [Start/End Maintenance] function before starting a drive data sanitization. If the operation has not been performed, [Sanitize Drive] cannot be clicked.
Web GUI or CLI cannot stop a drive data sanitization that is already in progress.
If this function is continuously executed, this function may stop due to an error.
This function cannot be used for some drive types. If these drives are selected and this function is started, this function stops due to an error.
- This function cannot be used when one of the following drives is selected.
Drives without the "Present" state and the "Broken" state
Drives that are registered in RAID groups, TPPs, FTRPs, or REC Disk Buffers
Drives that are used as Extreme Cache Pools
Drives used as a "Global Hot Spare" or a "Dedicated Hot Spare"
After a data sanitization is started, the data deletion processes for the multiple drives operate almost in parallel. The required time for deleting data depends on the drive capacity. Estimate the required time for deleting the data from the largest drive capacity. It takes approximately 0.6s/GB for SSDs, 15s/GB for online disks, and 20s/GB for Nearline disks to delete data.
To perform operations such as removing drives after a data sanitization for drives in the "Broken" state, wait the estimated time that was calculated from the drive type and capacity, and then start the next procedure.
If this function is started, event logs are output when the data sanitization is started and completed. However, the completion event log is not output for drives in the "Broken" state. To check the completion of the data sanitization via the event logs, use the [Force Enable Module] function to change the drive state to "Present" and then start this function. If the drive remains in the "Broken" state even after executing the [Force Enable Module] function, the process is assumed completed when the process time that is estimated from the drive type and capacity has passed. Refer to Note of this function for details.
- Do not perform any of the following operations when a data sanitization is in progress.
Turning off/on the storage system
Using the drive maintenance functions (or using the [Hot Preventive Maintenance] function, the [Force Enable Module] function, the [Force Disable Module] function, the [Remove Disk Drive] function, or performing a hot maintenance of the failed drives without the use of Web GUI)
Using the CM maintenance functions (or using the [Hot Preventive Maintenance] function, the [Force Enable Module] function, the [Force Disable Module] function, or performing a hot maintenance of the failed CMs without the use of Web GUI)
Application of the controller firmware or disk firmware
Obtaining the G-List
Executing functions that access drives (such as creating volumes)
Eco-mode
Rebooting all CMs
Disk diagnosis
If prohibited operations are performed or a power failure occurs when data is being deleted, re-execute this function. If a drive failure occurs due to an operation, use the [Force Enable Module] function to activate the drive in the storage system.
Disk drive patrol is suspended when data is being deleted. After the data sanitization is complete, the disk drive patrol is automatically resumed.
The drive lifetime information (or remaining life) cannot be obtained when data is being deleted. A "-" (hyphen) is displayed for the "Health" of the drive. Refer to the [Drives] function for details.
Drives can be re-used after the data is deleted. To re-use the drives, perform one of the following operations.
Re-insert the drives
Use the [Force Disable Module] function and the [Force Enable Module] function
When this function is started, the "Sanitize Start" event log is output for each drive.
For sanitization of drives in the "Present" state, check for the completion of the sanitization indicated by the "Sanitize Complete" event log. Refer to "About "Sanitize Complete" Event Log" for details.
For sanitization of drives in the "Broken" state, the "Sanitize Complete" event log is not output. Therefore, the process is assumed completed when the process time that is estimated from the drive type and capacity has passed. It takes approximately 0.6s/GB for SSDs, 15s/GB for online disks, and 20s/GB for Nearline disks to sanitize data.
Refer to the [Display/Delete Event Log] function for details about the event logs.
About "Sanitize Complete" Event Log
The "Sanitize Complete" event log is output when the data sanitization in each drive type is completed for each controller.
For example, when the data sanitization is performed for ten Online SAS disks that are in the "Present" state on CM#0, ten "Sanitize Start" event logs are output and one "Sanitize Complete" event log is output for the ten Online SAS disks.
Completion of the data sanitization process can be checked via the "Sanitize Complete" event log that corresponds to the "Sanitize Start" event log. The corresponding event logs are recognized by the following controller and drive type.
Controller
CM number
Drive type
Output result of "Sanitize Start" and "Sanitize Complete":
Sanitize Start Sanitize Complete 15000 rpm or 10000 rpm
HDD Online
7200 rpm
HDD Nearline
SSD
SSD
User Privileges
Availability of Executions in the Default Role
| Default role | Availability of executions |
|---|---|
| Monitor | |
| Admin | |
| StorageAdmin | |
| AccountAdmin | |
| SecurityAdmin | |
| Maintainer |
Refer to "User Roles and Policies" for details on the policies and roles.
Operating Procedures
Select the drive to sanitize data (multiple selections can be made) and click [Sanitize Drive] in [Action].
→ A confirmation screen appears.
Click the [OK] button.
→ The drive data sanitization process starts.
Click the [Done] button to return to the screen when starting this function in Step 1.