| Title: | VAX and Alpha VMS |
| Notice: | This is a new VMSnotes, please read note 2.1 |
| Moderator: | VAXAXP::BERNARDO |
| Created: | Wed Jan 22 1997 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 703 |
| Total number of notes: | 3722 |
Hi,
My customer has a SCSI/FDDI cluster with one ASRV 2100 and one ASRV
8400. They boot from the same disk ($2$DKC204:) one from root SYS0 and the
other from root SYS1. He is getting problem when tryes to boot from
SYS0 and is getting the message:
Halt Code = 5
HWRPB is invalid
PC=162c4
Both Cpus show the problem when using SYS0 and works fine when use
SYS1.
We used the flag 20000 and checked out that error happens exactly
after:
%SYSBOOT-I-WLCM, Welcome to Alpha secondary bootstrap
%SYSBOOT-I-LOADPARAM, Loading parameter file ALPHAVMSSYS.PAR
%SYSBOOT-I-LOADFILE, Loading [SYS0.SYSCOMMON.SYSEXE]ALPHAVMSSYS.PAR;1
%SYSBOOT-I-SYSPGTBL, Creating the system pagetables
%SYSBOOT-I-ALLOCPGS, Allocating loader huge pages
%SYSBOOT-I-LOADIMGS, Loading the base system images
%SYSBOOT-I-LOADFILE, Loading [SYS0.SYSCOMMON.SYSLIB]SYS$PUBLICVECTORS.EXE;1
%SYSBOOT-I-LOADFILE, Loading[SYS0.SYSCOMMON.SYS$LDR]SYS$BASEIMAGE.EXE;2
%SYSBOOT-I-INITDATA, Initialize MMG/Loader/Misc. system data cells
Here happens the error message....
It was supose to come :
%SYSBOOT-I-REMAP, Remap HWRPB/SWRPB
Is there any suggestion to fix this situation without a backup image
from the system disk?
Any help will be very welcome. Mauro.
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 477.1 | Possible Disk Corruption? | XDELTA::HOFFMAN | Steve, OpenVMS Engineering | Tue Apr 15 1997 16:28 | 25 |
It would appear there is a corruption or "unusual" setting in the [SYS0] root. I would hope these systems are running V6.2-1H3, or V7.1. Also check the PALcode version(s) in use, making sure these are compatible with the OpenVMS release in use. I would hope both systems are not booted from the same root. (Booting multiple nodes from the same disk root has been seen to cause severe disk corruptions, when this occured in similar SCSI configurations.) I would tend to remove the [SYS0] root, and then re-add it (via whichever variant of CLUSTER_CONFIG is in use locally), and see if this affects the problem. I would also check for the validity of current image BACKUPs, in the event there is a disk corruption here. If you wish to make a formal report via IPMT, we'll need an image copy of the contents of the disk, and some information around the specific disk and controller configuration, as well as the boot environment variable settings. This question would be better suited to SPEZKO::CLUSTER. | |||||
| 477.2 | The solution and doubts... | VAXRIO::MAURO | Tue Apr 15 1997 17:08 | 20 | |
We found out the reason why the root SYS0 became unbootable. Using the
boot flag 10000, we were able to see that boot hangs when it displays
"Create balance set slots". At this time the customer remembered that
executed a Autogen (until setparams) today in the morning. He changed, I
don't known why, the following parameters:
MIN_BALSETCNT = 803
MAXPROCESSCNT = 952
MIN_WSMAX = 800000
After the Autogen he checked the SETPARAMS.DAT and found:
BALSETCNT = 810
MAXPROCESSCNT = 892
WSMAX = 1000048
With these values the system becomes unbootable. The most interesting:
the parameters values in the SETPARAMS.DAT were configured by AUTOGEN,
superseeding the values from MODPARAMS.DAT. I'm waiting the system reboot
to check if there is any WARNING in AGEN$PARAMS.REPORT, about those values.
| |||||