BL860c i2 boot problem

[The Brit]

Try the following sequence.

1. Boot from the Distribution CD.
2. Go DCL commands.

$$$ Show Device dga
[make sure you can see the device you want to boot from]

$$$ set boot
$$$ @sys$manager:boot_options
[set up the boot option normally, when it asks for the device name enter ?, and then type in the device name exactly as it appears in the list.]
[once the boot option is set up, select option 5, (validate), and let it validate all boot options in the list.]
[if all of the options validate OK, then try shutdown and boot normally from new SAN disk.]

Can you cut and paste the whole session and attach it so that we can see what you see.

Dave.

[Ana M. García Olivencia]

I have a problem with the 'SET' command:
NOTE: I have booted from a SAN disk /DGA6484) with a copy of the OpenVMS distribution CD.
.....
Enter CHOICE or ? for help: (1/2/3/4/5/6/7/8/9/?) 8



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 ",
and you will be returned to the menu.

$$$ sh dev d

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DAD0: Online 0
$1$DGA1: () Online 0
$1$DGA2: () Online 0
$1$DGA3: () Online 0
$1$DGA4: () Online 0
$1$DGA5: () Online 0
$1$DGA6: () Online 0
$1$DGA7: () Online 0
$1$DGA8: () Online 0
$1$DGA9: () Online 0
$1$DGA6484: () Mounted wrtlck 0 I64084 1770316 50 1
$$$ set boot $1$DGA1:
%EFI-E-BADPARAM, bad parameter

$$$
.....


It's curious that, although the documentation says that you must use the 'BOOT_OPTIONS' procedure with the operating system started to define the SAN boot disks and not the efi maintenance menu, this last one is the only one that works.

If I compare two entries at the boot menu, one that works and the other one not working, the difference is:


WORKING (defined from the maintenance manager menu)
Boot0015
PcieRoot(0x30304352)/Pci(0x5,0x0)/Pci(0x0,0x0)/Fibre(0x50001FE150244799,0x1000000000000)/HD(1,GPT,E7DBA961-56EF-11E0-B039-AA000400FEFF)/\EFI\VMS\VMS_LOADER.EFI

NOTWORKING (from BOOT_OPTIONS.COM)
DGA1 -BOOT COMPLETO- OpenVMS 8.4
FGA0.5000-1FE1-5024-4799
PcieRoot(0x4D1A055)/Pci(0x5,0x0)/Pci(0x0,0x0)/Fibre(0x50001FE150244799,0x1000000000000)/HD(1,GPT,E7DBA961-56EF-11E0-B039-AA000400FEFF)/\efi\vms\vms_loader.efi

The differences are the capital letter at the loader file and the strings 0x30304352 and 0x4D1A055.


Any other ideas or tries?

Thanks in advance.

Ana

[The Brit]

My mistake, I forgot one small detail, you need to mount the target disk before you can run the "set boot" command.

example:

SYSTEM>> show dev dka

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
$100$DKA100: (TABBUD) Online 0
$100$DKA200: (TABBUD) Online 0
SYSTEM>> set boot $100$dka100:
%EFI-E-BADPARAM, bad parameter
SYSTEM>> set boot $100$dka100
%EFI-E-BADPARAM, bad parameter

Now MOUNT the Disk

SYSTEM>> mount/over=id $100$dka100:
%MOUNT-I-MOUNTED, System_14Jan mounted on _$100$DKA100: (TABBUD)
SYSTEM>> set boot $100$dka100:
SYSTEM>>

After executing the "set boot", run "BOOT_OPTIONS" to create the boot entry, and also "VALIDATE" the new entries.

Good Luck,

Dave.

[Domen Setar]

Hi Ana,

In my case ths sollution was very easy. I have to install latest UPDATE patch on the OpenVMS. After that everything works fine.

Regards

Domen

[Domen Setar]

Install latest UPDATE patch on OpenVMS.

[Ana M. García Olivencia]

Thanks all for your help.

Regards.

Ana

[Tom O'Toole]

Same problem here. The distribution for 8.4 crates worthless boot_options (with i2 blades, at least). It's not that easy to install the latest update, considering you can't boot.

Also the console is very slow.

[Domen Setar]

Hi Tom,

You can boot. But you must use EFI shell to manually enter your boot command. After booting system (and network) works normal.
I also noticed slow response at the console.
But somehow the issue was solved by installing latest update.

Regards

Domen