[Info-vax] Problems restoring image-backup

jouk joukj at hrem.nano.tudelft.nl
Tue Jun 28 11:00:20 EDT 2016


On 28/06/16 16:32, Stephen Hoffman wrote:
> On 2016-06-28 11:38:50 +0000, jouk said:
> 
>> Today my alpha's system disk crashed. So I tried on an itanium to
>> prepare for a new disk from a backup-saveset:
>>
>>  backup/ima/log DISK1_240616.BCK/sav $1$DGA113:
>>
>> The save set was also created using /image. This command seems to
>> finish normally.
>> I took the disk out of the Itanium and into the Alpha.
> 
> Tell the SET BOOTBLOCK command or the sys$setboot tool to write an Alpha
> bootbilock.  The default is to write the architecture-local boot block.
> 
>> Here it complains when booting that it does not contain a bootblock.
> 
> What does the following tell you about the boot structures on the target
> disk?
> 
> $ sb :== $sys$setboot
> $ sb  -f ddcu: -s
> 
> where ddcu: is the target (restored backup) disk.


$ sb  -f dka100: -s

%EFI-E-NOTMOUNTED, target volume is not mounted or not ready
-EFI-I-SBTRG, seeking:
-EFI-I-SBDEF, default: [000000]SYS$ISO9960.SYS

>> If I boot from CD, I cannot mount the device because it seems not to
>> caontain a files-11 homeblock.
> 
> The primary home block was made optional at V8.0, and current Alpha
> should be able to deal with that.  If you're running an older OpenVMS
> release, it won't.  I'd expect this to work on V8.4.
> 
It is OpenVMS 8.4.
If I try to mount I get:

$ mount/over=(id,lim) dka100

%MOUNT-F-NOHOMEBLK, Files-11 home block not found on volume
-MOUNT-I-VOLIDENT, label = '............', owner = '............',
format = '...
.........'






More information about the Info-vax mailing list