No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

Huawei V2 and V3 Server RAID Controller Card User Guide 36

This document describes the appearances and features of the redundant array of independent disks (RAID) controller cards, how to configure properties for the RAID controller cards, and how to install drivers. The RAID controller cards include the LSI SAS2208, LSI SAS2308, LSI SAS3008, LSI SAS3108, LSI SoftRAID, PM8060, and PM8068.
Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Common Boot Error Messages for RAID Controller Cards

Common Boot Error Messages for RAID Controller Cards

Table A-5 describes the boot error messages present in the MegaRAID firmware.

Table A-5 Boot error messages

Message Number

Boot Message Description

Troubleshooting Action

1

Memory or battery problems were detected.

The adapter has recovered, but cached data was lost.

Press any key to continue, or press C to load the configuration utility.

Cause: The cached data is lost and cannot be retrieved.

Action: Perform memory and battery tests. If needed, replace the RAID controller card or the battery.

2

This is a test message. You can press a key to ignore it, or you can wait five seconds.

No further action is required.

Press any key to continue, or press C to load the configuration utility.

This is a test message. You can press any key to ignore it or wait five seconds. No further action is required.

3

Firmware version inconsistency was detected. The adapter has recovered, but cached data was lost.

Press any key to continue, or press C to load the configuration utility.

Cause: Firmware versions are inconsistent. The adapter has recovered, but cached data was lost.

Action: Ensure that the other controller also has the same firmware version.

4

Foreign configuration(s) found on adapter.

Press any key to continue or press C to load the configuration utility or press F to import foreign configuration(s) and continue.

Cause: A storage device was inserted with the metadata that does not belong to any RAID arrays recognized by the controller.

Action: Either import the configuration settings of the inserted storage device or delete the RAID array.

5

Previous configuration cleared or missing.

Importing configuration created on %02d/%02d%2d:%02d.

Press any key to continue, or press C to load the configuration utility.

Cause: The controller is not able to recognize the current RAID array configuration.

Action: Either import the configuration settings or delete the foreign configuration found on the storage device.

6

Firmware package: %s

N/A

7

Firmware version: %s

N/A

8

This firmware is a TEST version. It has not completed any validation.

Cause: The controller is not able to recognize the current RAID array configuration.

Action: Update the firmware to the correct version.

9

This firmware is an ALPHA version – It has not completed all validation.

The validation stamp is:

%s"""

Cause: The controller is not able to recognize the current RAID array configuration.

Action: Update the firmware to the correct version.

10

This firmware is BETA version – It has not completed all validation.

The validation stamp is:

%s"""

Cause: The controller is not able to recognize the current RAID array configuration.

Action: Update the firmware to the correct version.

11

An enclosure was found that contains both SAS and SATA drives, but

this controller does not allow mixed drive types in a single enclosure.

Correct the problem then restart your system.

Press any key to continue, or press C to load the configuration utility.

Cause: A single enclosure that has both SAS and SATA drives cannot be used because the controller does not support mixed drive types in a single enclosure.

Action:

  • Use only one type of drive, either SAS or SATA drive.
  • Replace the controller with a controller that supports mixed drive types in a single enclosure.
  • Contact technical support to enable this feature.

12

SAS drives were detected, but this controller does not support SAS drives.

Remove the SAS drives then restart your system.

Press any key to continue, or press C to load the configuration utility.

Cause: This controller does not support SAS drives.

Action: Replace the SAS drives with SATA drives and restart the system.

13

SATA drives were detected, but this controller does not support SATA drives.

Remove the SATA drives then restart your system.

Press any key to continue, or press C to load the configuration utility.

Cause: This controller does not support SATA drives.

Action: Replace the SATA drives with SAS drives and restart the system.

14

There are %d enclosures connected to connector %s, but only maximum of %d enclosures can be connected to a single SAS connector.

Remove the extra enclosures then restart your system.

Cause: This controller supports only a particular number of enclosures.

Action: Remove extra enclosures or insert a controller that supports your enclosure requirements.

15

Invalid SAS topology detected.

Check your cable configurations, repair the problem, and restart your system.

