need help with a ds25 that is bug checking

[Karen Lee_3]

I made a change to modparams that seems to be preventing my server from booting - i'm on the road and don't have my system manuals.

how do i start a minimal boot and remove the offending shadow_sys_disk 1 from my sysgen params?

[Robert Gezelter]

Karen,

Use a conversational boot.

You will be prompted by a "SYSBOOT>". You can then make changes to the parameters and continue the boot.

The command option on the SRM BOOT command is either -fl 0,1 or -fl 1,0. I always mix it up and I don't have a console or the manual within reach at this instant.

- Bob Gezelter, http://www.rlgsc.com

[EdgarZamora_1]

I just mixed that up yesterday. The correct flag would be -fl 0,1 (assuming your root is 0).

E

[Karen Lee_3]

well i was going it right all along - but when i set -fl 0,1 i get the following

P00>>>show bootdef_dev
bootdef_dev dkb0.0.0.1.2
P00>>>set bootdef_dev -fl 0,1
device -fl is invalid
device 0 is invalid
device 1 is invalid

[Robert Gezelter]

Karen,

I would not set this parameter permanently, I would use the option on the BOOT command directly.

- Bob Gezelter, http://www.rlgsc.com

[Karen Lee_3]

you're right - i'm sitting in an airport trying to remember my vms commands

i did a boot -fl 0,1 and it came up to the boot prompt - can i modify and shadow disk sysgen parm from here?

[Karen Lee_3]

well it won't even boot minimally - i still get the bug check

at the sysboot> set startup_p1 "MIN"
sysboot> cont


I am trying to boot from the CD - looks like it's coming up - can i change the parameter using a boot from the cd?

[Robert Gezelter · Accepted solution]

Karen,

There is separate parameter for the BOOTFLAGS, it is not part of the device specification.

There is a command in the SRM console has a SHOW command, and the resulting display is fairly clear.

A cationary note: The parameters are used by name, there is no check against misspelling or wrong names, the parameter will just not work.

- Bob Gezelter, http://www.rlgsc.com

[Jan van den Ende]

Karen,

obviously dkbo is your intended boot device, so
>>> boot dkb0 -fl 0,1


should get you into
SYSBOOT>
you type SET SHADOW_SYS_DISK 0
c

I assume from there you can find your way again.

You can afterward set bootdef_def & boot_osflags at a more convinient time.

Success!

Proost.

Have one on me.

jpe

[Robert Gezelter]

Karen,

In your situation, I would not use the parameters, I would issue the BOOT command manually:

>>> boot -fl 0,1 dka0

- Bob Gezelter, http://www.rlgsc.com

[Andy Bustamante]

Another option is to boot from the operating system CD, mount your system disk and using sysman updating the ALPHAVMSSYS.PAR on the boot disk.


$ mount dkb100: /over=ident
$ mc sysgen
> use dkb100:[sys0.sysexe]ALPHAVMSSYS.PAR
> set <>
> write dkb100:[sys0.sysexe]ALPHAVMSSYS.PAR
> exit

Assumming a boot disk of dkb100 and root of 0.


Andy


"There are 9 and 60 ways of constructing tribal lays, and every single one of them is right."

[Volker Halle]

Karen,

it may be much too late for this answer, but if you assume your current ALPHAVMSSYS.PAR system parameter file is bad, you can always revert to the previous one, if you have done your parameter changes using @AUTOGEN.

AUTOGEN (see SYS$SYSTEM:SETPARAMS.DAT) always saves the old parameters in a file called sys$system:alphavmssys.old, so you can:

>>> B -fl 0,1 ! when 0 is your system root
SYSBOOT> use alphavmssys.old
SYSBOOT> C

Volker.

[Karen Lee_3]

There were so many issues with the OS - that I finally decided to just start over again - I already had the CD loaded - it came back fine - i'll just re-do the system disk shadow.

thanks for all your help

[Karen Lee_3]

well I completely rebuilt my system disk today to get rid of the bug check. I carefully went thru the shadowing instructions again - ran autogen - i it bugcheck again -

i was able to boot using your geat advice - about alphavmssys.old - save me - but now i need to figure out why it bug checks.

[Ian Miller.]

post the CLUE file from SYS$ERRORLOG here.

[Volker Halle]

Karen,

the most popular bugcheck when setting up shadowing for the first time is a when you forget to set up a non-zero allocation class for the system (ALLOCLASS=0).

Other than that, please supply the CLUE file (see CLUE$COLLECT:CLUE$node_ddmmyy_hhmm.LIS)

Volker.

[Karen Lee_3]

Alloclass was the issue - that you all for your timely assistance - i'm in europe trying to get this server up - limited access to tech support - so you guys are a great help.