what is this means ?

[SCC_2]

While reboot there is a message show on screen
%RBLD-W-DUALLOC, DUAL ALLOCATION ON VOLUME 1
it sit there for a min or more. How long I have to wait.
Thanks !
SCC

[Uwe Zessin · Accepted solution]

Outch! Your disk is badly corrupted!

It means that two or more files are sharing at least on data block (cluster).

An ANALYZE/DISK_STRUCTURE should report this, but of course it does not know to which file the data belongs.

[SCC_2]

holly that bad, is there anyway I can get back to the system at least it show me a $ sign ?
SCC

[Uwe Zessin]

You can try to disable the automatic system disk rebuild like I have writen in your other thread (ACP_REBUILDSYSD=0). But, honestly, it looks like you disk's structure is really, really badly corrupted and I would not try to recover from it. In my opinion it's a waste of time. Some other data blocks might have been overwritten and you might not find out of they are not doubly mapped.

[SCC_2]

Hello,
at >>> acp_rebuildsysd=0, no go
?17 ILL CMD
SCC

[Uwe Zessin]

Sorry, but you need to do a conversational boot first. It sounds like you are on a VAX system. Assuming that you boot from root [SYS0] (you can check that with:

>>> SHOW BFLG
or
>>> SHOW BFLAG

depending on model) I would do this first:

>>> BOOT/R5:1

The system should then respond with:
SYSBOOT>

where you enter:
SYSBOOT> SET ACP_REBLDSYSD 0
SYSBOOT> EXIT

[SCC_2]

Hello,
What a bad day, I don't know who setup this system. The boot was default to dua0: which is not excess. I try to set boot to dub0: which the disk have error on it and no go.
I try boot/r5:1 the system trying point at dua0: it will not work since there is no drive under this name. I have a complete images backup how can i install it, since I can't get to the $ sign.

type show boot error ?18 inv dgt, try all method you recommand just can't get to the sys$boot >
SCC

[Uwe Zessin]

I'm truly sorry for all the mess you are going through, but treat it as a great learning experience and I'm sure you feel a bit better.

You can usually override the boot device with:
>>> boot/R5:1 DUB0

I wonder, what system are you working with? Model number? The error message looks like from a MicroVAX II. If I recall correctly, this is a system with a so-called 'sniffer boot' which tries a fixed set of devices in a fixed order and you cannot set a default boot device.

It might be possible to set the system not to automatically boot after power on so that you can choose the boot devicve.

[SCC_2]

finally using the boot/r5:1 dub0 I can get to the sysboot> and i follow the bypass startup and login procedures
sysboot> set/startup opa0:
continue
it show vax/vms v5.2....
it try to access my bad disk again
my lord... what else can I try
SCC

[SCC_2]

yes, you are right the system is a micro vax II and they updated it call micro vax 3900 with a micro vax II case (box).
SCC

[SCC_2]

The file must be bad within the bootup version 5.2, the system can't boot up after I get the sys$boot show up

>>> b/r5:1 dub0
sysboot> set acp_rebldsysd 0
sysboot > exit
vax/vms version v5.2 major versio id = 1 minor version id = 0
and it sit there hrs, no respone.
I need to get back to the $ sign somehow to run the backup/restore the file.
Any idea how to do that ?
SCC

[Ian Miller.]

You need to boot from standalone backup - probably from another disk, tape or CD.

from a disk or CD
BOOT/R5:E0000000 DUxx

from tape (if you have standalone backup kit on tape)
BOOT MUxx

you will be prompted to enter the date and time then get a $ prompt at which you can only perform BACKUP commands.

Ideally restore the whole disk as it looks like the file structure is corrupt.

If you have a later VMS CD then parhaps an attempt to repair could be tried.

[SCC_2]

Don't know is the tape (td50) is too old or what. boot/r5:e0000000 mua0 (I heard the tape drive spinning back and forward)then
error come back sayinng ?4d devoffline, mua0
? o6 hlt inst
pc = 00800e0a failure.

I have another mirovax 3100 model 80 running, using v5.5 instead of V5.2, I guest I can build another standalone tape on that VAx and use it over here, Can I ?, even the Vms version are not the same.
Thanks !
SCC

[Ian Miller.]

to build a tape on your V5.5 system do
@SYS$UPDATE:STABACKIT MUA0:

[Volker Halle]

SCC,

you shouldn't specify the system root when booting from tape, just:

>>> B MUA0

should be sufficient.

And yes, you can built a standalone backup tape on another node (and VMS version) to be booted on your system:

$ @SYS$UPDATE:STABACKIT MUAn:

Volker.

[SCC_2]

Thanks, I will try that. But I am very sure that tape must be old.
SCC

[SCC_2]

My system was running under vms v5.2 and the standalone tape doesn't work maybe is too old. I create another standalone tape on another Vax it run under vms V5.5. I insert the standalone on v5.5 hope it will boot up my system( the dead one) but there is an error message % sysboot-f-unexpected machine check and bring me back to >>>.
Is there anyway I can by pass this.
Thanks !
SCC

[SCC_2]

at per perv. at the end of the error line
it say
?05 dbl err.
SCC

[Volker Halle]

SCC,

too bad, this looks like a CPU/memory error on your V5.2 system. DBL ERR is a double error, i.e. another HW error occured while handling a hardware error. The CPU then just halts.

To really make sure, that your SA-backup tape is o.k., try to boot it on your V5.5 system.

Volker.

[SCC_2]

I can't shutdown the other Vax at this point, Since other users is using it at business hour, I am going to make another standalone tape see it will work or not.

Is there another other option I can get try.

Thanks !

SCC

[SCC_2]

I make another tape, Have the same error. I can't see is the tape problem. When I shutdown and power up the Vax is go thru the KA630-a.v1.2 performing normal system tests 7..6..5..4..3..
tests completed
>>>

The system should be fine right ?

then I boot it

>>> b mua0

3..2..1..

the disk drive spinning then the error show.

I make up the tape using a micro 3100 model 80 with a tz30 drive to make up the tape. and insert the tape into a tk50 drive running on a micro vax II

what will go wrong.

thanks !
SCC

[Volker Halle]

SCC,

don't assume, that selftests will find all HW problems.

You can find a description of the available console commands and CPU errors on:

http://hampage.hu/dr/ka630.html

Maybe try the various >>> TEST [test-number] commands to try to isolate the problem.

Did the tape move at all, before the error happened ? BTW, which error happened this time ?

Volker.

[SCC_2]

Hello,
I use the standalone backup (tk50) that I build using the other Vax is not working, Finally I use the vms5.2 2of 2 that have standalone on it and it work. At least I can get into the $ sign. Not I am facing another problem. I try to backup the data on that bad drive and I have an error saying pool expansion failure.
There is a very good chance I have to send this disk drive out and let someone to recover the data for me.
SCC

[Jeroen Hartgers_3]

Do you have the possebility to swap disks.
If so you could remove the damaged system disk. Put in a empty slot of the other vax and maak a image backup af the disk and init the damaged disk.
Roll back a image backup you know its right. Swap the disk back to the original vax and try to boot normaly.

[SCC_2]

hello Jereon,
This is what I try to do, I have some other Dec drive hook it up. But don't know why when boot up from the standalone that drive should be dua0 but not show up, only the mua0 and dub0 (the damage one) on screen.

My next step is to take the damage drive and install to my other Vax that was running and see I can access it.
Thanks !
SCC