Cause: The controller has detected an invalid SAS topology.

Action: Check the cables or reconfigure the attached devices to create a valid SAS topology.

16

The battery is currently discharged or disconnected. Verify the connection and allow 30 minutes for charging.

If the battery is properly connected and it has not returned to operational state after 30 minutes of charging then contact technical support for additional assistance.

Cause: The battery is currently discharged or disconnected.

Action:

  • Check the battery cable to ensure that it is connected properly.
  • Ensure that the battery is charging properly.
  • Contact technical support to replace the battery if the battery is draining out.

17

The battery hardware is missing or malfunctioning, or the battery is unconnected, or the battery could be fully discharged.

If you continue to boot the system, the battery-backed cache will not function. If battery is connected and has been allowed to charge for 30 minutes and this message continues to appear, contact technical support for assistance.

Press D to disable this warning (if your controller does not have a battery)

Cause: The battery hardware is missing or malfunctioning, or the battery is unconnected, or the battery could be fully discharged.

Action:

  • Check the battery cable to ensure that it is connected properly.
  • Ensure that the battery is charging properly.
  • Contact technical support to replace the battery if the battery is draining out.

18

Invalid SAS Address present in MFC data.

Program a valid SAS Address and restart your system.

Cause: An invalid SAS address is in the MFC data.

Action:

  1. Power off the system and remove the controller.
  2. Contact technical support to re-program the SAS address.

19

Some configured disks have been removed from your system, or are no longer accessible.

Check your cables and also make sure all disks are present.

Press any key to continue, or press C to load the configuration utility.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.

20

The following VDs have missing disks: %s.

If you proceed (or load the configuration utility), these VDs will be marked OFFLINE and will be inaccessible.

Check your cables and make sure all disks are present.

Press any key to continue, or press C to load the configuration utility.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.

21

The following VDs are missing: %s.

If you proceed (or load the configuration utility), these VDs will be removed from your configuration.

If you wish to use them at a later time, they will have to be imported. If you believe these VDs should be present, power off your system and check your cables to make sure all disks are present.

Press any key to continue, or press C to load the configuration utility.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.

22

The following VDs are missing complete spans: %s. If you proceed (or load the configuration utility), these VDs will be removed from your configuration and the remaining drives marked as foreign.

If you wish to use them at a later time, restore the missing span(s) and use a foreign import to recover the VDs.

If you believe these VDs should be present, please power off your system and check your cables to make sure all disks are present.

Press any key to continue, or press C to load the configuration utility.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.

23

All of the disks from your previous configuration are gone. If this is an unexpected message, power off your system and check your cables to make sure all disks are present.

Press any key to continue, or press C to load the configuration utility.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.

24

The cache contains dirty data, but some VDs are missing or will go offline, so the cached data can not be written to disk. If this is an unexpected error, power off your system and check your cables to make sure all disks

are present. If you continue, the data in cache will be permanently discarded.

Press X to acknowledge and permanently destroy the cached data.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.

25

Your VDs that are configured for Write-Back are

temporarily running in Write-Through mode. This is caused by the battery being charged, missing, or bad.

Allow the battery to charge for 24 hours before evaluating the battery for replacement. The following VDs are affected: %s

Press any key to continue.

Cause: Your VDs that are configured for Write-Back are temporarily running in Write-Through mode. This is caused by the battery being charged, missing, or bad.

Action:

  • Check the battery cable to ensure that it is connected properly.
  • Ensure that the battery is charging properly.
  • Contact technical support to replace the battery if the battery is draining out.

26

Invalid memory configuration detected.

Contact your system support. System has halted.

Cause: The memory configuration is invalid.

Action: Replace the RAID controller card.

27

Cache data was lost due to an unexpected power-off or reboot during a write operation, but the adapter has recovered. This could be because of memory problems, bad battery, or you might not have a battery installed.

Press any key to continue or C to load the configuration utility.

Cause: Cache data was lost due to an unexpected power-off or reboot during a write operation, but the adapter has recovered. This could be because of memory problems, bad battery, or you might not have a battery installed.

