topic Re: VMS server boots but nothing is loaded. in Operating System - OpenVMS

VMS server boots but nothing is loaded.

Joewee — Wed, 27 May 2009 14:20:28 GMT

Hi All,

Im booting a vms server through a laptop connected to its serial port. I have attached the boot log with this. Nothing is getting loaded and I believe the system disk is corrupted. I need more clear picture of this. Kindly help.

NNNNNN$ @sys$system:shutdown

SHUTDOWN -- Perform an Orderly System Shutdown
on node NNNNNN

How many minutes until final shutdown [0]:
Reason for shutdown [Standalone]:
Do you want to spin down the disk volumes [NO]?
Do you want to invoke the site-specific shutdown procedure [YES]?
Should an automatic system reboot be performed [NO]?
When will the system be rebooted [later]:
Shutdown options (enter as a comma-separated list):
REBOOT_CHECK Check existence of basic system files
SAVE_FEEDBACK Save AUTOGEN feedback information from this boot
DISABLE_AUTOSTART Disable autostart queues

Shutdown options [NONE]:

%SHUTDOWN-I-OPERATOR, this terminal is now an operator's console
%SHUTDOWN-I-DISLOGINS, interactive logins will now be disabled
%%%%%%%%%%% OPCOM 27-MAY-2009 14:00:58.08 %%%%%%%%%%%
Operator status for operator _NNNNNN$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%SET-I-INTSET, login interactive limit = 0, current interactive value = 1
%SHUTDOWN-I-STOPQUEUES, the queues on this node will now be stopped

SHUTDOWN message on NNNNNN from user SYSTEM at _NNNNNN$OPA0: 14:00:58
NNNNNN will shut down in 0 minutes; back up later. Please log off node NNNNNN.
Standalone

1 terminal has been notified on NNNNNN.
%SHUTDOWN-I-SITESHUT, the site-specific shutdown procedure will now be invoked
DFG$NNNNNN not stopped
%SYSTEM-W-NONEXPR, nonexistent process
Disk File Optimizer for OpenVMS has been shut down on NNNNNN
%DCL-E-OPENIN, error opening MQS_ROOT:[MQM.IDM]SHUTDOWN_IDM.COM; as input
-RMS-F-DEV, error in device name or inappropriate device type for operation
%SHUTDOWN-I-STOPUSER, all user processes will now be stopped
%SHUTDOWN-I-STOPAUDIT, the security auditing subsystem will now be shut down
%%%%%%%%%%% OPCOM 27-MAY-2009 14:01:00.46 %%%%%%%%%%%
Message from user AUDIT$SERVER on NNNNNN
Security alarm (SECURITY) and security audit (SECURITY) on NNNNNN, system id: 24
57
Auditable event: Audit server shutting down
Event time: 27-MAY-2009 14:01:00.46
PID: 0000020E
Username: SYSTEM

%SHUTDOWN-I-REMOVE, all installed images will now be removed
%SHUTDOWN-I-DISMOUNT, all volumes will now be dismounted
$1$DRA1: (NNNNNN)

$1$DRA2: (NNNNNN)

%%%%%%%%%%% OPCOM 27-MAY-2009 14:01:02.09 %%%%%%%%%%%
$1$DRA1: (NNNNNN) has been removed from shadow set.

$1$DRA3: (NNNNNN)

$1$DRA4: (NNNNNN)

%%%%%%%%%%% OPCOM 27-MAY-2009 14:01:02.09 %%%%%%%%%%%
$1$DRA2: (NNNNNN) has been removed from shadow set.

%%%%%%%%%%% OPCOM 27-MAY-2009 14:01:02.20 %%%%%%%%%%%
$1$DRA3: (NNNNNN) has been removed from shadow set.

%%%%%%%%%%% OPCOM 27-MAY-2009 14:01:02.20 %%%%%%%%%%%
$1$DRA4: (NNNNNN) has been removed from shadow set.

%%%%%%%%%%% OPCOM 27-MAY-2009 14:01:03.54 %%%%%%%%%%%
Message from user SYSTEM on NNNNNN
_NNNNNN$OPA0:, NNNNNN shutdown was requested by the operator.

%%%%%%%%%%% OPCOM 27-MAY-2009 14:01:03.55 %%%%%%%%%%%
Logfile was closed by operator _NNNNNN$OPA0:
Logfile was NNNNNN::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;4048

