SOLVED: X8691AOE boots OK - X8692OE fails as follows

OpenVMS x86 Field Test questions, reports, and feedback.
Post Reply

Topic author
mgdaniel
Valued Contributor
Posts: 62
Joined: Mon Feb 28, 2022 5:16 pm
Reputation: 0
Location: Adelaide, South Australia
Status: Offline
Contact:

SOLVED: X8691AOE boots OK - X8692OE fails as follows

Post by mgdaniel » Fri Apr 15, 2022 1:37 pm

BOOTMGR> boot
Booting...
%VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
100%
%VMS_BOOTMGR-F-MEMDISK, Invalid MemoryDisk image. ID:2.0, Sig:0x24534D56, Exp:0x24534D56
%VMS_BOOTMGR-F-MEMDISK, Unable to load DMM0.
%VMS_BOOTMGR-E-MEMDISK, Unable to load memory disk.
%VMS_BOOTMGR-F-MEMDISK, Unable to load selected boot image.
%VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.

Added in 2 hours 24 minutes 32 seconds:
Seems as if the 9.2 ISO (VMS_BOOTMGR?) is device order sensitive.

With the ISO at dka0 (SATA port 0), with device specification:
> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA100 (HD) = FS2 UEFI: V9_1_A OpenVMS: X86SYS 16384 MB SATA Disk
> DKA0 (DVD) = FS1 UEFI: E9_2 OpenVMS: None 1263 MB SATA DVD
>
> BOOTMGR> boot dka0
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
8< snip 8<
And without device specification:
> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA100 (HD) = FS2 UEFI: V9_1_A OpenVMS: X86SYS 16384 MB SATA Disk
> DKA0 (DVD) = FS1 UEFI: E9_2 OpenVMS: None 1263 MB SATA DVD
>
> BOOTMGR> boot
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
8< snip 8<
But with my original config (ISO at SATA port 2):
> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA0 (HD) = FS0 UEFI: V9_1_A OpenVMS: X86SYS 0 MB SATA Disk
> DKA200 (DVD) = FS2 UEFI: E9_2 OpenVMS: None 1263MB SATA DVD
>
> BOOTMGR> boot dka200
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
> %VMS_BOOTMGR-F-MEMDISK, Invalid MemoryDisk image. ID:2.0, Sig:0x24534D56, Exp:0x24534D56
> %VMS_BOOTMGR-F-MEMDISK, Unable to load DMM0.
> %VMS_BOOTMGR-E-MEMDISK, Unable to load memory disk.
> %VMS_BOOTMGR-F-MEMDISK, Unable to load selected boot image.
> %VMS_BOOTMGR-F-MAIN, Unable to load MemoryDisk from boot device.
8< snip 8<
This was *not* the behaviour with the 9.1A ISO (and still isn't):
> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA0 (HD) = FS0 UEFI: V9_1_A OpenVMS: X86SYS 0 MB SATA Disk
> DKA200 (DVD) = FS2 UEFI: V9_1_A OpenVMS: None 918 MB SATA DVD
>
> BOOTMGR> boot dka200
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%
8< snip 8<
Without device specification, still boots the install media:
> BOOTMGR> devices
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA0 (HD) = FS0 UEFI: V9_1_A OpenVMS: X86SYS 0 MB SATA Disk
> DKA200 (DVD) = FS2 UEFI: V9_1_A OpenVMS: None 918 MB SATA DVD
>
> BOOTMGR> boot
> BOOT
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
8< snip 8<
So there appears to be a change in behaviour between the 9.1-A and 9.2 ISOs, requiring 9.2 to be at dka0 (or some such).

The document; 2.2. Installing OpenVMS x86-64 V9.2, continues to suggest the order need not be specific:
7. At the BOOTMGR> prompt on the graphics console, type BOOTMGR> BOOT DKA0, where DKA0 represents the DVD device.
and
BOOTMGR> BOOT DKA100
Booting...
%VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
100%
%%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
8< snip lots from c.o.v. 8<

So the upshot appears to be the VMS_BOOTMGR is taken from the first bootable device (FS0...FSn), meaning you need to have the latest version first in the device list.

Added in 4 hours 53 minutes 21 seconds:
> So the upshot appears to be the VMS_BOOTMGR is taken from the first bootable device (FS0...FSn), meaning you need to have the latest version first in the device list.

*** NOT (strictly) TRUE - RTFM ***

The "2.1. Booting the Virtual Machine" states:
1. The following figure shows the graphics console that comes up when the VM is started. At the Shell> prompt, enter the command map fs* to display the file systems available on your system.

2. Choose the file system that maps to the .ISO file that you have downloaded and set up as a CDROM/DVD. The shell sees the .ISO file as a CDROM, so you need to choose an FSn that is labeled CDROM. In the above example, we know that fs1 is the .ISO that we want to boot.

3. Knowing that fs1 is associated with the CDROM that is the .ISO, enter the following command to run the Boot Manager:
fs1:\efi\vms\vms_bootmgr.efi
I must have gotten into the habit of running the BootMgr

Shell> vms_bootmgr

and then booting 9.1-A VMS with a simple

BOOTMGR> BOOT

which was happy as long as DKA0 (bootable system disk) had the 9.1-A BootMgr. It was a poor recipe when "upgrading".

And of course...

Had the 9.2 installation had a non-bootable .VDI (DKA0) the previous BootMgr would not have been invoked and the simple BOOT would have picked up the most recent ISO as DKA200 (only bootable device).

Confirmed that suspicion (quoted to prevent wrapping):
> Shell> vms_bootmgr
8< snip 8<
> BOOTMGR> DEVICES
>
> BOOTABLE DEVICES (System Disks, Installation Kits, other):
>
> DKA200 (DVD) = FS1 UEFI: E9_2 OpenVMS: None 1263 MB SATA DVD
>
> BOOTMGR> BOOT
> Booting...
> %VMS_BOOTMGR-I-INSTALL, Booting an OpenVMS Installation Kit...
> 100%
>
> %%%%%%%%%%% VSI OpenVMS (tm) x86-64 %%%%%%%%%%%
>
>
> _______________________________________________
>
> GRAPHICAL OUTPUT HAS BEEN SUSPENDED
> USE A TERMINAL UTILITY FOR ACCESS
> _______________________________________________
>
> VSI Primary Kernel SYSBOOT Mar 8 2022 14:47:10
>
> %SYSBOOT-I-VMTYPE, Booting as a VirtualBox (tm) Guest
>
>
> VMS Software, Inc. OpenVMS (TM) x86_64 Operating System, E9.2
> Copyright 2022 VMS Software, Inc.
8< snip 8<
Couple of gotchas here.

But not suspect, only expected behaviour it seems.
Last edited by mgdaniel on Fri Apr 15, 2022 8:56 pm, edited 2 times in total.

Post Reply