HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

%STDRV-F-FATALERR, fatal error reading startup database

 
SOLVED
Go to solution
Clark Powell
Frequent Advisor

%STDRV-F-FATALERR, fatal error reading startup database

Here's a fun one. I rebooted a test system and found that the boot failed with the message below. Nothing worked so I SET/START OPA0: and ran startup.com manually. Didn't learn much more. There's no editor and no verify to see more closely what is happening. Any suggestions? Do I have to move system disk to another node to inspect or is there a way around this road block?

thanks
Clark Powell

$ @ [SYS0.SYSCOMMON.SYSEXE]STARTUP.COM
%STDRV-I-STARTUP, OpenVMS startup begun at 6-JAN-2009 11:30:43.09
%STDRV-E-OPENFAIL, failure opening component file 0, STARTUP$STARTUP_VMS
%STDRV-I-CONTINUING, continuing with partial file list
%DCL-E-OPENIN, error opening STARTUP$PHASES as input
-RMS-F-FNM, error in file name
%DCL-W-UNDFIL, file has not been opened by DCL - check logical name
%DCL-W-INSFPRM, missing command parameters - supply all required parameters
%DCL-W-INSFPRM, missing command parameters - supply all required parameters
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PRODUCT_INFO\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$CURRENT_PHASE\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PRODUCT_INFO\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PRODUCT_INFO\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PRODUCT_INFO\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PARAM_END\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PARAM_END\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PARAM_END\
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$FLAG\
%STDRV-F-FATALERR, fatal error reading startup database
%DCL-W-UNDFIL, file has not been opened by DCL - check logical name
$
22 REPLIES
Robert Gezelter
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Clark,

The OP did not mention the platform, one presumes Alpha or Itanium (or the release).

I would suspect something wrong with the these (and possibly other) files.

Two possibilities:

- use the Standalone CD/DVD to do a verify and also a mount
- mount the disk on another running system (recommendation: mount privately).