%%%%%%%%%%% OPCOM 27-MAY-2009 14:01:03.59 %%%%%%%%%%%
Operator _NNNNNN$OPA0: has been disabled, username SYSTEM

SYSTEM SHUTDOWN COMPLETE

halted CPU 0

halt code = 5
HALT instruction executed
PC = ffffffff80077f00
resetting all I/O buses
P00>>>
P00>>>sho dev
dka600.6.0.1.0 DKA600 RRD45 0436
dra0.0.0.7.0 DRA0 2 Member RAID 1
dra1.0.0.7.0 DRA1 1 Member JBOD
dra2.0.0.7.0 DRA2 1 Member JBOD
dra3.0.0.7.0 DRA3 1 Member JBOD
dra4.0.0.7.0 DRA4 1 Member JBOD
dra5.0.0.7.0 DRA5 1 Member JBOD
drb0.0.0.8.0 DRB0 2 Member RAID 0
drb1.0.0.8.0 DRB1 1 Member JBOD
drb2.0.0.8.0 DRB2 1 Member JBOD
drb3.0.0.8.0 DRB3 1 Member JBOD
drb4.0.0.8.0 DRB4 1 Member JBOD
drb5.0.0.8.0 DRB5 1 Member JBOD
drb6.0.0.8.0 DRB6 2 Member RAID 0
drb7.0.0.8.0 DRB7 2 Member RAID 0
dva0.0.0.1000.0 DVA0 RX26/RX23
mka500.5.0.1.0 MKA500 TZ89 296D
ewa0.0.0.6.0 EWA0 00-00-F8-22-C9-FA
pka0.7.0.1.0 PKA0 SCSI Bus ID 7
P00>>>sho boot
Use bootdef_dev instead.
P00>>>sho boot*
boot_dev dra0.0.0.7.0
boot_file
boot_osflags 0,0
boot_reset OFF
bootdef_dev dra0.0.0.7.0
booted_dev dra0.0.0.7.0
booted_file
booted_osflags 0,0
P00>>>boot
(boot dra0.0.0.7.0 -flags 0,0)
block 0 of dra0.0.0.7.0 is a valid boot block
reading 912 blocks from dra0.0.0.7.0
bootstrap code read in
base = 200000, image_start = 0, image_bytes = 72000
initializing HWRPB at 2000
initializing page table at 17ff0000
initializing machine state
setting affinity to the primary CPU
jumping to bootstrap code

OpenVMS (TM) Alpha Operating System, Version V7.1-1H2

%DRA, firmware version V2.36
%DRA, drives = 6, optimal = 6, degraded = 0, failed = 0
%DRA, drive 0, 4110336 LBNs, optimal, 2 Member RAID 1
%DRA, drive 1, 8378368 LBNs, optimal, 1 Member JBOD
%DRA, drive 2, 8378368 LBNs, optimal, 1 Member JBOD
%DRA, drive 3, 8378368 LBNs, optimal, 1 Member JBOD
%DRA, drive 4, 8378368 LBNs, optimal, 1 Member JBOD
%DRA, drive 5, 4110336 LBNs, optimal, 1 Member JBOD
$! Copyright (c) 1996 Digital Equipment Corporation. All rights reserved.
%STDRV-I-STARTUP, OpenVMS startup begun at 27-MAY-2009 14:04:38.32
%DCL-W-ACTIMAGE, error activating image SYSGEN
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]SYSGEN.EXE;1
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%INSTALL-E-FAIL, failed to CREATE entry for DISK$ALPHASYS:>SYSGEN.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%NONAME-F-NOMSG, Message number 00000154
%NONAME-F-NOMSG, Message number 00000154
%DCL-W-NOMSG, Message number 00038120
%SET-I-NEWAUDSRV, identification of new audit server process is 00000206
%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:48.85 %%%%%%%%%%%
Operator _NNNNNN$OPA0: has been enabled, username SYSTEM

%DCL-W-ACTIMAGE, error activating image LMF
%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:48.96 %%%%%%%%%%%
Operator status for operator _NNNNNN$OPA0:
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LMF.EXE;1
-SYSTEM-F-PROTINSTALL, protected images must be installed
%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:49.58 %%%%%%%%%%%
Logfile has been initialized by operator _NNNNNN$OPA0:
Logfile is NNNNNN::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;4049

