axpbox
axpbox copied to clipboard
lenticularis39
OpenVMS 8.4-2 Installation (Ubuntu 22.04, 22.10) Problems
Problem 1:
Several -RMS-E-CRE, ACP file create failed -SYSTEM-F-CTRLERR, fatal controller error at various different points of installations. Work-around:
after placing disk image of tmpfs these errors did not occur anymore. Additionally I am using SCSI instead of IDE now.
Problem 2:
...80% %PCSI-I-PRCOUTPUT, output from subprocess follows ... %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=000000000026 C104, PC=000000007FDC5324, PS=0000001B %PCSI-E-MODREPLERR, error replacing module ADARTL in library DISK$ALPHASYS:[VMS$ COMMON.][SYSLIB]IMAGELIB.OLB -SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual address=!XH, PC=!XH , PS=!XL %PCSI-E-OPFAILED, operation failed Terminating is strongly recommended. Do you want to terminate? [YES] n
...
%PCSIUI-I-COMPWERR, operation completed after explicit continuation from errors
**************************************************************
* *
* W A R N I N G *
* *
* One or more errors were encountered during installation/ *
* upgrade. The target system may not operate correctly. *
* *
* You should correct the condition that caused the error(s) *
* and repeat the installation/upgrade. *
* *
**************************************************************
The installation is now complete.
When the newly installed system is first booted, a special startup procedure will be run. This procedure will:
o Configure the system for standalone or OpenVMS Cluster operation.
o Run AUTOGEN to set system parameters.
o Reboot the system with the newly set parameters.
You may shut down now or continue with other operations.
Process AXPVMS_INSTALL logged out at 12-NOV-2022 22:01:11.74
I ran into similar issues, running on Mac OS 12.6 (M1). Both the latest code and the 1.1 release; the latter not optimized because of a build script issue that I see was fixed later. I also tried using the SCSI controller instead of the default IDE. The actual failures vary; the most consistent one I see is a failure to create HELPLIB.
Regarding the HELPLIB error, please see this Google groups comment:
Alpha V8.4-2L1 was designed for upgrade only, not a fresh install.
V8.4-2L2 (which is Alpha-only) can be used for a fresh install.
Having said that, reports are that you can continue past those error messages and have a working system.
It turns out that the helplib error is not a real issue. If I bypass that I get one more, on dcltables.exe. But then the install finishes and it seems to be successful. (This is with a SCSI disk, not IDE.) So it seems the claim that L1 is upgrade-only is not correct, and indeed the documentation clearly states that both L1 and L2 are full kits. The difference is that L2 is built with EV6 instructions while L1 is built for older Alphas.
So it looks good. Now on to configuring some stuff like DECnet phase V...
We've merged a pull request yesterday (#100 ) that should resolve the errors during installation. Could you please check if it has fixed anything for you?
