🚀 go-pugleaf

In newsgroup vmsnet.misc, article <1992Aug10.142728.4397@mic.ucla.edu>,\
 shinn@agsm.ucla.edu (Shinn-Tzong Wu) writes...
> Hi, we just encounteded one of our worst nightmare, the VAXStation 3100
> (running VMS 5.3) died probably because it ran out of disk space for  
> the AUDIT process.  Since the AUDIT process tried to write into the
> full disk in the process of rebooting, there seemed to be no way that we
> can bring the system up.  We tried to boot it from a stand alone tape but
> it won't access to any of the disks.  Can anyone suggest any help?  Thanks...

     Use a conversational boot to bring up a minimum system.  For a 3100,
use B/1 at the `>>>' console prompt.  (If you have a console password
enabled, you'll have to enter it in order to use any variant of the boot
command other than just "B".)  From B/1, you'll get a `SYSBOOT>' prompt
where you can modify SYSGEN parameters; do the following
SYSBOOT> SET STARTUP_P1 "MIN"
SYSBOOT> CONTINUE
from there the system will boot normally, except that under a minimum
system many things are suppressed, including the audit server.  (Also
systartup_v5, the site-specific startup procedure, is suppressed, as are
sylogin and login.com once the system is up.)

     Log in immediately as SYSTEM, use SET LOGIN/INTERACTIVE=1 to keep
ordinary users out, and then purge, delete, or move files to recover
sufficient disk space for normal operation.  Lastly, reset the system
parameters
$ run sys$system:sysgen
SYSGEN> USE CURRENT
SYSGEN> SET STARTUP_P1 ""
SYSGEN> WRITE CURRENT
SYSGEN> EXIT
and then reboot.

     This kind of stuff should be covered in the "emergency procedures"
section of the system manager's manual(s).  Followups redirected to
vmsnet.sysmgt.

		Pat Rankin, rankin@eql.caltech.edu