Users Guide

Multi-bit errors are more serious as they result in corrupted data and data loss. The following are the actions that occur in the
case of multi-bit errors:
● If a multi-bit error occurs while accessing data in the cache when the controller is started with dirty cache, the controller
discards the cache contents. The controller generates a warning message to the system console to indicate that the cache
was discarded and generates an event.
● If a multi-bit error occurs at run-time either in code/data or in the cache, the controller stops.
● The controller logs an event to the controller’s internal event log and a message during POST is displayed indicating a
multi-bit error has occurred.
NOTE: In case of a multi-bit error, contact Global Technical Support.
Preserved Cache State
The controller preserves the dirty cache from a virtual disk if the virtual disk goes offline or is deleted because of missing
physical disks. This preserved dirty cache is called pinned cache and is preserved until you import the virtual disk or discard the
cache.
1. Import the virtual disk—Power off the system, re-insert the virtual disk and restore the system power. Use the HII
Configuration Utility to import the foreign configuration.
2. Discard the preserved cache—See Clear the cache memory.
NOTE: It is recommended to clear the preserved cache before reboot using any of the virtual disks present on the
controller.
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 two 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 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.
Failure to select or configure non Self-Encrypting Disks non-SED
A virtual disk can be either secured or unsecured depending on how it was configured when created. In order to create a
secured virtual disk, the controller must have a security key present and must contain SEDs only. In order to select/configure
non-SED, you must create an unsecured virtual disk. You can create an unsecured virtual disk even if there is a security key.
Select the Secure VD option as No in the Create New VD menu. For steps on how to create an unsecured virtual disk, see
Create virtual disks.
Failure to delete security key
A security key is used to lock or unlock access to a security-enabled component. This key is not utilized in the actual encryption
of data. If a security key is present, both secured and unsecured virtual disks may exist.
To delete the security key, you must have a previously established security key present on the controller and there cannot be
any configured secured disks. If there are configured secured virtual disks, remove or delete them.
72
Troubleshooting