%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:49.59 %%%%%%%%%%%
Operator status for operator NNNNNN::SYS$SYSROOT:[SYSMGR]OPERATOR.LOG;4049
CENTRAL, PRINTER, TAPES, DISKS, DEVICES, CARDS, NETWORK, CLUSTER, SECURITY,
LICENSE, OPER1, OPER2, OPER3, OPER4, OPER5, OPER6, OPER7, OPER8, OPER9, OPER10,
OPER11, OPER12

%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:50.13 %%%%%%%%%%%
Message from user SYSTEM on NNNNNN
%SHADOW_SERVER-I-SSRVINICMP, shadow server has completed initialization

%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:50.64 %%%%%%%%%%%
Message from user SYSTEM on NNNNNN
%LICENSE-E-NOAUTH, DEC OPENVMS-ALPHA use is not authorized on this node
-LICENSE-F-NOT_STARTED, License Management Facility is not started
-LICENSE-I-SYSMGR, please see your system manager

%LICENSE-E-NOAUTH, DEC OPENVMS-ALPHA use is not authorized on this node
-LICENSE-F-NOT_STARTED, License Management Facility is not started
-LICENSE-I-SYSMGR, please see your system manager
%LICENSE-F-NOT_STARTED, License Management Facility is not started
%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:51.26 %%%%%%%%%%%
Message from user SYSTEM on NNNNNN
%SECSRV-I-PROXYSTARTINGUP, proxy processing now starting up

%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:51.28 %%%%%%%%%%%
Message from user SYSTEM on NNNNNN
%SECSRV-I-SERVERSTARTINGU, security server starting up

%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:51.38 %%%%%%%%%%%
Message from user SYSTEM on NNNNNN
%SECSRV-I-CIASTARTINGUP, breakin detection and evasion processing now starting u
p

========================27-MAY-2009 14:04:52.12========================

OpenVMS system is now executing the site-specific startup commands.

=======================================================================
%%%%%%%%%%% OPCOM 27-MAY-2009 14:04:52.28 %%%%%%%%%%%
Message from user AUDIT$SERVER on NNNNNN
Security alarm (SECURITY) and security audit (SECURITY) on NNNNNN, system id: 24
57
Auditable event: Audit server starting up
Event time: 27-MAY-2009 14:04:52.06
PID: 00000203
Username: SYSTEM

-----------------------------------------------------------------------
Mounting disks

%MOUNT-I-MOUNTED, APP mounted on _DSA0:
%MOUNT-I-SHDWMEMSUCC, _$1$DRA1: (NNNNNN) is now a valid member of the shadow set
%MOUNT-I-SHDWMEMSUCC, _$1$DRA2: (NNNNNN) is now a valid member of the shadow set
%MOUNT-I-MOUNTED, USER mounted on _DSA1:
%MOUNT-I-SHDWMEMSUCC, _$1$DRA3: (NNNNNN) is now a valid member of the shadow set
%MOUNT-I-SHDWMEMSUCC, _$1$DRA4: (NNNNNN) is now a valid member of the shadow set
%MOUNT-F-NOMASTER, no master member found for this virtual unit
%MOUNT-I-SHDWMEMFAIL, _$1$DRB6: failed as a member of the shadow set
-SYSTEM-W-NOSUCHDEV, no such device available
%MOUNT-I-SHDWMEMFAIL, _$1$DRB7: failed as a member of the shadow set
-SYSTEM-W-NOSUCHDEV, no such device available
%JBC-E-JOBQUEDIS, system job queue manager is not running
-----------------------------------------------------------------------
Registering all network services

-----------------------------------------------------------------------
Start LAT

