Instruction Manual

128 Security Key and RAID Management
Instant Secure Erase
Instant Secure Erase is the process of permanently erasing all data on an
encryption-capable physical disk which is either unconfigured or foreign, and
resetting the security attributes. You need to execute Instant Secure Erase on
SEDs that are inaccessible (blocked) due to a lost or forgotten passphrase.
CAUTION: By executing Instant Secure Erase, the data on your
encryption-capable physical disk is lost.
Perform the following steps when instant secure erasing a physical disk:
1
Press <Ctrl><N> to access the PD Mgmt screen.
A list of physical disks is displayed. On the right menu, the physical disk
properties are displayed including information about whether the physical
disk is secured or not.
2 Press the down-arrow key to highlight a physical disk that is secured.
3 Press <F2> to display a menu of available actions.
4 The Secure Erase option is highlighted at the bottom of the menu.
5 Press <Enter> to Secure Erase the physical disk and select YES.
Troubleshooting Security Key Errors
Secured Foreign Import Errors
A foreign configuration is a RAID configuration that already exists on a
replacement physical disk that you install in a system. A secured foreign
configuration is a RAID configuration that was created under a different
security key. There are three scenarios in which a secured foreign import fails:
• The passphrase authentication fails— A virtual disk secured with a security
key different from the current controller security key cannot be imported
without authentication of the original passphrase used to secure them.
Supply the correct passphrase to import the secured foreign configuration.
If you have lost or forgotten the passphrase, the secured foreign disks
remain locked (inaccessible) until the appropriate passphrase is entered or
if they are instant secure erased.
• The secured virtual disk is in an offline state after supplying the correct
passphrase— You must check to determine why the virtual disk failed and
correct the problem. See "Troubleshooting" on page 131.
PERC7.2_UG.book Page 128 Thursday, March 3, 2011 2:14 PM