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

Chapter 9 Issues and Problem Resolution

• NetRAID-4M installed

• NetWare 4.2 or 5.1

• SymBIOS agent is loaded (symsnmp.nlm - Ver1.01d - 7/1/99) or if the

SymBIOS SCSI-status agent is loaded (symtrap.nlm)

• NetRAID-4M FAST utility is started on a remote client

Workaround 1: Delete the Agents.

Either rename or remove the file “sys:system\symsnmp.nlm” and

“sys:system\symtrap.nlm” so it will not load the next time. Then reboot the LP

2000r. Start the FAST utility from the NT client and manage the LP 2000r.

Workaround 2: Use a RAID Configuration Tool other than FAST.

Instead of configuring your NetWare server from a Windows client running FAST,

use either the Container Configuration Utility or the Command Line Interface.

64 UnixWare unable to access files under very heavy load

Problem: Under extremely heavy load, the controller firmware sometimes does not

reserve enough resources prior to starting an I/O transaction. If the problem occurs,

there will be no further I/O until the server is rebooted. There is no known data

corruption, only an issue of data availability. This problem has only been seen in a

UnixWare test environment.

Workaround: One of the following workarounds will prevent the problem.

• Shut down and restart the server.

• Do not mix RAID types. For example, use either all RAID-1 configurations or

all RAID-5 configurations, but not both at the same time on the same controller.

• Disable write caching on each data container.

Resolution: Fixed in Release 3.

65 UnixWare no longer boots reliably on machines with four CPUs

Problem: Servers with four CPUs sometimes will not boot from the NetRAID-4M.

HP has confirmed this boot failure on LH4 using both 550 and 700 MHz, and

recently on an LH 6000 with four CPUs.

Impact to Customer: Server cannot be booted from between 10-100% of the time.