HP NetRAID-4M Configuration and Upgrade Guide (Release 5)

Chapter 9 Issues and Problem Resolution

• When the original controller is replaced with another controller. This situation

would occur only if the user were planning to use the same containers and

wishes to keep the data they contain.

• When a new controller is installed in a system with preexisting containers.

• A “controller rescan” command is issued to detect the new devices. The detected

containers are not automatically exposed to the OS. That is, the containers are

not accessible by the OS. It would not be a problem if a user does not care about

the data, because new containers can be created that will contain the controller's

signature. This would not occur when drive roaming is exercised.

Workaround for Linux: If the container is not located at the desired container

number, simply move the container to the desired number. If the container is already

at the desired container number, move the container to a number between 32 and 63,

then move it back to the original location.

Workaround for OpenServer: No workaround required.

Workaround for UnixWare: Two workarounds are available:

1. Move, create, or delete any container or

2. As root, run the command: /sbin/sdiadd -n

31 Uninstallation and reinstallation of MSCS causes uninstallation and

reinstallation of NetRAID-4M cluster software component

Problem: The design of the NetRAID-4M as a cluster adapter is such that you first

install the MSCS in local quorum, then install the NetRAID-4M cluster software

component, and finally, move the resources to the shared quorum. Every time you

uninstall MSCS, you need to uninstall the cluster component. This makes the

installation, uninstallation, and reinstallation a very tedious task.

Workaround: The problem occurs because the NetRAID-4M cluster software

component is a custom Wolfpack DLL and not part of the base Wolfpack. Therefore,

every time Wolfpack uninstalls and reinstalls, the NetRAID-4M cluster software

component needs to be reregistered.

32 AAC entries in the Syslog

Problem: The NetRAID-4M controller is the HP version of the Adaptec AAC

product line. The NetRAID-4M should be abbreviated as HPN/HPNRAID/hpn/

hpnraid in all documentation and entries in all the logs. Some Unix messages refer

to the NetRAID-4M controller as AAC/AACRAID/aac/aacraid controller, not

HPN/HPNRAID/hpn/hpnraid. Windows and NetWare messages are correct.