%NONAME-F-NOMSG, Message number 00000154
%DCL-W-NOMSG, Message number 00038120
%JBC-E-JOBQUEDIS, system job queue manager is not running
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-W-NOTSET, error modifying LTA9999
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-E-NOTSET, error modifying LTA9999:
-SYSTEM-W-NOSUCHDEV, no such device available
%JBC-E-JOBQUEDIS, system job queue manager is not running
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9998:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9998:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-W-NOTSET, error modifying LTA9997
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-E-NOTSET, error modifying LTA9997:
-SYSTEM-W-NOSUCHDEV, no such device available
%JBC-E-JOBQUEDIS, system job queue manager is not running
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9982:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9982:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9981:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9981:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9980:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9980:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9979:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9979:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9978:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9978:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9977:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9977:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9976:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9976:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9975:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9975:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9984:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9984:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-W-NOTSET, error modifying LTA9993:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-E-NOTSET, error modifying LTA9993:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9993:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9992:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9992:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9988:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9988:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-W-NOTSET, error modifying LTA9983
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-E-NOTSET, error modifying LTA9983:
-SYSTEM-W-NOSUCHDEV, no such device available
%JBC-E-JOBQUEDIS, system job queue manager is not running
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9995:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9995:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-W-NOTSET, error modifying LTA9990
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-E-NOTSET, error modifying LTA9990:
-SYSTEM-W-NOSUCHDEV, no such device available
%JBC-E-JOBQUEDIS, system job queue manager is not running
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-W-NOTSET, error modifying LTA9989
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-E-NOTSET, error modifying LTA9989:
-SYSTEM-W-NOSUCHDEV, no such device available
%JBC-E-JOBQUEDIS, system job queue manager is not running
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-E-NOTSET, error modifying LTA9986:
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-W-NOTSET, error modifying LTA9986:
-SYSTEM-W-NOSUCHDEV, no such device available
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%DCL-W-ACTIMAGE, error activating image LATCP
-CLI-E-IMGNAME, image file $1$DRA0:[SYS0.SYSCOMMON.][SYSEXE]LATCP.EXE
-IMGACT-F-IMG_SIZ, image header descriptor length is invalid
%SET-W-NOTSET, error modifying LTA9985
-SYSTEM-W-NOSUCHDEV, no such device available
%SET-E-NOTSET, error modifying LTA9985:
-SYSTEM-W-NOSUCHDEV, no such device available
%JBC-E-JOBQUEDIS, system job queue manager is not running

This product requires a license for Digital TCP/IP Services
for OpenVMS. Please refer to the OpenVMS License Management
Utility Manual for more information.

%NONAME-F-NOMSG, Message number 00000154
-----------------------------------------------------------------------
Starting HITMAN software

%HITMAN-S-PRCSSTRT, Starting HITMAN, please wait ...
%%%%%%%%%%% OPCOM 27-MAY-2009 14:05:15.65 %%%%%%%%%%%
Message from user SYSTEM on NNNNNN
HITMAN - A new log file has been created

%HITMAN-S-PROCID, Identification of created process is 0000020A
-----------------------------------------------------------------------
Starting DFO software

%SUBMIT-F-CREJOB, error creating job
-JBC-E-JOBQUEDIS, system job queue manager is not running
-----------------------------------------------------------------------
Starting CALS software

%SUBMIT-F-CREJOB, error creating job
-JBC-E-JOBQUEDIS, system job queue manager is not running
-----------------------------------------------------------------------
Starting RS1INS software

%SUBMIT-F-CREJOB, error creating job
-JBC-E-JOBQUEDIS, system job queue manager is not running
-----------------------------------------------------------------------
Starting the PMO interface

%SUBMIT-F-CREJOB, error creating job
-JBC-E-JOBQUEDIS, system job queue manager is not running
-----------------------------------------------------------------------
Starting MQ Series software

%SUBMIT-F-CREJOB, error creating job
-JBC-E-JOBQUEDIS, system job queue manager is not running
-----------------------------------------------------------------------
Starting SWXCR monitor processes for DRA and DRB devices

%MAIL-E-ERRACTRNS, error activating transport SMTP
%LIB-E-ACTIMAGE, error activating image $1$DRA0:[SYS0.SYSCOMMON.][SYSLIB]SMTP_MA
ILSHR.EXE;
-RMS-E-FNF, file not found
%SYSTEM-F-ABORT, abort
%SYSTEM-W-NOSUCHDEV, no such device available
%SYSTEM-F-ABORT, abort
%SET-I-INTSET, login interactive limit = 64, current interactive value = 0
%DECW$DEVICE-I-NODEVICE, no graphics devices found.
%NONAME-F-NOMSG, Message number 00000154
%DCL-W-NOMSG, Message number 00038120
SYSTEM job terminated at 27-MAY-2009 14:05:27.98

