User's Manual

Alerts 2146 Through 2150 Received While Performing I/O, Consistency

Check, Format, Or Other Operation

If you receive alerts 2146 through 2150 while performing an operation other than a rebuild, replace the

damaged disk immediately to avoid data loss.

Perform the following steps:

1. Back up the degraded virtual disk to a fresh (unused) tape drive.

2. Replace the damaged disk.

3. Perform a rebuild.

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 offline, the Offline 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 firmware at regular intervals to obtain temperature and status information. On some

enclosures, there is a short delay before the enclosure firmware reports the current temperature and

temperature probe status. This may cause a delay in displaying the correct temperature and temperature

probe status.