%BACKUP-W-GETBOOTERR, error reading boot information

[Andrew Chatfield_1]

Hi all,

Has anyone experienced the above warning durning an image backup of a shadow set?

Using OpwnVMS 8.2

Extract form the backup log file:
$ SHOW DEV D

Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA0: Mounted 0 ALPHASYS 31877370 486 1
DSA1: Mounted 0 DATADISK 14066115 119 1
$1$DKA0: (DS10) ShadowSetMember 0 (member of DSA1:)
$1$DKA100: (DS10) ShadowSetMember 0 (member of DSA1:)
$1$DKA200: (DS10) ShadowSetMember 0 (member of DSA0:)
$1$DKA300: (DS10) ShadowSetMember 0 (member of DSA0:)
$1$DQA0: (DS10) Offline 1
$1$DQA1: (DS10) Offline 1
$1$DQB0: (DS10) Online 0
$1$DQB1: (DS10) Offline 1
$1$DVA0: (DS10) Online 0
$ INIT BMS$DAT: BACKUP/MEDIA_FORMAT=COMPACT
$!
$ ON WARNING THEN CONTINUE
$ DISM $1$DKA100/NOUNLOAD
$ MOUNT $1$DKA100:/OVER=ID
%MOUNT-W-VOLSHDWMEM, mounting a shadow set member volume; volume write locked
%MOUNT-I-MOUNTED, DATADISK mounted on _$1$DKA100: (DS10)
$ BACKUP/NOLOG/IMAGE/LIST=DKA100.LIS DKA100: BMS$DAT:DKA100.BCK/SAVE -
/LABEL=BACKUP/IGNORE=(INTERLOCK,LABEL) -
/MEDIA_FORMAT=COMPACT/NOALIAS
%MOUNT-I-MOUNTED, BACKUP mounted on _DS10$MKB500:
%BACKUP-W-GETBOOTERR, error reading boot information
-NONAME-E-NOMSG, Message number 078EDE02
%BACKUP-W-GETBOOTERR, error reading boot information
-NONAME-E-NOMSG, Message number 078EDE02
$ DISM $1$DKA100/NOUNLOAD

The backup continues onto the other shadowset which also gets the same message and then seems to complete OK.

[Karl Rohwedder]

Andrew, pls. read HELP/MESS GETBOOTERR and check your bootblock.
Perhaps you have to rewrite it.

regards Kalle

[Daniel Fernandez Illan]

Andrew.
Disk DKA100 is a shadow set member. You can remount it using option /OVERRIDE=SHADOW_MEMBERSHIP and then execute BACKUP command.
Saludos.
Daniel.

[Karl Rohwedder]

A side note: When temp. dismounting a shadowset member for backup, you may use the /POLICY=MINICOPY feature. Using minicopy the remount into the shadowset will result in mucher shorter rebuild times.
And remember to shut down any application with open files prior to dismounting, else you could do as well do a BACKUP/IGNORE=INTERLOCK.

Regarding. MOUNT/OVERRIDE:
Since a backup would not write to the disk, a readonly mount should by o.k. ( An /OVERRIDE would make the use of MINICOPY impossible)

regards Kalle

[Volker Halle]

Andrew,

there is something wrong in BACKUP, 078EDE02 is not a valid 'accompanying message'.

You can try to check the bootblock information with:

$ setboot:==$sys$setboot
$ setboot -s -f $1$DKA100:

If you get the same error message on your DSA1: disk, is it also a bootable disk with an operating system on it ? Does DSA1:APB.EXE exist ?

Volker.

[Andrew Chatfield_1]

Thanks for you comments.

volker,

setboot -s -f $1$DKA100: returns
Boot Architecture : Unrecognized
setboot -s -f $1$DKA300: returns
Boot Architecture : Alpha
Boot Address : 0x01162f29 : 000018231081
Boot Size : 0x00000490 : 000000001168

DKA0 is the only disk with an operating system installed so I guess DKA100 would not contain any boot information however DKA300 also returns the same error.

[Volker Halle]

Andrew,

have you installed the VMS82A_BACKUP-V0100 patch or any VMS82A_UPDATE kit ?

Not that the release notes have to say anything about this error message, but you never know...

What does $ ANAL/IMA/SELEC=LINK SYS$SYSTEM:BACKUP.EXE report ?

Volker.

[Volker Halle]

Andrew,

did you try without the /NOALIAS qualifier ?

Volker.

[Guenther Froehlin · Accepted solution]

$ SET MESSAGE SYS$MESSAGE:EFI$MSG.EXE
$ EXIT %X078EDE02
%EFI-E-NOBOOACC, no bootblock access is available

In the sources it hides the true error and returns this if there was problem accessing [000000]GPT.SYS and [000000]INDEXF.SYS. Looks like a bug if SYS$SHARE:SYS$SETBOOTSHR.EXE which is from the VMS facility EFI.

It seems like LOG_IO privilege is need to avoid that bug and the EFI message.

Also a buglet that the EFI message text is not presented with the BACKUP message.

/Guenther