Skip Navigation Links | |
Exit Print View | |
![]() |
Sun Storage 6 Gb SAS REM RAID HBA Installation Guide For HBA Models SGX-SAS6-R-REM-Z and SG-SAS6-R-REM-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
Cannot Enter the Login Password for the GUI and CLI
Administrative Actions Are Inaccessible Through the MSM GUI
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
Application Event Notifications Are Not Displaying in the MSM GUI
Cannot Locate a Disk Because the Blue Ready-to-Remove LED Is Not Illuminated
Cannot Clear Controller Events From the UEFI HII Menu
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
The Advanced Software Options Feature on the WebBIOS Utility Menu Is Not Supported
Mouse Clicks Are Not Detected by the WebBIOS Utility
Cannot Tell, Through the WebBIOS Utility, When the Copyback Process Is Completed
“Invalid SAS Topology Detected” Error Occurs, Preventing the System From Booting
Cannot Boot the Operating System
NEM Removal Causes Virtual Disk Members to Be Displayed as (FOREIGN) Unconfigured Bad
Blue Ready-to-Remove LED Is Illuminated After Reinserting a Drive
Bug 15584190
Issue: If you attempt, through the MSM GUI, to connect to a host that does not have the MSM GUI software installed on it, the following Java exception and error messages might be displayed in the terminal from which you started the MSM GUI.
Socket connection to xxx.xxx.xxx.xxx failed once..try again Socket connection to xxx.xxx.xxx.xxx failed on retry Fatal Error : Can not create SASKernel object ! java.net.ConnectException: Connection refused at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at com.oracle.net.ssl.internal.ssl.SSLSocketImpl.connect(Unknown Source) at com.oracle.net.ssl.internal.ssl.SSLSocketImpl.<init>(Unknown Source) at com.oracle.net.ssl.internal.ssl.SSLSocketFactoryImpl.createSocket(Unknown Source) at Framework.Network.CachedSSLSocketFactory.createSocket(Unknown Source) at KernelNetwork.RAIDSocket.processCommand(Unknown Source) at SASKernel.SASKernel.queryServerList(Unknown Source) at GUI.RemoteServerPanel.scanRemoteServers(Unknown Source) at GUI.RemoteServerPanel$8.doInBackground(Unknown Source) at GUI.RemoteServerPanel$8.doInBackground(Unknown Source) at javax.swing.SwingWorker$1.call(Unknown Source) at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source) at java.util.concurrent.FutureTask.run(Unknown Source) at javax.swing.SwingWorker.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) .................Continued on next page..................
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) Terminating .... set: KEY=PERSISTENT_REM_FW_IP VAL=xxx.xxx.xxx.xxx (where "xxx.xxx.xxx.xxx" is the IP address of the non-MSM host.)
Workaround: Avoid connecting to a host that does not have the MSM GUI software installed on it. If you inadvertantly attempt such a connection through the MSM GUI, type the IP address of a known MSM GUI host in the IP Address text box, and click Discover Host. You can now safely ignore the error messages that are generated.