Action:

  • Check the battery cable to ensure that it is connected properly.
  • Ensure that the battery is charging properly.
  • Contact technical support to replace the battery if the battery is draining out.

28

Entering the configuration utility in this state will result in drive configuration changes.

Press Y to continue loading the configuration utility or power off your system and check your cables to make sure all disks are present and reboot the system.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.
  • If the controller is being used to create new configurations by reusing the drives, clear the existing data and continue.

29

Multibit ECC errors were detected on the RAID controller. If you continue, data corruption can occur.

Contact technical support to resolve this issue.

Press X to continue, otherwise power off the system, replace the controller, and reboot.

Cause: Multibit ECC errors were detected on the RAID controller. If you continue, data corruption can occur.

Action:

  1. Replace the RAID controller card.
  2. If the fault persists, contact technical support.

30

Single-bit ECC errors were detected on the RAID controller.

Contact technical support to resolve this issue.

Press X to continue or else power off the system, replace the controller, and reboot.

Cause: Single-bit ECC errors were detected on the RAID controller.

Action:

  1. Replace the RAID controller card.
  2. Restart the system.
  3. If the fault persists, contact technical support.

31

Single-bit overflow ECC errors were detected on the RAID controller. If you continue, data corruption can occur.

Contact technical support to resolve this issue.

Press X to continue or else power off the system, replace the controller, and reboot.

Cause: Single-bit overflow ECC errors were detected on the RAID controller. If you continue, data corruption can occur.

Action:

  1. Replace the RAID controller card.
  2. Restart the system.
  3. If the fault persists, contact technical support.

32

Multibit ECC errors were detected on the RAID controller. The DIMM on the controller needs replacement.

Contact technical support to resolve this issue. If you continue, data corruption can occur.

Press X to continue, otherwise power off the system and replace the DIMM module and reboot. If you have replaced the DIMM press X to continue.

Cause: Multibit ECC errors were detected on the RAID controller.

Action:

  1. Replace the RAID controller card.
  2. Restart the system.
  3. If the fault persists, contact technical support.

33

Single-bit ECC errors were detected during the previous boot of the RAID controller. The DIMM on the controller needs replacement.

Contact technical support to resolve this issue.

Press X to continue, otherwise power off the system and replace the DIMM module and reboot. If you have replaced the DIMM press X to continue.

Cause: Single-bit ECC errors were detected during the previous boot of the RAID controller.

Action:

  1. Replace the RAID controller card.
  2. Restart the system.
  3. If the fault persists, contact technical support.

34

Single-bit overflow ECC errors were detected during the previous boot of the RAID controller. The DIMM on the controller needs replacement.

Contact technical support to resolve this issue. If you continue, data corruption can occur.

Press X to continue, otherwise power off the system and replace the DIMM module and reboot. If you have replaced the DIMM press X to continue.

Cause: Single-bit overflow ECC errors were detected during the previous boot of the RAID controller.

Action:

  1. Replace the RAID controller card.
  2. Restart the system.
  3. If the fault persists, contact technical support.

35

The attached enclosure does not support in controller's Direct mapping mode.

Contact your system support.

The system has halted because of an unsupported configuration.

Cause: Too many chained enclosures may be present. This message may also be related to a security feature in the drive.

Action:

  • Remove the drives that are not supported.
  • Reduce the number of drives.
  • Replace the enclosure with another one.
  • Ensure that the firmware version is updated.
  • If the fault persists, contact technical support.

36

Expander detected in controller with direct mapping mode.

Reconfiguring automatically to persistent mapping mode. Automatic reboot would happen in 10 seconds.

Cause: An expander is detected on the controller in the direct mapping mode.

Action: No action is required. The controller will configure itself to a persistent mapping mode and reboot.

If the fault persists, contact technical support.

37

Your controller's I/O processor has a fault

that can potentially cause data corruption. Your controller needs replacement.

Contact your system support.

To continue, press Y to acknowledge.

Cause: Your controller's I/O processor has a fault that can potentially cause data corruption.

Action: Contact technical support to replace the controller.

38

The number of disks exceeded the maximum supported count of %d disks.

