ssacli zero disk for media errors

[mr_vaughn]

Got the following message on a DL380 Gen10 P408i RAID10 Array running ESXi 6.7u3

I updated the firmware's the system everything, disks, conroller bios etc. 

1915 Slot # Smart Array - Drive media errors could not be recovered by RAID protection.Action: Backup and restore the data on the drive. Overwriting the affected blocks should resolve the media errors.

I did find the HPE Advisory "1716" or "1915" POST Error 

But issue is there are Zero command examples on how to "Erase all disks in the array using SSA/SSCLI with One-pass: Write all zeroes."

This has been my base for structuring and learning SSACLi commands.
https://kallesplayground.wordpress.com/useful-stuff/hp-smart-array-cli-commands-under-esxi/

This talks about the secure erase https://www.cloudhosting.lv/eng/faq/How-To-Secure-Erase-ESXi-Disks-HPE-or-Generic-Hardware , which is not the same and one-pass write all zero's correct?

If so I do see all disks support the Santize Erase but have concerns since some disks say 52min to erase and other over 3hours.

All disks are the same 15K 900Gb SAS HPE disks

Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)
Unrestricted Sanitize Supported: True

1. Is it the correct method to use the Sanitise erase to have it write all Zero's

2. Do i have to do this on each disk in the array?

3. Why the large time differences?

[mr_vaughn · Accepted solution]

I think I found my solution
https://support.hpe.com/resource3/docDisplay/pdfjs/web/viewer.html?file=%2Fhpesc%2Fpublic%2Fapi%2Fdocument%2Fdp00002635en_us%3Fv%3D1724321506000&locale=en-US&rangeChunkSize=256000&disableAutoFetch=false&disableCache=true&version=20241003140944#_OPENTOPIC_TOC_PROCESSING_d1561e4214

Erasing a Physical Drive
This section provides syntax to begin and stop the drive erase process.
Syntax:
To begin the drive erase process:
<target> modify [erasepattern= zero|random_zero|random_random_zero|crypto|block|
overwrite][unrestricted=on|off]
Where
• the <target> can be any valid physical drive
• block is for SSDs only
• overwrite is for HDDs only
• crypto, if implemented, is for both SSDs and HDDs
To stop the drive erase process:
<target> modify [stoperase]
Where
• the <target> can be any valid physical drive
• stoperase applies to zero, random_zero, and random_random_zero erase patterns only
• crypto, block, or overwrite drive erase processes cannot be stopped.
Example Commands:
=> ctrl slot=3 physicaldrive 1e:1:1 modify enableerasedrive
=> ctrl slot=3 physicaldrive 1e:1:1 modify erase erasepattern=zero
=> ctrl slot=3 pd 1e:1:1 modify stoperase
=> ctrl slot=3 physicaldrive 1e:1:1 modify erase erasepattern=crypto unrestricted=on

[Parvez_Admin]

@mr_vaughn ,

Excellent! Glad to know that you have found the solution. Thank you for sharing the steps.

[mr_vaughn]

Here is the command for ESXi for all disks on controller in slot 3

/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd all modify erase erasepattern=zero

but erase times are massive difference between models of the same HPE part number Drive for 15K 600Gb SAS drives

52min vs 3 hours14min. Why?

Firmware cannot be updated in ESXi 6.7 I cannot reboot Host to apply SPP offline either.

[root@ESXHOST:~] /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd all show detail |grep Erase
Status: Erase In Progress
Erase Pattern: zero
Erase Percent Complete: 3%
Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 0 hour(s), 52 minute(s)
Status: Erase In Progress
Erase Pattern: zero
Erase Percent Complete: 3%
Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 0 hour(s), 52 minute(s)
Status: Erase In Progress
Erase Pattern: zero
Erase Percent Complete: 3%
Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 0 hour(s), 52 minute(s)
Status: Erase In Progress
Erase Pattern: zero
Erase Percent Complete: 0%
Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)
Status: Erase In Progress
Erase Pattern: zero
Erase Percent Complete: 3%
Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 0 hour(s), 52 minute(s)
Status: Erase In Progress
Erase Pattern: zero
Erase Percent Complete: 0%
Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)
Status: Erase In Progress
Erase Pattern: zero
Erase Percent Complete: 0%
Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)
Status: Erase In Progress
Erase Pattern: zero
Erase Percent Complete: 0%
Sanitize Erase Supported: True
Sanitize Estimated Max Erase Time: 3 hour(s), 14 minute(s)
[root@ESXHOST:~] /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd all show detail |grep Model
Model: HPE EH000600JWCPL
Model: HPE EH000600JWCPL
Model: HPE EH000600JWCPL
Model: HPE EH000600JWHPN
Model: HPE EH000600JXLVT
Model: HPE EH000600JWHPN
Model: HPE EH000600JWHPN
Model: HPE EH000600JWHPN
[root@ESXHOST:~] /opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd all show detail |grep Firmware
Firmware Revision: HPD8
Firmware Revision: HPD8
Firmware Revision: HPD8
Firmware Revision: HPD7
Firmware Revision: HPD9
Firmware Revision: HPD7
Firmware Revision: HPD7
Firmware Revision: HPD7
[root@ESXHOST:~]

[mr_vaughn]

Further this command worked on the drive that got stuck at 0% for zero write.

/opt/smartstorageadmin/ssacli/bin/ssacli ctrl slot=3 pd 1I:2:4 modify erase erasepattern=overwrite unrestricted=off forced