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

43
Chapter 9 Issues and Problem Resolution
Resolution: By disabling the cache after the first drive failure, a second drive failure
will no longer hang the system.
14 1 TB expansion
Problem: A container expansion to 1 TB can cause a controller panic.
Impact to customer: Serious. The user will be unable to expand the current
container without having to rebuild the container and restoring the data from a
current backup.
Resolution: Modifications to the morphing code of the firmware will now allow the
container to expand beyond 1TB.
15 More than 2 GB of RAM with NetWare 6
Problem: The NetRAID-4M card utilized a DEC PCI bridge chip in conjunction
with the Intel Strong ARM Processor. This combination has a limitation when used
in machines trying to load or run with NetWare 6 with >2 GB of RAM installed. As
soon as information traverses the DEC PCI bridge chip to the 4M driver,
unpredictable results or server crashes can be expected.
Impact to customer: Serious. A customer will be unable to upgrade to NetWare 6
if the system has >2 GB of RAM.
Resolution: Additional code was added to the comm memory allowing access to
comm memory above 2GB.
16 Cannot add 9 GB hot spare
Problem: When a container is created using the maximum capacity of the physical
drives, neither the Container Configuration Utility (CCU) nor Flexible Array
Storage Tool (FAST) can assign the same capacity physical drives as a hot spare
(failover drive).
Background: The error given by CCU and FAST utility is “There are no drives
present which can be assigned as failover drives to this container and there are no
drives previously assigned as failover drives. 8.4GB is the required failover space
for this container.”
Resolution: The workaround was to reduce container size by 1/1000 of a gigabyte
(8.473 GB vs. 8.474 GB) of the maximum default amount. Fixed in Release 3.
17 SMART MRIE Level 2