Remove the extra drives and reboot system to avoid losing data.

Press Y to continue with extra drives.

Cause: The number of disks exceeds the upper limit.

Action:

  • Power off the system and remove the controller.
  • Remove the extra drives to reduce the size of the topology.
  • Replace the controller with a controller that supports a larger topology.

39

The number of devices exceeded the maximum limit of devices per

quad. Remove the extra drives and reboot the system to avoid losing data.

System has halted due to unsupported configuration.

Cause: The number of disks exceeds the upper limit.

Action:

  • Power off the system and remove the controller.
  • Remove the extra drives to reduce the size of the topology.
  • Replace the controller with a controller that supports a larger topology.

40

A discovery error has occurred, power cycle the system and all the enclosures attached to this system.

Cause: A discovery error has occurred, power cycle the system and all the enclosures attached to this system.

Action:

  • Shutdown and restart the system as well as all the enclosures attached to the system.
  • Ensure that all cables are correctly connected. Reduce the topology in case of a bad drive.
  • If the fault persists, collect the logs of the system, driver, and firmware and contact technical support.

41

Drive security is enabled on this controller and a pass phrase is required. Enter the pass phrase.

Cause: Drive security is enabled on this controller and a password is required.

Action: Enter the password.

42

Invalid pass phrase. Enter the pass phrase.

Cause: The password is invalid.

Action: Enter a valid password.

43

There was a drive security key error. All secure drives will be marked as foreign.

Press any key to continue, or C to load the configuration utility.

Cause: There was a drive security key error. All secure drives will be marked as foreign.

Action: Check if the controller supports self-encrypting drives.

44

Invalid pass phrase. If you continue, a drive security key error will occur and all secure configurations will be marked as foreign.

Reboot the machine to retry the pass phrase or press any key to continue.

Cause: The password is invalid.

Action: Restart the system to retry the password or press any key to continue.

45

Unable to communicate to EKMS. If you continue, there will be a drive security key error and all secure configurations will be marked as foreign.

Check the connection with the EKMS, reboot the machine to retry the EKMS or press any key to continue.

Cause: Failed to communication with the EKMS.

Action: Check the connection of the EKMS and restart the system to re-establish the connection to the EKMS.

46

Unable to change security to EKMS as not able to communicate to

EKMS. If you continue, the drive security will remain to existing security mode.

Check the connection with the EKMS, reboot the machine to retry the EKMS or press any key to continue.

Cause: Failed to communication with the EKMS and change the security mode to EKMS

Action: Check the connection of the EKMS and restart the system to re-establish the connection to the EKMS.

47

DKM existing key request failed; existing secure configurations will be labeled foreign and will not be accessible.

Reboot the server to retry.

Cause: DKM existing key request failed. Existing secure configurations will be labeled foreign and will not be accessible.

Action: Check the connection of the EKMS and restart the system to re-establish the connection to the EKMS.

48

DKM new key request failed; controller security mode transition was not successful.

Reboot the server to retry request, or press any key to continue.

Cause: DKM new key request failed. Controller security mode transition was not successful.

Action: Check the connection of the EKMS and restart the system to re-establish the connection to the EKMS.

49

Firmware did not find valid NVDATA image.

Program a valid NVDATA image and restart your system.

Press any key to continue.

Cause: Firmware did not find valid NVDATA image.

Action:

  • Update the correct firmware package that has a proper NV data image.
  • Check the current firmware version, and if needed, update to the latest firmware version. Updating to the latest firmware version may require importing foreign volumes.

50

IR to MR Migration failed.

Press any key to continue with MR defined NVDATA values

Cause: IR to MR migration failed. Press any key to continue with MR defined NVDATA values.

Action: None

51

Two BBUs are connected to the adapter. This is not a supported configuration. Battery and caching operations are disabled. Remove one BBU and reboot to restore battery and caching operations. If dirty cache is lost in this boot, that could have been because of dual battery presence.

Cause: Two BBUs are connected to the adapter. This is not a supported configuration. Battery and caching operations are disabled.

Action: Remove one BBU and reboot to restore battery and caching operations.

