Description

VMS cannot boot due to damaged boot block

If the system disk is accessible in read-only mode, this is because Charon detected a Windows partition on the disk. In such a case, the boot block repair operation will not succeed and you will have to re-create the disk (Windows disk partition removal) and perform a full VMS system disk restore.

This procedure is also requested when moving a system disk from VAX 7000 to VAX 66x0

Step-by-step guide

For VAX systems, please click here

Alpha systems

Boot error message

P00>>>boot dka100
(boot dka100.1.0.1.1)
boot block integrity verification failure

Repair operations

In the example given below we will assume dka100 is the VMS system disk and dka300 is the CDROM drive.

Either boot from the OpenVMS installation CDROM, or its .iso file, or from another already installed OpenVMS system disk

Example with a CDROM boot:

P00>>>boot dka300
(boot dka300.3.0.1.1)
jumping to bootstrap code

OpenVMS (TM) Alpha Operating System, Version V7.3-2
© Copyright 1976-2003 Hewlett-Packard Development Company, L.P.

Please enter date and time (DD-MMM-YYYY HH:MM) 16-DEC-2014 17:45

Installing required known files...

Configuring devices...
%EWA0, Auto-negotiation mode set by console
%EWA0, Auto-negotiation (internal) starting
%EWA0, Full Duplex 10BaseT connection selected
%EWA0, Auto-negotiation (internal) starting
%EWA0, Full Duplex 10BaseT connection selected

****************************************************************

    You can install or upgrade the OpenVMS Alpha operating system
        or you can install or upgrade layered products that are included
        on the OpenVMS Alpha operating system CD-ROM.

You can also execute DCL commands and procedures to perform
"standalone" tasks, such as backing up the system disk.

Please choose one of the following:

        1) Upgrade, install or reconfigure OpenVMS Alpha Version V7.3-2
        2) Display products and patches that this procedure can install
        3) Install or upgrade layered products and patches
        4) Show installed products
        5) Reconfigure installed products
        6) Remove installed products
        7) Execute DCL commands and procedures
        8) Shut down this system

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 7

WARNING --

    The normal OpenVMS startup procedure has not executed.
    Some commands and utilities will not work as documented.
    HP does not support PRODUCT INSTALL and other
    PRODUCT operations in this environment.

    Enter DCL commands – Enter "LOGOUT" when done.
    When you enter "LOGOUT" a message will be displayed saying
    "Process SA_STARTUP_DCL logged out at <date> <time>",
    and you will be returned to the menu.

$$$

Identify the system disk and mount it:

$$$ show device d

Device                  Device    Error    Volume Free Trans Mnt
Name                   Status            Count Label      Blocks Count Cnt
DAD0:                   Online                0
DKA0:                   Online                0
DKA100:                 Online                0
DKA300:                 Mounted wrtlck        0 ALPHA0732        7791   48 1
DKA302:                 Online wrtlck         0
DVA0: Offline               0
$$$ mount /override=identification dka100:
%MOUNT-I-MOUNTED, ALPHASYS mounted on _DKA100:
$$$

Install the boot block:

$$$ run sys$system:writeboot
Update VAX portion of boot block (default is Y) : n
Update AXP portion of boot block (default is Y) : y
Enter AXP boot file : dka100:[vms$common.sysexe]apb.exe

Analyze the disk for repair (optional but recommended):

$$$ analyze /disk /repair dka100:
Analyze/Disk_Structure/Repair for _DKA100: started on 16-DEC-2014 18:04:50.67

%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
-SYSTEM-W-NOSUCHFILE, no such file
$$$

Logout and shutdown the system:

$$$ logout
Process SA_STARTUP_DCL logged out at 16-DEC-2014 18:07:04.11
...
7) Execute DCL commands and procedures
8) Shut down this system

Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/?) 8

Shutting down the system

SYSTEM SHUTDOWN COMPLETE

halted CPU 0

halt code = 5
HALT instruction executed
PC = ffffffff800a3fdc
P00>>>

You can now boot the system:

P00>>>boot dka100

resetting all I/O buses

initializing ...

polling for units on kzpba0, slot 1, bus 0, hose 1 ...
pka0.0.0.1.1 PKA0 Q-Logic/ISP PCI SCSI HBA

(boot dka100.1.0.1.1)
jumping to bootstrap code

OpenVMS (TM) Alpha Operating System, Version V7.3-2
© Copyright 1976-2003 Hewlett-Packard Development Company, L.P.
...

VAX systems

Boot error message

>>>boot dka0
(BOOT/R5:0 DKA0)

2..
-DKA0
?43 FILESTRUCT, DKA0
?06 HLT INST
PC = 00000F39
Bootstrap failure.

Repair operations

In the example given below we will assume dka0 is the production system disk and dka200 is the backup system disk.

Either boot from the OpenVMS installation CDROM, or its .iso file, or from another already installed OpenVMS system disk

Example with a boot from a second system disk:

>>>boot dka200
(BOOT/R5:0 DKA200)

2..
-DKA200
1..0..

%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
OpenVMS (TM) VAX Version V7.1 Major version id = 1 Minor version id = 0
...

Welcome to OpenVMS (TM) VAX Operating System, Version V7.1

Username:

Install the boot block:

$ mount /override=identification dka0:
%MOUNT-W-HOMBLKBAD, primary home block is bad; backup used
%MOUNT-I-MOUNTED, OPENVMS071 mounted on _BAK071$DKA0:
$ run sys$system:writeboot
Target system device (and boot file if not VMB.EXE): dka0:[VMS$COMMON.SYSEXE]VMB.EXE
Enter VBN of boot file code (default is 1) : <press return>
Enter load address of primary bootstrap in HEX (default is 200): <press return>
$

Analyze the disk for repair (optional but recommended):

$ analyze /disk /repair dka0:

Analyze/Disk_Structure/Repair for _BAK071$DKA0: started on 12-JAN-2015 13:24:42.56

%ANALDISK-W-CHKALTHOME, invalid alternate home block, VBN 2, RVN 1
%ANALDISK-I-OPENQUOTA, error opening QUOTA.SYS
-SYSTEM-W-NOSUCHFILE, no such file
%ANALDISK-W-DELHEADER, file (888,1,1) SYS.EXE;1
marked for delete
$

Shutdown the system and reboot with the production system disk:

$ @sys$system:shutdown

SHUTDOWN – Perform an Orderly System Shutdown
on node BAK071

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
%%%%%%%%%%% OPCOM 12-JAN-2015 13:17:22.61 %%%%%%%%%%%
...

SYSTEM SHUTDOWN COMPLETE - use console to halt system

Either press CTRL-P if enabled in the configuration file or stop and restart the emulator:

>>>boot dka0
(BOOT/R5:0 DKA0)

2..
-DKA0
1..0..

...

%SYSBOOT-I-SYSBOOT Mapping the SYSDUMP.DMP on the System Disk
%SYSBOOT-I-SYSBOOT SYSDUMP.DMP on System Disk successfully mapped
OpenVMS (TM) VAX Version V7.1 Major version id = 1 Minor version id = 0

...
Username:

Related articles

Page:

DEC VAX-VMS use is not authorized on this node
Page:

DECNET might hang during OpenVMS boot if TCPIP is configured
Page:

How to repair VMS boot block

Browser not supported