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

Chapter 9 Issues and Problem Resolution

In Windows NT 4.0, a non-I/O pull push (removing and re-inserting a drive

immediately), detected by SAF-TE, will create a yellow event in the Windows NT

4.0 system error log. The FAST GUI utility running on a Windows based client for

a remote connection to NetWare will not be in sync, either on the server operating

with NetWare or on a client console.

In NetWare, a non-I/O loss, pull push will not create an event message on the system

console screen. Event messages are typically logged to a text file but this is disabled

by default (note that conlog.nlm is the program and console.log is the text file). An

experienced system administrator will frequently copy and review this file.

Example: This situation occurs during a test when a drive is pulled and then

immediately re-inserted. I/O lag is not likely in actual application. The NetRAID-

4M background consistency check (enabled by default) will eventually detect the

fault.

Workaround: Manually update the FAST GUI with either a rescan or F5 refresh.

60 Novell NetWare 4.2 installation causing red pop-up

Problem: NetWare 4.2 installation may encounter an error message if the

NetRAID-4M is intended to be the boot device, and you are using either NetWare

Automatic Partition Creation or manual installation. This is not an issue with

Navigator Installation Assistant. The error message is:

“No information about device 1 could be obtained. Program execution may not

continue normally. Press Escape to continue.”

The previous release supplement incorrectly stated the problem as “NetWare 4.2

installation may encounter an error message if the NetRAID-4M is intended to be

the boot device, and you are using either NetWare Automatic Partition Creation or

Navigator Installation Assistant. This is not an issue with manual installation.”

Workaround: Press ESC. The installation will complete correctly.

61 Novell NetWare 5.1 NSS free space and file system extension

Problem: Any new containers that are changed in size or deleted are not reflected

in the NSS Update Provider Information option.

Background: NSS is not fully compatible with the traditional NetWare File System.

This forces the SYS volume to be traditional NWFS. Current versions of NetWare

5.0, 5.1, and 5.1 SP1 do not offer updates for dynamically changed NSS

configuration. The NetRAID-4M controller offers a dynamic container creation

process, allowing adding new volumes on the fly. When new containers (disk