what is this means ?

[SCC_2]

I am very confuse with this Micro VaxII.
First the external hard drive (dub0:) have bad files/data maybe sharing with other files/date with in the same block and cause me can't login/bootup at all. Finally with all you people help, I using a tk50 tape (vms5.2, with standalone s/w inside it work, I build a standalone b/u tape using a micro Vax 3100 don't work) and I finally boot up the Vax. Since my hard drive is no good, I can't backup the data from it. Then I find another hard drive that contain system files and boot up overthere and it work but I can't login since I don't know the username/password that was set long time ago...lol.
later I use the mua0: to reboot the Vax again
now it don't work anymore it say
% execinit-f-error loading system file - syslicense exe r0 = 00000054

question # 2, if I go out and purchase another used micro vax same model. Can I just dump an image backup from the other working machine to it and it will work ?

Thanks !
SCC

[Uwe Zessin]

the error message for code %x54 is:
%SYSTEM-F-CTRLERR, fatal controller error

[Antoniov.]

If you purchase another MicroVax, you can restore all data.
SCC you live in Canada, too far from me. I've got and old MicroVax 3100 I don't use it; I'm afraid delivery cost is too expensive :-(

Antonio Vigliotti

[SCC_2]

Hello All,
I am looking getting another Used Vax for backup and the cost of it is pretty cheap and I am not worried about it.

Now, what I did on last fews day is.

I took out the ext. 8mm tape drive from another running system (3100 model 80) and put my bad (damage hard drive in) and when I boot up the system, I can see a new drive name call dka0: show up which is the bad hard drive I install.

And I have to mount it and call the label as sysdsk before I can access it, after I done all that I backup all my data (part by part, instead of using image backup, since I know the sysO: directory might have some bad block or file in it.

I found out that hard drive is write lock.
I was trying or testing see I can just install an old image backup vol:6 which have all system files for that hard drive. Since is write lock it will not allow me to write into it.

Is there any options or I have to erase the drive to start fresh again.

Thanks !
SCC

[Uwe Zessin]

It's possible that there is an error in the bitmap so the system write-locks as a precaution. Does the write-lock also appear if you mount the disk /FOREIGN ?

[SCC_2]

it don't allow me to mould the disk using
mount/fore dka0:
The only way to get in is mount it using
mount dka0:
volume sysdsk

Thanks !
Scc

[comarow]

There are two situations where we have seen multiply allocated blocks.

1: booting into a cluster with vaxcluster =0
2: third party defragmentors

$analyze/disk/repair will give you a choice,
but rarely can fix such a disk. The idea is since boots usuaually just write log files and such, there's a chance they weren't important files.

Make sure whatever caused it doesn't happen again.

Then restoration is almost always the only option.