openvms boot crash

Everything about buying, using, and managing OpenVMS systems not covered by other sections.
Post Reply

Topic author
avnt
Visitor
Posts: 1
Joined: Mon Sep 04, 2023 8:21 pm
Reputation: 0
Status: Offline

openvms boot crash

Post by avnt » Mon Sep 04, 2023 8:28 pm

hi all,

I need some advice with my problem.
I downloaded student ovms image and boot openvms several times successfully for learning purposes.
I tested the OS by boot previous date to see what happen. System wont boot up. Can I clear up the date parameter and let the system boot normally or is there any sysboot parameters I need to modify to allow it to continue booting with old date?

Code: Select all

>>> boot dka100
(boot -file '' -flags '' 'dka100')
BOOT_RESET is ON: cold boot
Booting from the device 'dka100' file ''
Loaded the primary booter; size 0x94000


    OpenVMS (TM) Alpha Operating System, Version V8.4-2L2
                    Copyright 2017 VMS Software, Inc.


Please enter date and time (DD-MMM-YYYY  HH:MM)  02-SEP-2023 00:00
%STDRV-I-STARTUP, OpenVMS startup begun at  2-SEP-2023 00:00:42.27

**** OpenVMS Alpha Operating System V8.4-2L2 - BUGCHECK ****

** Bugcheck code = 00000214: MACHINECHK, Machine check while in kernel mode
** Crash CPU: 00000000    Primary CPU: 00000000    Node Name: STUDNT
** Highest CPU number:    00000000
** Active CPUs:           00000000.00000001
** Current Process:       STARTUP
** Current PSB ID:        00000001
** Image Name:            STUDNT$DKA100:[SYS0.SYSCOMMON.][SYSEXE]SYSMAN.EXE

**** Starting compressed selective memory dump at  2-SEP-2023 00:00...
.........................
** System space, key processes, and key global pages have been dumped.
** Now dumping remaining processes and global pages...
...Complete ****
Last edited by marty.stu on Tue Sep 05, 2023 5:22 am, edited 1 time in total.

User avatar

volkerhalle
Master
Posts: 198
Joined: Fri Aug 14, 2020 11:31 am
Reputation: 0
Status: Offline

Re: openvms boot crash

Post by volkerhalle » Tue Sep 05, 2023 6:50 am

A MACHINECHK crash is typically caused by a 'hardware' problem.

In this case, the SYSMAN image may probably be executing 'IO AUTOCONFIGURE'

You could try a conversational boot:

>>> b -fl 0,1 dka100

SYSBOOT> SET STARTUP_P1 "MIN"
SYSBOOT> CONT

Then try MC SYSMAN IO AUTO/LOG and see if it crashes again.

Volker.

Post Reply