Open VMS Boot Up Issue

[Malps]

Hi All

I have been trying to Boot Up an OVMS System Unsuccessfully.

I have attached here the Boot Logs Collected in Verbose mode.

The System goes through it's boot process showing error related to SECURESHRP. line as an Error(There could be more errors in the logs which I don't Understand)......

%%%%%%%%%%% OPCOM 4-AUG-2010 05:28:45.72 %%%%%%%%%%%
05:28:33.44 Node ALXNDR (csid 00010004) is now a VMScluster member

%RUN-S-PROC_ID, identification of created process is 2080040F
%DCL-W-ACTIMAGE, error activating image SECURESHRP
-CLI-E-IMGNAME, image file ALXNDR$DKA0:[SYS0.SYSCOMMON.][SYSLIB]SECURESHRP.EXE;1
-SYSTEM-F-PROTINSTALL, protected images must be installed
%DCL-W-ACTIMAGE, error activating image SECURESHRP
-CLI-E-IMGNAME, image file ALXNDR$DKA0:[SYS0.SYSCOMMON.][SYSLIB]SECURESHRP.EXE;1
-SYSTEM-F-PROTINSTALL, protected images must be installed
SYSTEM job terminated at 4-AUG-2010 05:28:48.07

Accounting information:
Buffered I/O count: 1168 Peak working set size: 6320
Direct I/O count: 691 Peak virtual size: 180368
Page faults: 1494 Mounted volumes: 0
Charged CPU time: 0 00:00:00.62 Elapsed time: 0 00:00:07.17


Normally, Beyond this an OVMS System shows login Prompt but here it doesn't show anything after this.

Sometime we press enter to get a Login prompt but here nothing happens after pressing enter.

I have been advised to boot a system in minimum mode & I am not sure how do we do it as I am new to OVMS.

Please Suggest.

Thank you

Deepak

[Volker Halle]

Deepak,

looks like SECURESHRP or any shared image itselfs needs are not correctly installed.

You need someone with real OpenVMS experience to figure out, why that is and how to solve that problem.

What happened to this system ? Did it ever work before ?

Volker.

[SDIH1]

Looks to me you miss startup1.com.

%STDRV-I-STARTUP, OpenVMS startup begun at 4-AUG-2010 05:28:41.23
%RMS-E-FNF, file not found

Like Volker, I think you need someone experienced to work on this, and I get the feeling this is a new system, or a system in the process of an upgrade.

Although not related to this problem, did you see the firmware message at the beginning of the log?

[Hoff · Accepted solution]

At first guess, the boot settings are bogus, or the system disk is corrupted.

There are many potential triggers.

As was mentioned previously, this:

%STDRV-I-STARTUP, OpenVMS startup begun at 4-AUG-2010 05:28:41.23
%RMS-E-FNF, file not found

Looks to be the key error.

That's usually the STARTUP.COM file.

If somebody has been messing with SYSBOOT (and that's likely, given folks are also clearly experimenting with semi-relevent console commands), I'd check and see of the startup file is set correctly.

Boot the Alpha box conversationally, and issue the following:

SYSBOOT> SHOW /STARTUP

That should show the SYS$SYSTEM:STARTUP.COM file.

If not, issue:

SYSBOOT> SET /STARTUP=SYS$SYSTEM:STARTUP.COM
SYSBOOT> CONTINUE

I'd then start by booting up from the CD or from another system disk here, and having a look at the contents of this system disk.

There are also pieces of Spiralog erroneously left over here. That's going to need to be expunged.

Based on other available information, this question has already been forwarded to HP and was being investigated by HP earlier today, so I'd work this issue with them.

[Bob Blunt]

Deepak in addition to the other suggestions I'd add the following. As recommended boot the machine conversationally but then add the following at the SYSBOOT> prompt.

SYSBOOT> SET STARTUP_P2 "CCC"

This should put the system into another layer of "verbose" boot. You've enabled the gory details of the APB by tweaking the boot flags. Setting STARTUP_P2 to "CCC" should enable tracking of the command procedures that are called or executed during the startup process. That should help give you a better idea what's triggering those mysterious "File not found" errors. This is an iterative process which can be time-consuming...or if you're starting to build a machine from scratch you might consider reloading from the distribution...

bob

[Malps]

Thank you all..

@ Volker

Yes, This system was working.

One of our developers rebooted it for some reason & this is our build machine in a cluster with other machine.

The other machine in the cluster is UP.

@ HoseBaars

I have attached the Boot logs from the Start now.

@Hoff

Tried your commands & the O/p is in the logs attached,

I will have to ask for a CD to boot however.

Please let me ,know if you get anything from HP about this.

@BOb

I tried the command you suggested & continued with boot up

But it booted like a normal boot(not in Verbose mode)

I Have attached the latest bootup logs.

[Richard Brodie_1]

sys$manager:vmsimages.dat is likely missing. Restore a working copy from your backups.

[Oswald Knoppers_1]

%STDRV-I-DIRECT, @SYS$STARTUP:VMS$INITIAL-050_VMS.COM
%RMS-E-FNF, file not found

This file seems to be missing.

You can boot from CD and copy this file to the startup directory.

Question remains why this file is gone.

Oswald

[Malps]

Hi

How do we boot the system in min mode?

I checked with my developers & it was advised that It could be because of the latest installation of a TCPIP Package.

What do you all think? Can it cause this?

We have been advised to uninstall it from Min mode.

I tried following steps.to get the system in min mode.I found this from OVMS Documentation website

1) >>>b -fl 0,1

2) SYSBOOT>SET STARTUP_P1 "MIN"

3) SYSBOOT>continue

It still gets me to the Account information stage.With no prompt to login.

[Oswald Knoppers_1]

>I checked with my developers & it was advised that It could be because of the latest installation of a TCPIP Package.

I dont think this would cause this.

You really need to boot from CD and restore the missing startup file.

Oswald