Users Guide

Read And Write Operations Experience Problems
If the system hangs, times out, or experiences other problems with read and write operations, then there may be a problem with the
controller cables or a device.
Related links
Cables Attached Correctly
Isolate Hardware Problems
A Task Menu Option Is Not Displayed
You may notice that the task menus do not always display the same task options. Some tasks are only valid for certain types of
objects or at certain times. For example, a Check Consistency task can only be performed on a redundant virtual disk. Similarly, if a
disk is already oine, the Oine task option is not displayed.
There may be other reasons why a task cannot be run at a certain time. For example, there may already be a task running on the
object that must complete before additional tasks can be run.
A Corrupt Disk Or Drive Message Suggests Running Autocheck During A Reboot
You can ignore the message and perform autocheck. The reboot completes after autocheck is completed. Depending on the size of
your system, it may take about 10 minutes.
Erroneous Status And Error Messages After A Windows Hibernation
Activating the Windows hibernation feature may cause Storage Management to display erroneous status information and error
messages. This problem resolves when the Windows operating system recovers from hibernation.
Storage Management May Delay Before Updating Temperature Probe Status
In order to display the enclosure temperature and temperature probe status, Storage Management polls the enclosure rmware at
regular intervals to obtain temperature and status information. On some enclosures, there is a short delay before the enclosure
rmware reports the current temperature and temperature probe status. This may cause a delay in displaying the correct
temperature and temperature probe status.
Related links
Changing The Warning Threshold On The Temperature Probe
Storage Management May Delay Displaying Storage Devices After Reboot
Storage Management requires time after a reboot to nd and inventory all attached storage devices. You may experience a delay in
storage controllers being displayed until this operation has completed.
You Are Unable To Log Into A Remote System
Ensure that you have connected to the system with administrator privileges and have provided the correct login details. The remote
system may be turned o or there may be network problems.
Cannot Connect To Remote System Running Microsoft Windows Server 2003
When connecting to a remote system running Windows Server 2003, log in to the remote system using an account that has
administrator privileges. By default, Windows Server 2003 does not allow anonymous (null) connections to access the SAM user
accounts. Therefore, if you are attempting to connect using an account that has a blank or null password, the connection may fail.
156