Accounting information:
Buffered I/O count: 3081 Peak working set size: 4704
Direct I/O count: 1256 Peak virtual size: 174832
Page faults: 4088 Mounted volumes: 2
Charged CPU time: 0 00:00:05.16 Elapsed time: 0 00:00:50.54

Re: VMS server boots but nothing is loaded.

Volker Halle — Wed, 27 May 2009 14:47:01 GMT

Joewee,

if providing large .TXT files, please consider to attach them as a .TXT attachment in the future.

SYSGEN.EXE or maybe some image activated by the image activator when starting SYSGEN.EXE seems to have a corrupted file header. Consider to run ANAL/IMA on SYSGEN.EXE and all dependant images.

Consider to run ANAL/DISK on the system disk.

Provide the output of the above actions as an attached .TXT file for further examination.

Volker.

Re: VMS server boots but nothing is loaded.

Robert Gezelter — Wed, 27 May 2009 15:05:46 GMT

Joewee,

Indeed. As Volker has commented, SYSGEN.EXE would appear to be corrupted, as are several other files.

At a minimum, I would view that system disk with extreme suspicion, where multiple files have been corrupted, there are likely others.

If there is important data on that drive, I would immediately stop using it until it has been imaged physically, so that recovery can be attempted.

- Bob Gezelter, http://www.rlgsc.com

Re: VMS server boots but nothing is loaded.

Joewee — Wed, 27 May 2009 15:37:14 GMT

Thanks for your replies and very sorry for pasting such a long text file there...

I tried Ana/disk some time ago.. Please find the file attached.

Re: VMS server boots but nothing is loaded.

Jeremy Begg — Thu, 28 May 2009 05:54:49 GMT

Your system disk cannot be trusted. Errors like this in your ANAL/DISK ...

%ANALDISK-W-BADDIR, directory [SYS0.SYSCOMMON.DECW$DEFAULTS.USER] has invalid fo
rmat
-ANALDISK-I-BAD_DIRSIZE, directory record has invalid size
-ANALDISK-I-BAD_DIRTYPE, invalid type code in directory record

... imply that something has randomly corrupted various file headers.

The only fix is to restore from backup.

Regards,
Jeremy Begg

Re: VMS server boots but nothing is loaded.

Joewee — Thu, 28 May 2009 07:05:56 GMT

Even Im planning the same. But the Last available backup was taken only 6 months ago. But there were no activity after that since this server is not used for day today activities.. They have some important data on the other disk and an application which they use very rarely.

One quick question... will we be able to get this fixed if we take a image backup of this disk and restore it back??

And one more problem...

In SRM prompt when i find..

P00>>>sho dev
dka600.6.0.1.0 DKA600 RRD45 0436
dra0.0.0.7.0 DRA0 2 Member RAID 1
dra1.0.0.7.0 DRA1 1 Member JBOD
dra2.0.0.7.0 DRA2 1 Member JBOD
dra3.0.0.7.0 DRA3 1 Member JBOD
dra4.0.0.7.0 DRA4 1 Member JBOD
dra5.0.0.7.0 DRA5 1 Member JBOD
drb0.0.0.8.0 DRB0 2 Member RAID 0
drb1.0.0.8.0 DRB1 1 Member JBOD
drb2.0.0.8.0 DRB2 1 Member JBOD
drb3.0.0.8.0 DRB3 1 Member JBOD
drb4.0.0.8.0 DRB4 1 Member JBOD
drb5.0.0.8.0 DRB5 1 Member JBOD
drb6.0.0.8.0 DRB6 2 Member RAID 0
drb7.0.0.8.0 DRB7 2 Member RAID 0
dva0.0.0.1000.0 DVA0 RX26/RX23
mka500.5.0.1.0 MKA500 TZ89 296D
ewa0.0.0.6.0 EWA0 00-00-F8-22-C9-FA
pka0.7.0.1.0 PKA0 SCSI Bus ID 7

Where as once the system is booted I find only this

MSUK04$ sho dev

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA0: Mounted 0 APP 2392713 1 1
DSA1: Mounted 0 USER 3759975 1 1
DSA2: Online 0
$1$DRA0: (MSUK04) Mounted 0 ALPHASYS 272619 180 1
$1$DRA1: (MSUK04) ShadowSetMember 0 (member of DSA0:)
$1$DRA2: (MSUK04) ShadowSetMember 0 (member of DSA0:)
$1$DRA3: (MSUK04) ShadowSetMember 0 (member of DSA1:)
$1$DRA4: (MSUK04) ShadowSetMember 0 (member of DSA1:)
$1$DRA5: (MSUK04) Online 0