If dirty cache is lost in this boot, that could have been because of dual battery presence.

52

Offline or missing virtual drives with preserved cache exist.

Check the cables and make sure that all drives are present.

Press any key to continue, or C to load the configuration utility.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.
  • Cache offload occurs if the missing drive is restored.

53

Offline or missing virtual drives with preserved cache exist.

Check the cables and make sure that all drives are present.

Press any key to enter the configuration utility.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.
  • Cache offload occurs if the missing drive is restored.

54

Invalid SAS Address present in SBR. Contact

your system support.

Press any key to continue with Default SAS Address.

Cause: An invalid SAS address is in the SBR.

Action: Contact technical support to restore to factory default values.

55

Incompatible secondary iButton present!

Insert the correct iButton and restart the system.

Press any key to continue but OEM specific features will not be upgraded!

Cause: Incompatible RAID keys exist.

Action: Insert the correct RAID keys and restart the system. If the fault persists, contact technical support engineers to replace the RAID key.

56

Upgrade Key Missing! An upgrade key was present on a previous power cycle, but it is not connected.

This can result in inaccessible data unless it is addressed.

Re-attach the upgrade key and reboot.

Cause: An upgrade key that was present on a previous power cycle may not be connected.

Action: Reattach the upgrade key and restart the system. If the fault persists, contact technical support to replace the upgrade key.

57

The native configuration is not supported by the controller.

Check the controller, iButton or key-vault. If you continue the configuration will be marked foreign.

Press any key to continue.

Cause: The native configuration is not supported by the controller.

Action: Insert the correct RAID keys and restart the system. If the fault persists, contact technical support to replace the RAID key.

58

The battery is currently discharged or disconnected. Verify the connection and allow 30 minutes for charging. If the battery is properly connected and it has not returned to operational state after 30 minutes of charging, contact technical support for additional assistance.

Press D to disable this warning (if your controller does not have a battery).

Cause: The battery is currently discharged or disconnected.

Action:

  • Check the battery cable to ensure that it is connected properly.
  • Ensure that the battery is charging properly.
  • Contact technical support to replace the battery if the battery is draining out.

59

The battery is currently discharged or disconnected. VDs configured in

Write-Back mode will run in Write-Through mode to protect your data and will return to the Write-Back policy when the battery is operational.

If VDs have not returned to Write-Back mode after 30 minutes of charging then contact technical support for additional assistance.

The following VDs are affected: %s.

Press any key to continue.

Cause: The battery is currently discharged or disconnected. VDs configured in Write-Back mode will run in Write-Through mode to protect your data and will return to the Write-Back policy when the battery is operational.

Action:

  • Check the battery cable to ensure that it is connected properly.
  • Ensure that the battery is charging properly.
  • Contact technical support to replace the battery if the battery is draining out.

60

Cache data was lost, but the controller has recovered. This could be because your controller had protected cache after an unexpected power loss and your system was without power longer than the battery backup time.

Press any key to continue or C to load the configuration utility.

Cause: Cache data was lost, but the controller has recovered. This could be because your controller had protected cache after an unexpected power loss and your system was without power longer than the battery backup time.

Action:

  • Check the memory and battery.
  • Check the voltage levels and cache offload timing in case of power loss.
  • If necessary, replace the memory or battery.

61

A snapshot rollback is in progress on VDs %s, the controller cannot boot until the rollback operation completes.

Press any key to enter the configuration utility.

Cause: A snapshot rollback is in progress on VDs. The controller cannot boot until the rollback operation completes.

Action: Wait for some time until the rollback is complete.

62

The following VDs: %s have Rollback active and the corresponding Repository is missing. If you continue to boot the system or enter the configuration utility, these VDs will become unusable.

Press any key to Continue.

Cause: This may be related to the snapshot feature, which is not supported on MegaRAID 12Gb/s SAS RAID controllers.

Action: Wait for some time until the rollback is complete.

63

Snapshot Repository VDs %s have been removed from your system, or are no longer accessible.

Check the cables and make sure all disks are present. If you continue to boot the system, the snapshot related data will be lost.