- Bob Gezelter, http://www.rlgsc.com
Hakan Zanderau ( Anders
Trusted Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

You can set STARTUP_P2 = "v" and get a "VERIFY" for the boot.

Hakan Zanderau
Don't make it worse by guessing.........
cnb
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

SYS_PARAMETERS

STARTUP_P1-8

The following table describes possible values of STARTUP_P1
through _P8:

STARTUP
Value Description

STARTUP_P1 Specifies the type of system boot the system-
independent startup procedure is to perform when
STARTUP_P1 has one of the following values:

o " "- A full boot is performed.

o "MIN"- A minimum boot that starts only what is
absolutely necessary for the operating system
to run.

STARTUP_P2 Controls the setting of verification during the
execution of the system-independent startup
procedure, STARTUP.COM, when STARTUP_P2 has one
of the values described in the lists below.

STARTUP_P2 can be one of the values shown in the
following list:

o F[ALSE], N[O], 0, " "-Verification is not
enabled; in other words, NOVERIFY is performed.

o T[RUE], Y[ES], 1-Verification is enabled; in
other words, a SET VERIFY is performed.

Alternatively, STARTUP_P2 can be a string
containing one or more of the letters shown in
the following list:

o C-Display various checkpointing messages during
startup.

o D-Log (or Dump) the output from the startup to
a file called SYS$SPECIFIC:[SYSEXE]STARTUP.LOG.

o P-DCL verification is enabled for each
component file, but not for the startup driver.
If both P and V are used, P is ignored.

o V-Full DCL verification is enabled; same as
TRUE.

Refer to the SYSMAN command STARTUP SET OPTIONS
for more information about STARTUP_P2.
STARTUP_P3 Beginning in OpenVMS Version 7.2, if STARTUP_P3
is set to AGEN, the system executes AUTOGEN at the
end of the startup sequence.

STARTUP_P4 Reserved for future use.
through
STARTUP_P8
Clark Powell
Frequent Advisor

Re: %STDRV-F-FATALERR, fatal error reading startup database

All very good ideas, I'm studying the verbose boot and while I'm doing that, I'll share it. It crashes early on:

%STDRV-I-STARTUP, OpenVMS startup begun at 6-JAN-2009 12:08:40.13
$else
$endif
$stdrv$phase_pos = 0
$stdrv$phase_len = 12
$stdrv$mode_pos = 12
$stdrv$mode_len = 1
$stdrv$file_pos = 13
$stdrv$file_len = 79
$stdrv$param_pos = 93
$stdrv$enable_flag = "E"
$stdrv$disable_flag = "D"
$if p1.nes."FULL"
$else stdrv$vms_only = stdrv$false
$endif
$stdrv$param = "Initial Parameters"
$stdrv$invoc = f$integer(f$trnlnm("stdrv$invoc","lnm$startup_table",,"EXECUTIVE"
))
$stdrv$invoc = stdrv$invoc + 1
$define/exec/nolog/table=lnm$startup_table stdrv$invoc 1
$stdrv$phase_name = "stdrv$phase" + f$string(stdrv$invoc)
$stdrv$product_name = "stdrv$product" + f$string(stdrv$invoc)
$stdrv$save_layered = f$trnlnm("startup$startup_layered","lnm$system_table")
$stdrv$save_num = -1
$stdrv$startup_file = 0
$next_open_file:
$stdrv$comp_file = f$trnlnm("startup$startup_list","lnm$system_table",stdrv$star
tup_file)
$if stdrv$comp_file .eqs. "" then goto count_comp_files
$if stdrv$comp_file .eqs. "STARTUP$STARTUP_LAYERED" then stdrv$save_num = stdrv$
startup_file
$if stdrv$verbose then stdrv$say f$fao("%STDRV-I-OPENCOMP, opening component fil
e !UB, !AS", stdrv$startup_file, stdrv$comp_file)
$open/share/error=comp_error stdrv$product1_0 STARTUP$STARTUP_VMS
$comp_error:
$stdrv$say f$fao("%STDRV-E-OPENFAIL, failure opening component file !UB, !AS", s
tdrv$startup_file, stdrv$comp_file)
%STDRV-E-OPENFAIL, failure opening component file 0, STARTUP$STARTUP_VMS
$stdrv$say f$fao("%STDRV-I-CONTINUING, continuing with partial file list")
%STDRV-I-CONTINUING, continuing with partial file list
$count_comp_files:
$stdrv$comp_files = stdrv$startup_file - 1
$if f$trnlnm(stdrv$phase_name,"lnm$process_table").nes."" then $ close stdrv$pha
se1
$open/share=read stdrv$phase1 STARTUP$PHASES
%DCL-E-OPENIN, error opening STARTUP$PHASES as input
-RMS-F-FNM, error in file name
$get_phase:
$read/end=done_all_phases stdrv$phase1 stdrv$current_phase
%DCL-W-UNDFIL, file has not been opened by DCL - check logical name
$if stdrv$verbose then -
stdrv$say f$fao("!/%STDRV-I-STRTPHAS, starting phase !AS at !%D",stdrv$current_p
hase,0)
$define/nolog startup$phase_name
%DCL-W-INSFPRM, missing command parameters - supply all required parameters
$stdrv$num_batch_jobs = 0
$stdrv$startup_file = 0
$goto first_file
$first_file:
$if stdrv$verbose then stdrv$say f$fao("%STDRV-I-INDXFILE, using component file
!UB", stdrv$startup_file)
$stdrv$first = stdrv$true
$if stdrv$startup_file .eq. stdrv$save_num .and. -
stdrv$save_layered .nes. f$trnlnm("startup$startup_layered","lnm$system_table")
$endif
$goto get_product
$get_product:
$if stdrv$first
$then
$read/end=next_file/error=read_error/nolock -
/index=0/key= stdrv$product1_0 stdrv$product_info
%DCL-W-INSFPRM, missing command parameters - supply all required parameters
$stdrv$first = stdrv$false
$else
$endif
$goto cont
$cont:
$if stdrv$param.nes.""
$then
$stdrv$x1 = p1
$stdrv$x2 = p2
$stdrv$x3 = p3
$stdrv$x4 = p4
$stdrv$x5 = p5
$stdrv$x6 = p6
$stdrv$x7 = p7
$stdrv$x8 = p8
$endif
$stdrv$phase = f$edit(f$extract(stdrv$phase_pos,stdrv$phase_len,stdrv$product_in
fo),"COLLAPSE")
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PRODUCT_INFO\
$if stdrv$phase.nes.stdrv$current_phase then goto next_file
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$CURRENT_PHASE\
$stdrv$mode = f$extract(stdrv$mode_pos,stdrv$mode_len,stdrv$product_info)
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PRODUCT_INFO\
$stdrv$filen = f$edit(f$extract(stdrv$file_pos,stdrv$file_len,stdrv$product_info
),"COLLAPSE")
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PRODUCT_INFO\
$stdrv$param_end = f$locate(stdrv$end_field,stdrv$product_info)
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PRODUCT_INFO\
$stdrv$param = f$extract(stdrv$param_pos,stdrv$param_end-stdrv$param_pos,stdrv$p
roduct_info)
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PARAM_END\
$stdrv$flag = f$extract(stdrv$param_end+1,1,stdrv$product_info)
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PARAM_END\
$stdrv$node = ","+f$extract(stdrv$param_end+2,200,stdrv$product_info)
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$PARAM_END\
$if stdrv$file_to_run.nes."*"
$endif
$run_file:
$if (stdrv$flag.eqs.stdrv$enable_flag)
%DCL-W-UNDSYM, undefined symbol - check validity and spelling
\STDRV$FLAG\
$then
$endif
$goto get_product
$get_product:
$if stdrv$first
$else
$read/end=next_file/error=read_error/nolock stdrv$product1_0 stdrv$product_info
$read_error:
$stdrv$error_code == $status
$if stdrv$error_code.eq.%X000182B2
$endif
$stdrv$say "%STDRV-F-FATALERR, fatal error reading startup database"
%STDRV-F-FATALERR, fatal error reading startup database
$exit stdrv$error_code
SYSTEM job terminated at 6-JAN-2009 12:08:46.68

Accounting information:
Buffered I/O count: 216 Peak working set size: 5184
Direct I/O count: 68 Peak virtual size: 183296
Page faults: 197 Mounted volumes: 0
Charged CPU time: 0 00:00:00.03 Elapsed time: 0 00:00:06.99
Robert Gezelter
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Clark,

SYS$STARTUP:VMS$PHASES.DAT would appear to be missing. This file is normally in [VMS$COMMON.SYS$STARTUP] (the verify output shows the OPEN command failing with a "file not found"). Errors after than point are a cascade.

As a starting point, I wonder if [VMS$COMMON.SYS$STARTUP] is intact. As I mentioned previously, I would want to verify that the file structure is intact overall.

- Bob Gezelter, http://www.rlgsc.com
cnb
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Hmmm..

%STDRV-E-OPENFAIL, failure opening component file 0, STARTUP$STARTUP_VMS
%STDRV-I-CONTINUING, continuing with partial file list
%DCL-E-OPENIN, error opening STARTUP$PHASES as input
-RMS-F-FNM, error in file name

What exactly did you input for set/startup? It looks like you have a syntax error.
1) Suggest you set it back to SYS$SYSTEM:STARTUP.COM
2) Boot minimum with verify using P1 & P2

What version and h/w platform of VMS are you using?
Robert Gezelter
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Clark,

After CNB's post, I took a look. Indeed, the database file is also inaccessible.

I double emphasize: Check the directory and file structure.

- Bob Gezelter, http://www.rlgsc.com
EdgarZamora_1
Respected Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

I think you have a simple typo/misdefinition somewhere. Some things I would check...

sysgen> show/startup
sysgen> show startup_p1 p2... p3... etc.

$ show log sys$startup


good luck!

Cass Witkowski
Trusted Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Just an FYI, we had some zealous admin clean up the system disk by deleting old .DAT files from the system disk. VMSIMAGES.DAT was one unlucky victim.

Since this file is only used at boot time it was hard to determine when it was actually deleted. It may be a reason for this file to be missing.
Willem Grooters
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Stating platform and VMS version would be handy...

[quote]
$open/share/error=comp_error stdrv$product1_0 STARTUP$STARTUP_VMS
$comp_error:
$stdrv$say f$fao("%STDRV-E-OPENFAIL, failure opening component file !UB, !AS", s
tdrv$startup_file, stdrv$comp_file)
%STDRV-E-OPENFAIL, failure opening component file 0, STARTUP$STARTUP_VMS
[/quote]

Conclusion: Something is wrong with file "STARTUP$STARTUP_VMS". I have no Alpha at hand to see what it should refer to (as a logical of a file specification).
As Bob Gezelter already mentioned: check your file structure. If your system disk is ODS-5, check case of directory- and filenames. IIRC, I once had a problem on boot from an ODS-5 disk where one of the required directories had not been named in uppercase.
Willem Grooters
OpenVMS Developer & System Manager
Hakan Zanderau ( Anders
Trusted Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

The logical STARTUP$STARTUP_VMS points to SYS$STARTUP:VMS$VMS.DAT

Check if the file exist or if you can read it.

Hakan Zanderau
Don't make it worse by guessing.........
Willem Grooters
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

And what is shown by

$ SHO LOG/FULL SYS$STARTUP
$ SHO DEV/FULL SYS$STARTUP

The latter to find out if it's a ODS-2 or ODS-5 structured disk. As stated before, non-uppercase directory names _could_ cause trouble - here, or before this point.
Willem Grooters
OpenVMS Developer & System Manager
Clark Powell
Frequent Advisor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Sorry about the delay in answering; this is a test system and I was involved in production issues. Priority on this problem is low as I don't need to fix this problem; I will simply use our disaster recovery tapes and create a new one. On the other hand, it would be useful to know why this system failed so profoundly, out of the blue. A test system can be abused and I do abuse it but I can think of nothing that would have caused this problem. Here's a little bit more data. If we can't figure the problem out with this data then I would like to put it aside. If it happens again I will have more input as to how it go this way.

One thing I don't understand about what's going on here is why the logical, sys$system is not defined yet it works as
@sys$system:startup.com There may aspect of OpenVMS at work here that I don't understand.
Also why is the default directory
DSA10:[SYSEXE]?
$ dir
%DIRECT-E-OPENIN, error opening DSA10:[SYSEXE]*.*;* as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
$ sho def
DSA10:[SYSEXE]
%DCL-I-INVDEF, DSA10:[SYSEXE] does not exist

disk is ODS2
Volume Status: ODS-2, subject to mount verification, write-through caching
enabled.


$ show log sys$system:
%SYSTEM-W-IVLOGTAB, invalid logical name table
%SHOW-S-NOTRAN, no translation for logical name SYS$SYSTEM:
$ sho log startup$startup_list
%SYSTEM-W-IVLOGTAB, invalid logical name table
%SHOW-S-NOTRAN, no translation for logical name STARTUP$STARTUP_LIST
$ sho log startup$startup_list
%SYSTEM-W-IVLOGTAB, invalid logical name table
%SHOW-S-NOTRAN, no translation for logical name STARTUP$STARTUP_LIST
$ dir
%DIRECT-E-OPENIN, error opening DSA10:[SYSEXE]*.*;* as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
$
$ sho log SYS$STARTUP
sho log SYS$STARTUP
%SYSTEM-W-IVLOGTAB, invalid logical name table
%SHOW-S-NOTRAN, no translation for logical name SYS$STARTUP
$ show log STARTUP$STARTUP_VMS
show log STARTUP$STARTUP_VMS
%SYSTEM-W-IVLOGTAB, invalid logical name table
%SHOW-S-NOTRAN, no translation for logical name STARTUP$STARTUP_VMS
$ show log sys$system
%SYSTEM-W-IVLOGTAB, invalid logical name table
%SHOW-S-NOTRAN, no translation for logical name SYS$SYSTEM

$ @SYS$SYSTEM:STARTUP.COM
%STDRV-I-STARTUP, OpenVMS startup begun at 8-JAN-2009 09:12:09.18
$else
$endif
$stdrv$phase_pos = 0
$stdrv$phase_len = 12
$stdrv$mode_pos = 12
$stdrv$mode_len = 1
$stdrv$file_pos = 13
$stdrv$file_len = 79
$stdrv$param_pos = 93
$stdrv$enable_flag = "E"
$stdrv$disable_flag = "D"
$if p1.nes."FULL"
$then stdrv$vms_only = stdrv$true
$else stdrv$vms_only = stdrv$false
$endif
$stdrv$param = "Initial Parameters"
$stdrv$invoc = f$integer(f$trnlnm("stdrv$invoc","lnm$startup_table",,"EXECUTIVE"
))
$stdrv$invoc = stdrv$invoc + 1
$define/exec/nolog/table=lnm$startup_table stdrv$invoc 1
$stdrv$phase_name = "stdrv$phase" + f$string(stdrv$invoc)
$stdrv$product_name = "stdrv$product" + f$string(stdrv$invoc)
$stdrv$save_layered = f$trnlnm("startup$startup_layered","lnm$system_table")
$stdrv$save_num = -1
$stdrv$startup_file = 0
$next_open_file:
$stdrv$comp_file = f$trnlnm("startup$startup_list","lnm$system_table",stdrv$star
tup_file)
$if stdrv$comp_file .eqs. "" then goto count_comp_files
$if stdrv$comp_file .eqs. "STARTUP$STARTUP_LAYERED" then stdrv$save_num = stdrv$
startup_file
$if stdrv$verbose then stdrv$say f$fao("%STDRV-I-OPENCOMP, opening component fil
e !UB, !AS", stdrv$startup_file, stdrv$comp_file)
$open/share/error=comp_error stdrv$product1_0 STARTUP$STARTUP_VMS
$comp_error:
$stdrv$say f$fao("%STDRV-E-OPENFAIL, failure opening component file !UB, !AS", s
tdrv$startup_file, stdrv$comp_file)
%STDRV-E-OPENFAIL, failure opening component file 0, STARTUP$STARTUP_VMS
$stdrv$say f$fao("%STDRV-I-CONTINUING, continuing with partial file list")
%STDRV-I-CONTINUING, continuing with partial file list
$count_comp_files:
$stdrv$comp_files = stdrv$startup_file - 1
$if f$trnlnm(stdrv$phase_name,"lnm$process_table").nes."" then $ close stdrv$pha
se1
$open/share=read stdrv$phase1 STARTUP$PHASES
$get_phase:
$read/end=done_all_phases stdrv$phase1 stdrv$current_phase
$if stdrv$verbose then -
stdrv$say f$fao("!/%STDRV-I-STRTPHAS, starting phase !AS at !%D",stdrv$current_p
hase,0)
$define/nolog startup$phase_name INITIAL
$stdrv$num_batch_jobs = 0
$stdrv$startup_file = 0
$goto first_file
$first_file:
$if stdrv$verbose then stdrv$say f$fao("%STDRV-I-INDXFILE, using component file
!UB", stdrv$startup_file)
$stdrv$first = stdrv$true
$if stdrv$startup_file .eq. stdrv$save_num .and. -
stdrv$save_layered .nes. f$trnlnm("startup$startup_layered","lnm$system_table")
$endif
$goto get_product
$get_product:
$if stdrv$first
$then
$read/end=next_file/error=read_error/nolock -
/index=0/key=INITIAL stdrv$product1_0 stdrv$product_info
$read_error:
$stdrv$error_code == $status
$if stdrv$error_code.eq.%X000182B2
$endif
$stdrv$say "%STDRV-F-FATALERR, fatal error reading startup database"
%STDRV-F-FATALERR, fatal error reading startup database
$exit stdrv$error_code
%DCL-W-UNDFIL, file has not been opened by DCL - check logical name
$
Hakan Zanderau ( Anders
Trusted Contributor
Solution

Re: %STDRV-F-FATALERR, fatal error reading startup database

Did you check the file SYS$STARTUP:VMS$VMS.DAT ?

[VMS$COMMON.SYS$STARTUP]VMS$VMS.DAT

You get the first errormessage because the file can't be opened

Hakan
Don't make it worse by guessing.........
Robert Gezelter
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Clark,

I do not have my references handy. I would have to check why SYS$SYSTEM seems to be undefined yet appears to work at that point.

Basically, if one gets control BEFORE STARTUP.COM executes, the system is not completely functional. There is a bare minimum functionality, and STARTUP.COM is crafted to not work outside of these limits. As the startup sequence progresses, more and more of the system is usable.

By the time one gets to LP* phases, almost all of the system is usable.

I do not see an answer to what is the status of the [VMS$COMMON.SYS$STARTUP] directory. At this point in the life of the system, I generally DO NOT use logical names, I explicitly enumerate the path [That may be an acquired quirk from the dark ages, but it is depoendable].

- Bob Gezelter, http://www.rlgsc.com
Clark Powell
Frequent Advisor

Re: %STDRV-F-FATALERR, fatal error reading startup database

OK, thanks Bob, that explains a lot. And thanks, Hakan, I did find that SYS$STARTUP:VMS$VMS.DAT is missing and when I copied one from a backup I got a plethora of new errors. I don't think that this disk is salvageable but I do think that I should be thoughtful to see if I can recreate the problem because it may be unrecoverable in any case. I am using some beta distributions so I need to go through the motions of installing these and see if this is the source of the problem. It difficult because the problem only makes booting impossible; the system keeps running until one tries to reboot. It sure does emphasize the golden rule of new software and that is, keep a shadow copy of the system disk for an orderly retreat. So I'm going to focus on figuring out what caused this and warning any developers if necessary. Following this will be the log which I present for curiosity only.

%EIA0, Link state change: UP
%EIB0, Link state change: UP
%SHADOW-I-VOLPROC, DSA10: is offline. Volume Processing in progress.

%SHADOW-I-VOLPROC, DSA10: has completed volume processing.

%STDRV-I-STARTUP, OpenVMS startup begun at 8-JAN-2009 10:50:17.40
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$INITIAL-050_VMS.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$INITIAL-050_LIB.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$INITIAL-050_CONFIGURE.COM does not exi
st.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_CSP.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_SHADOW_SERVER.COM does not
exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$DEVICE_STARTUP.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:IPC$STARTUP.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_VMS.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_ERRFMT.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_CACHE_SERVER.COM does not e
xist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_OPCOM.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_AUDIT_SERVER.COM does not e
xist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_JOBCTL.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_LMF.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_SECURITY_SERVER.COM does no
t exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$CONFIG-050_ACME_SERVER.COM does not ex
ist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$BASEENVIRON-050_VMS.COM does not exist
.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$BASEENVIRON-050_SMISERVER.COM does not
exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$BASEENVIRON-050_LIB.COM does not exist
.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:DECDTM$STARTUP.COM does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:LICENSE_CHECK.EXE does not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$BASEENVIRON-050_INDICT_SERVER.COM does
not exist.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$LPBEGIN-050_STARTUP.COM does not exist
.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$LPBEGIN-050_SMHANDLER.COM does not exi
st.
%STDRV-E-NOSUCHFILE, File SYS$STARTUP:VMS$END-050_COORDINATED.COM does not exist
.
SYSTEM job terminated at 8-JAN-2009 10:50:20.26

Accounting information:
Buffered I/O count: 173 Peak working set size: 5184
Direct I/O count: 80 Peak virtual size: 183296
Page faults: 203 Mounted volumes: 0
Charged CPU time: 0 00:00:00.04 Elapsed time: 0 00:00:03.07

Robert Gezelter
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Clark,

Please compare a directory listing of [VMS$COMMON.SYS$STARTUP] and [SYSn.SYSMGR] on the "damaged" system and its undamaged BACKUP.

You are getting error messages indicating that the various component files invoked by STARTUP.COM are missing.

Without data, my guess would be that somebody deleted the contents of this directory. Note that SYS$STARTUP (the logical name) includes both the SYS$SPECIFIC and SYS$COMMON contents of BOTH [SYS$STARTUP] and [SYSMGR] (you can see this on any properly running OpenVMS system by using SHOW LOGICAL). This logical name search sequence is what allows LAT$STARTUP.COM to be in SYS$COMMON:[SYS$STARTUP] (which is actually [VMS$COMMON.SYS$STARTUP]) and LAT$SYSTARTUP.COM to be in [SYSMGR] (actually, any of the four directories referenced above; normally clusterwide LAT$SYSTARTUP.COM is in SYS$COMMON:[SYSMGR] if it is node-specific, it is in SYS$SPECIFIC:[SYSMGR]).

As I mentioned, check ALL of the files. Working one at a time will just slow progress.

- Bob Gezelter, http://www.rlgsc.com
EdgarZamora_1
Respected Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

It is possible that you think files are missing when they're actually not. If I'm not mistaken you are using logical names when you look for the files. Your logicals are hosed. Use the actual directory paths... i.e. instead of looking for SYS$STARTUP:VMS$VMS.DAT look for [VMS$COMMON.SYS$STARTUP]VMS$VMS.DAT.

What do

SYSGEN> SHOW STARTUP
SYSGEN> SHOW STARTUP_P1 ... Pn show?
Clark Powell
Frequent Advisor

Re: %STDRV-F-FATALERR, fatal error reading startup database

No, files are missing; I'm checking the actual directorys and not logicals. I think that it's possible that a PRODUCT REMOVE command did this but I will have to try to reproduce the problem to find out. Thanks, everyone for the help.
Willem Grooters
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

[quote]
Also why is the default directory
DSA10:[SYSEXE]?
$ dir
%DIRECT-E-OPENIN, error opening DSA10:[SYSEXE]*.*;* as input
-RMS-E-DNF, directory not found
-SYSTEM-W-NOSUCHFILE, no such file
$ sho def
DSA10:[SYSEXE]
%DCL-I-INVDEF, DSA10:[SYSEXE] does not exist
[/quote]

This is wrong.
DSA10: should normally be a device (here: shadowset) OR a (concealed) logical.
$ SHO LOG/FULL DSA10 would tell. It should refer to a physical disk.

If DSA10 is a device, your SYSUAF data for SYSTEM is probably broken and all references of logical could be wrong. It should read "SYS$SYSROOT:[SYSMGR]" - and logical SYS$SYSROOT would need to be ":[SYSn.], SYS$COMMON:" ans SYS$COMMON would be referring to ":
[SYSn.SYSCOMMON.]"
All with attributes EXEC and (concealed, terminal).

Second:
Since this is DSA - meaning: shadowset. That reminds me: have you specified the system should boot from a shadowset? There are sos SYSGEN parameters involved here - that you could set booting MINimal.

[quote]
disk is ODS2
Volume Status: ODS-2, subject to mount verification, write-through caching
enabled.
[/quote]
Ok, so no problem here.

[quote]
$ show log sys$system:
%SYSTEM-W-IVLOGTAB, invalid logical name table
%SHOW-S-NOTRAN, no translation for logical name SYS$SYSTEM
[/quote]

That means something more trouble. The logical may have been set but the logical name table is either not accessable, or not in the searchpatch. Check:

$ sho log/table=lnm$system_directory
$ sho log/table=lnm$process_directory

in either one of them table lnm$startup_table should be mentioned.

The table would contain all the logicals you're missing. IIRC, this is the table that is heavily used during startup - it's defines (and connected) pretty early in the boot process.

Willem Grooters
OpenVMS Developer & System Manager
Clark Powell
Frequent Advisor

Re: %STDRV-F-FATALERR, fatal error reading startup database

I have confirmation that the missing files were deleted by a PCSI installation of a beta test Hp product. Developers have been notified and will fix this problem. Since it is not a released version I will not name the product to protect the innocent. The really insidious thing about this problem is that the files deleted were only needed for boot so if this happened, one would not know until one had rebooted the system. So I guess this indicates two rules of installing software:
1.) Always reboot before and after, if you can.
2.) Always make a shadow copy of the system disk and the target disk.

I think we can close this now.
Willem Grooters
Honored Contributor

Re: %STDRV-F-FATALERR, fatal error reading startup database

Backup BEFORE installation, that is ;).
Willem Grooters
OpenVMS Developer & System Manager