Device Device Error
Name Status Count
OPA0: Online 0

Tape drive is missing, CD drive is missing and few disks are missing. What could be the reason??

Re: VMS server boots but nothing is loaded.

marsh_1 — Thu, 28 May 2009 12:35:02 GMT

hi,

it would be well worth opening up the box and checking for dust levels , also reseat all connections. do a show config at the srm prompt and post the output.

hth

Re: VMS server boots but nothing is loaded.

Joewee — Thu, 28 May 2009 14:37:21 GMT

Here is the output...

P00>>>show config
Digital Equipment Corporation
AlphaServer 2000 4/275

SRM Console V5.3-2 VMS PALcode V5.56-7, OSF PALcode V1.45-12

Component Status Module ID
CPU 0 P B2024-AA DECchip (tm) 21064A-2
Memory 0 P B2023-BA 256 MB
Memory 1 P B2023-BA 128 MB
I/O B2111-AA
dva0.0.0.1000.0 RX26/RX23

Slot Option Hose 0, Bus 0, PCI
1 NCR 53C810 pka0.7.0.1.0 SCSI Bus ID 7
dka600.6.0.1.0 RRD45
mka500.5.0.1.0 TZ89
2 Intel 82375 Bridge to Bus 1, EISA
6 DECchip 21040-AA ewa0.0.0.6.0 00-00-F8-22-C9-FA
7 Mylex DAC960 dra.0.0.7.0
dra0.0.0.7.0 2 Member RAID 1
dra1.0.0.7.0 1 Member JBOD
dra2.0.0.7.0 1 Member JBOD
dra3.0.0.7.0 1 Member JBOD
dra4.0.0.7.0 1 Member JBOD
dra5.0.0.7.0 1 Member JBOD
8 Mylex DAC960 drb.0.0.8.0
drb0.0.0.8.0 2 Member RAID 0
drb1.0.0.8.0 1 Member JBOD
drb2.0.0.8.0 1 Member JBOD
drb3.0.0.8.0 1 Member JBOD
drb4.0.0.8.0 1 Member JBOD
drb5.0.0.8.0 1 Member JBOD
drb6.0.0.8.0 2 Member RAID 0
drb7.0.0.8.0 2 Member RAID 0

Slot Option Hose 0, Bus 1, EISA
4 ISA

Re: VMS server boots but nothing is loaded.

Jeremy Begg — Fri, 29 May 2009 05:35:00 GMT

With a system disk as broken as yours is, no VMS behaviour will be reliable. SHOW DEVICES relies on the magic incantation

$ mcr sysman io autoconfigure

being run during boot, and given the problems you've got it wouldn't surprise me if the above command didn't run or didn't work.

Backing up this disk and restoring it may correct some problems but probably not all.

I strongly recommend you boot from the OpenVMS binary distrbution CD-ROM, and use BACKUP to back up all your disks. Then restore a known good backup of your system disk (e.g. from 6 months ago, if that's what you have). If your application files are all on non-system disks you shouldn't lose anything important.

Regards,
Jeremy Begg

Re: VMS server boots but nothing is loaded.

Jeremy Begg — Fri, 29 May 2009 05:41:49 GMT

There is a possible explanation for how your system disk got corrupted in the first place.

Your console output appears to show two Mylex Raid controllers with different configurations. What if drives had been swapped between controllers? I would hope the Mylex would detect this ... but maybe not, or maybe the RAID rebuild wasn't dnoe properly.

Regards,
Jeremy Begg

Re: VMS server boots but nothing is loaded.

Joewee — Tue, 02 Jun 2009 12:30:06 GMT

Hi,

I rebooted the server from the CD and restored system disk from recent backup and booted the server and all seems to be fine. Im not sure of the root cause of this problem. And no time to dig more in to it.

Thanks all of you for your time on this.

Re: VMS server boots but nothing is loaded.

Joewee — Tue, 02 Jun 2009 12:31:07 GMT

Backup in binary mode and reboot