Users Guide

Shared PERC 8 card has yellow exclamation mark in device

manager

Issue: The device is displayed in Device Manager but has a yellow exclamation mark (!).

Corrective Action: Reinstall the driver. For more information on reinstalling drivers, see Driver Installation. If reinstalling the driver does

not resolve the yellow exclamation mark, perform a shutdown of all server modules and power cycle the chassis.

Incorrect number of virtual disks displayed in Windows Disk

Manager

Issue: The number of disks displayed in Windows Disk Manager is more than the actual number of virtual disks assigned

to the server.

Corrective Action: This issue occurs if the MPIO feature is not installed in systems with the Fault Tolerant Shared PERC 8 card

conguration. Install MPIO services from the list of features that can be installed on the server. For instructions on

how to install MPIO, see Installing and Conguring MPIO at technet.microsoft.com.

Controller issues

Controller cache issues

For certain conditions virtual drives are either not congured to write back caching or if congured, it transitions to write-through caching.

The status of write-back caching can be viewed through CMC storage logs.

The following table details the conditions and the corrective actions.

Table 6. Conditions and the corrective actions

Conditions Actions

Peer controllers reporting incompatibility due to mismatched

controller settings

When the active controller does not have any native congurations

and imports a foreign conguration, the active controller inherits the

controller conguration settings stored with the virtual disk. These

settings may dier from the settings present on the peer controller,

which triggers the incompatibility due to controller setting mis-

match.

It is recommended to manually reconcile the dierence in settings

to resolve the issue.

During the VRTX power on with no failing conditions, the virtual

drive temporarily transitions to write-through as part of the Shared

PERC 8 rmware initialization. After the system power-on, the

virtual drive transitions back to write back.

There is no intervention required.

During VRTX power on or reset, unresolved pinned cache is

present.

Perform the following:

• Insert the drives that caused the virtual drive to go oine, that

resulted in the cache being pinned to recover the virtual drive.

Troubleshooting 57