Press any key to continue, or C to load the configuration utility.

Cause: The controller is unable to find the configured drives.

Action:

  • Check if the configured drives are present and they are properly connected.
  • Access the BIOS and check if the devices are displayed.
  • Ensure that the drives are spun-up and have power supplied to them.
  • If there is a backplane, check the connector to ensure that power is being supplied to the drive.

64

The most recent configuration command could not be committed and must be retried.

Press any key to continue, or C to load the configuration utility.

Cause: The most recent configuration command could not be committed and must be retried.

Action: None

65

Firmware could not synchronize the configuration or property changes for some of the VD's/PD's.

Press any key to continue, or C to load the configuration utility.

Cause: Firmware could not synchronize the configuration or property changes for some of the VD's/PD's.

Action: Press any key to continue or press C to load the Configuration Utility. If the fault persists, contact technical support.

66

On-board expander firmware or manufacturing image is corrupted. The flash expander firmware and manufacturing image use the recovery tools.

Cause: The expander has a software failure.

Action:

Contact technical support.

67

The native configuration is not supported by the current firmware.

Make sure that the correct controller firmware is being used. If you continue, the configuration will be marked as foreign.

Press any key to continue.

Cause: The native configuration is not supported by the current firmware.

Action:

  • Collect the logs of the system, driver, and firmware.
  • Ensure that the firmware version is correct and updated to the latest version.
  • If the fault persists, contact technical support.

68

Foreign configuration import did not import any drives.

Press any key to continue.

Cause: The foreign configuration import function did not import any drives.

Action:

  • Check the firmware version of the controller.
  • Replace the controller and try again.
  • If the fault persists, contact technical support.

69

Valid memory detected. Firmware is upgraded from iMR to MR.

Reboot the system for the MR firmware to run.

Cause: The memory is detected. The firmware is upgraded from iMR to MR.

Action: Reboot the system for the MR firmware to run.

70

Advanced software options keys were detected, features activated – %s.

Cause: Advanced software options keys were detected and the feature is being activated.

Action: None

71

Advanced software options keys were missing, features deactivated – %s.

Cause: Advanced software options keys were missing and the feature is being disabled.

Action:

  • Check the cable connection.
  • Check for the Advanced Software Options key.
  • If the fault persists, contact technical support.

72

Cannot communicate with iButton to retrieve premium features. This is probably because of extreme temperatures.

The system has halted!

Cause: Failed to communicate with RAID keys to retrieve premium features. This is probably because of extreme temperatures.

Action:

  • Check the cable connection.
  • Ensure that the RAID keys are present.
  • Check the ambient temperature near the RAID keys.
  • If the fault persists, contact technical support.

73

Consecutive power loss detected during I/O transactions on non-optimal write-back volumes. This might have resulted in data integrity issues.

Press 'X' to proceed.

Cause: Consecutive power loss was detected during I/O transactions on non-optimal write-back volumes. This might have resulted in data integrity issues.

Action:

  • Check if the controller is securely locked in the PCI slot.
  • Check the power supply, battery, and supercapacitor.
  • If you find any hardware defect, contact technical support.

74

USB cache device is not responding.

Power down the system for 2 minutes to attempt recovery and avoid cache data loss, and then power-on.

Cause: The USB cache device is not responding.

Action:

  • The LSI SAS2208 controller supports USB cache offload. Ensure that USB cache is present and secure.
  • Reseat and replace the USB cache.
  • Power off the system for 2 minutes to attempt recovery and avoid cache data loss, then power on the system.

75

Bad or missing RAID controller memory module detected.

Press D to downgrade the RAID controller to iMR mode.

Warning! Downgrading to iMR mode, might result in incompatible Logical drives.

Press any other key to continue, controller shall boot to safe mode.

Cause: The memory module of the RAID controller is damaged or lost.

Action: Replace the RAID controller card.

Translation
Download
Updated: 2019-11-01

Document ID: EDOC1000004186

Views: 751566

Downloads: 20670

Average rating:
This Document Applies to these Products
Related Version
Related Documents
Share
Previous Next