HP OpenVMS Systems

SYSINIT mount error, PROCGONE bugcheck?

» close window

The Question is:

 
I've got an AlphaStation 200 4/233. It came with a SEAGATE ST32171N disk.
The disk was unreadable.
I used rztools to FORMAT the disk.  Then our standard system disk was copied
to this drive.  It will
boot up OK when VAXCLUSTER=0, and DECnet does
connect me to our network.  However, with
VAXCLUSTER=2 the following sequence occurs:
OpenVMS banner
%DECnet-I-LOADED
waiting to form or join a VMScluster
VMScluster-I
EWA0, 10 base T
CNXMAN, Sending VMScluster
CNXMAN, Now a VMScluster member
%SYSINIT-E- error when mounting system device, retrying..., status =
007280B4
  (the above message repeats 24 times)
%SYSINIT-E-error mounting system device, status = 007280B4
 
****OpenVMS Alpha Opering System V6.2 - BUGCHECK ****
** Code = 0000836C: PROCGONE, process not in system
** Crash CPU:00 Primary CPU:00 Active CPUs:00001
** Current Process: STARTUP
** Image Name =
**** Starting Memory Dump ...
..................................
 
Thanks,
 
Mike
 
 

The Answer is :

 
  First, please realize that the error:
 
    %SYSINIT-E-error mounting system device, status = 007280B4
 
  indicates the following:
 
    $ exit %x07280B4
    %MOUNT-F-VOLALRMNT, another volume of same label already mounted
    $
 
  Please set a system disk label that is unique.
 
  Then -- if resetting the label does not resolve the problem -- please
  replace the Seagate disk with a supported disk, and use that as a
  baseline configuration for testing.  Also use it to make sure that
  the ALPSCSI06_062 (or later) kit has been applied to the target
  system disk.
 
  Please get the value in R0 at the time of the PROCGONE system crash.
  (This value is expected to be a status code related to the failure.)
 
  If the status code does not point to the particular failure, please
  first try a conversational bootstrap.  Set STARTUP_P1 to MIN to select
  a minimal bootstrap.  If that fails, perform another conversational
  bootstrap and set the values of the SYSGEN parameters to the defaults
  via USE DEFAULT.  If this fails, please attempt a direct installation
  of OpenVMS Alpha on the target system disk from an OpenVMS distribution
  kit.
 
  If the above operations fail, please contact the customer support
  center for assistance.  Please expect to be asked how the original
  disk copy was performed, among other questions.
 
 

  

     

     
answer written or last revised on ( 5-NOV-1998 )
     
» close window