Skip Navigation Links | |
Exit Print View | |
Sun Storage 6 Gb SAS PCIe RAID HBA, Internal Installation Guide For HBA Models SGX-SAS6-R-INT-Z and SG-SAS6-R-INT-Z |
Chapter 2 Hardware Installation and Removal
Chapter 3 Creating a Bootable Drive in a Preboot Environment
Chapter 4 HBA Software Installation
MegaRAID Storage Manager-Related Issues
BackingStoreException Error Messages Occur When Trying to Start the GUI
Debug Messages Are Displayed in the Terminal Window
Error Messages Are Displayed When Attempting to Connect to Another Host
Cannot Enter the Login Password for the GUI and CLI
Cannot Create a Drive Group Through the MSM GUI
sas_snmp and sas_ir_snmp Errors Occur During the MSM GUI Installation
Connection Refusal Error Messages Occur When Trying to Start the MSM GUI
Monitoring System Is Displayed as a MegaRAID Server in the MSM GUI
MSM GUI Is Not Starting After Becoming the root User
Cannot Locate a Disk Because the Blue Ready-to-Remove LED Is Not Illuminated
Cannot Save Controller Events From the UEFI HII Menu
Cannot Clear Controller Events From the UEFI HII Menu
The Advanced Software Options Feature on the WebBIOS Utility Menu Is Not Supported
Mouse Actions Are Erratic When Using the WebBIOS Utility
MegaCLI Log Files Are in the /tmp Directory
Unsupported RAID Levels Are Displayed in the MegaCLI Utility
Error Message Occurs After Issuing the MegaCli64 -AdpAlILog -aALL Command
Mouse Clicks Are Not Detected by the WebBIOS Utility
Cannot Tell, Through the WebBIOS Utility, When the Copyback Process Is Completed
Cannot Boot the Operating System
Blue Ready-to-Remove LED Is Illuminated After Reinserting a Drive
Bug 15625059
Issue: After rebooting a server that is running the SLES 11 OS, and upon launching the MSM GUI, the MSM GUI might detect the server, but the hostname/OS type data might not be visible, and administrative actions might be inaccessible (grayed out).
Workaround: Close all MSM GUI windows and issue the following command to restart the vivaldiframeworkd service:
# service vivaldiframeworkd restart
You can now restart the MSM GUI and administrative actions will be accessible.