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

Chapter 9 Issues and Problem Resolution

Problem: The test case involves running both a “proprietary test” and “winthrax”

to separate containers. After running in the time frame of 30min to several hours, the

“proprietary test” detects incorrect data. An analysis of the data shows that the

preceding 1 k write to the given chunk wrote the first 512 B correctly but the second

512 B was not written at all; that is, the second half of the 1 KB chunk had data that

was written from the 2nd preceding write.

Impact to customer: Rare but serious. Can cause undetectable loss of data.

Resolution: Multiple non-interlocked DMA transfers to the same subsection of a

cache block caused the data corruption problem. The fix was to use the already-

existing locking mechanism for the two cases where no locking had previously been

done. Fix is in Firmware and has been tested.

5 FAST identify does not turn off the blinking drive location LED

Problem: FAST identify does not turn off the blinking drive location LED on

LP2000r internal enclosure.

Impact to customer: Low. FAST identify is a rarely used maintenace command

used to flash the LED on a drive slot. This error results in a blinking red LED that

will not shut off.

Resolution: Set the bit to “ready” in the SAFTE slots identify on/off.

6 4M option ROM does not call Post Memory Manager when CTRL + A is

invoked

Problem: The Adaptec 4M option ROM card does not call the PMM when the

CTRL+A is invoked. It is supposed to call the PMM to allocate a temporary buffer

in main memory in order to load its configuration display when the CTRL+A is

invoked.

Impact to customer: Low. Does not affect current HP Servers; this issue was

detected on testing for a future product. However, resolution was tested on current

HP Servers prouct line as well as future HP Servers.

Resolution: There was a stack error in the forced memory allocation path. A

modification in the BIOS code resolved this issue.

7 DOS driver cannot handle inquiry command when the specified Host

Adapter number does not exist

Problem: The DOS driver for 4M cannot handle inquire command when the

specified Host Adapter number does not exist.