- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: %STDRV-F-FATALERR, fatal error reading startup...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2009 03:56 AM
тАО01-07-2009 03:56 AM
Re: %STDRV-F-FATALERR, fatal error reading startup database
[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.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2009 04:21 AM
тАО01-07-2009 04:21 AM
Re: %STDRV-F-FATALERR, fatal error reading startup database
Check if the file exist or if you can read it.
Hakan Zanderau
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-07-2009 08:17 AM
тАО01-07-2009 08:17 AM
Re: %STDRV-F-FATALERR, fatal error reading startup database
$ 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.
OpenVMS Developer & System Manager
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2009 09:45 AM
тАО01-08-2009 09:45 AM
Re: %STDRV-F-FATALERR, fatal error reading startup database
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
$
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2009 09:54 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2009 10:42 AM
тАО01-08-2009 10:42 AM
Re: %STDRV-F-FATALERR, fatal error reading startup database
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2009 11:06 AM
тАО01-08-2009 11:06 AM
Re: %STDRV-F-FATALERR, fatal error reading startup database
%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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-08-2009 12:39 PM
тАО01-08-2009 12:39 PM
Re: %STDRV-F-FATALERR, fatal error reading startup database
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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-09-2009 05:52 AM
тАО01-09-2009 05:52 AM
Re: %STDRV-F-FATALERR, fatal error reading startup database
What do
SYSGEN> SHOW STARTUP
SYSGEN> SHOW STARTUP_P1 ... Pn show?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО01-09-2009 11:19 AM
тАО01-09-2009 11:19 AM