HP NetRAID-4M Configuration and Upgrade Guide (Release 5)
59
Chapter 9 Issues and Problem Resolution
Problem: If you run Windows NT 4.0 Setup from the three boot floppies, NT 4.0
fails to detect any logical drives or the container created with the NetRAID-4M
during the text portion of NT 4.0 Setup, even if you load the NetRAID-4M driver.
The root cause is the txtsetup.oem file on the driver's diskette for the NetRAID-4M.
The workaround was to use the Navigator Installation Assistant, or boot from the
Windows NT 4.0 CD and press F6 to load your own drivers, or else modify the
following section of txtsetup.oem on driver disk #1. You must duplicate the first
entry and insert it as the second to last line. Thus, it should look like this:
[Files.Scsi.hpn]
driver = HEIDAC, hpn.sys, hpn
driver = HEIDAC, hpnscsi.sys, hpnscsi
driver = HEIDAC, hpndisk.sys, hpndisk
driver = HEIDAC, hpnport.sys, hpnport
driver = HEIDAC, hpncomm.sys, hpncomm
driver = HEIDAC, hpn.sys, hpn<--- new line (duplicate of
1st)
inf = HEIDAC, oemsetup.inf
Resolution: The textsetup.oem file is fixed in Navigator L.19.00 and beyond.
51 Container creation via FAST is placing container 0 as disk zero under
disk administrator after a reboot
Problem: When creating a container with FAST under NT 4.0, on a reboot,
Container 0 becomes Disk 0 under the Disk Administrator.
Background: When you create a container it is assigned the next available disk
admin number. When rebooting Windows NT 4.0 and the controller is first in the
boot order, the first container on it will get the first disk admin number. Disk
numbers are assigned sequentially across controllers and class drivers. The driver
stack winds up starting before Microsoft's, so if there are containers present they will
be assigned disk numbers before any physical disks that are present on other
controllers that use Microsoft's class driver stack (such as SCSI adapters and AMI
RAID controllers).
NOTE This is not an issue in Windows 2000 since the SCSI miniport
driver uses the Microsoft class driver stack.