Problem upgr 4.11 to 5.1 on Compaq PL3000

[averytech]

I've been doing battle with a Compaq Proliant 3000 (256mB, SmartArray 3200 controller in Raid5 config - 3x9gB drives).&nbsp;&nbsp;Nw 4.11 has been chugging just fine, but during the inplace upgrade to 5.1, I cannot get any Netware volume to mount.&nbsp;&nbsp;I've spent 5 hrs on the phone w/compaq tech support and we all agree it's a driver issue, but we can't seem to resolve it.&nbsp;&nbsp;The server is patched to NW4sp8a and has had the compaq NSSD driver update v5.50 loaded (latest).&nbsp;&nbsp;Again, NW4.11 is very happy with this config (I can revert to the NW4.11 install when the 5.1 install fails).<br>Anyone else encountered this?&nbsp;&nbsp;Any ideas?&nbsp;&nbsp;Your help will be greatly appreciated.<br>Dennis<br>

 

[rjs]

We had a similar problem about a year ago going from 4.11 to 5.0 on a Compaq Proliant server. The server would start and the drives would mount, but if you copied a single small (100-300Kb) file from one directory to another, it caused server utilization to peg at 100% for over a minute and then abend. We worked with Novell and with Compaq, even sent a core dump. No luck.<br><br>We bagged it and went back to 4.11 - no problem since. We have a number of other installations with 5.0 and 5.1 that are ok. But none of those were in-place upgrades.

 

[averytech]

Thanks.&nbsp;&nbsp;When I try to manually mount the volumes (outside of the install program) using the &quot;mount sys&quot; command I get an immediate &quot;no accessible disk drives with Netware partitions were found - check drives, drivers, etc.&quot; message.&nbsp;&nbsp;I can restore an image of my original C:\NWSERVER directory (when they say &quot;back up everything, including the DOS partition&quot;, they mean it!) and the NW4.11 system will start normally and run just fine.&nbsp;&nbsp;After spending hours on the phone with Compaq and our area Novell tech support, we all agree the problem is a driver mismatch, but it seems NW5.1 is forcing us to use the drivers.&nbsp;&nbsp;It creates a C:\NWINST.TMP directory and pulls the drivers from that (and from a DRIVERS subdir in C:\NWSERVER).&nbsp;&nbsp;This happens during the install initialization and once that happens, you can't get back to the DOS partition to change anything.&nbsp;&nbsp;Supposedly, you can populate the C:\NWUPDATE directory with &quot;correct&quot; drivers and the install will pull from here instead of the default locations.&nbsp;&nbsp;This doesn't seem to work as advertised.<br><br>I'm happy with 4.11, but I've got to move 10 servers to 5.1, and quickly.&nbsp;&nbsp;I'll keep plowing along.&nbsp;&nbsp;Thanks again.<br>Dennis

 

[averytech]

Problem resolved!<br>The problem of not being able to mount the netware volumes during the upgrade process was caused by the Veritas Backup Exec v8.5 Open File Option component that was installed on the server.&nbsp;&nbsp;The OFO creates a &quot;disk device filter&quot; that serves as an intermediary between the backup prgm and the netware volume in order to allow for backing up files that are opened.&nbsp;&nbsp;Unfortunately, it also sat between the Netware 5.1 upgrade process and the existing volumes.&nbsp;&nbsp;I uninstalled the OFO using the SINSTALL.NLM utility provided by the BE installation.&nbsp;&nbsp;Restarted the server and let it settle for awhile.&nbsp;&nbsp;Restarted and entered the upgrade process.&nbsp;&nbsp;It completed without a hitch.