[Info-vax] image backup on itanium

Stephen Hoffman seaohveh at hoffmanlabs.invalid
Sun May 3 14:45:23 EDT 2015


On 2015-05-03 18:26:36 +0000, David Froble said:

> Phillip Helbig (undress to reply) wrote:
>> In article <554524af$0$32302$c3e8da3$cc4fe22d at news.astraweb.com>, JF
>> Mezei <jfmezei.spamnot at vaxination.ca> writes:
>>>> Two different things.  BACKUP/IMAGE creates a disk which is LOGICALLY 
>>>> the same, i.e. at the Files-11 level.  It doesn't know about anything 
>>>> lower-level than that.
>>> BACKUP/IMAGE on that IA64 thing is aware of the lower level stuff
>>> because it is able to create the fake partitioning scheme at the very
>>> low disk blocks, and allocate a VMS file at the right disk blocks that
>>> happen to match where EFI sees the EFI partition on the disk.
>> 
>> But Hans said it didn't result in something bootable.
> 
> Two different things.
> 
> The disk was bootable ...
> 
> The bootstrap code didn't have the information to allow it to use the disk ...

Ayup.    The EFI boot alias was wrong.

While the mechanisms do differ, the same basic problem can happen on 
both Alpha and VAX.

In VAX-11 terms, the console CMD file from your VAX console storage 
device — DEFBOO.CMD or GENBOO.CMD or whatever you named it — didn't 
have the right device name embedded.

In Alpha terms, BOOTDEV_DEF might have been set to the wrong device, or 
there might have been an incorrect WWID embedded.

There are other examples.

None of which means that the system disk was not bootable.


-- 
Pure Personal Opinion | HoffmanLabs LLC




More information about the Info-vax mailing list