[Info-vax] Configured shadowing, neglected to update satellite.. Can't figure out how to fix.

[cyberdefensedave at gmail.com]

So I've now resolved all of my Decnet issues and just set up volume shadowing for my boot node.  Unfortunately, I neglected to reconfigure the satellite before getting the boot node up and running again.

The satellite now reports that it cannot mount it's boot volume.  The error reported is:

$ write sys$output F$message(%x728334)
%MOUNT-F-DEVSHAMEM, device is already mounted as a shadow set member

Research seems to reveal that this is because I have failed to set up the satellite node to support shadowing.  Using SYSGEN I did the following:

$ mcr sysgen
SYSGEN>  USE DSA0:[SYS11.SYSEXE]VAXVMSSYS.PAR
SYSGEN>  SET ALLOCLASS 2
SYSGEN>  SET SHADOW_SYS_DISK 0
SYSGEN>  SET SHADOW_SYS_UNIT 0
SYSGEN>  SET SHADOWING 2
SYSGEN>  WRITE DSA0:[SYS11.SYSEXE]VAXVMSSYS.PAR

Rebooting the satellite, it still fails to mount the volume.  Conversational boot at the SYSBOOT prompt reveals that all of these settings appear to be configured, though the "SHADOW_SYS_DISK" reports that while it is set to zero, the maximum value is -1.  Not sure what to make of that.

I can't seem to figure out how to proceed from this point to get the satellite functioning again.  Interestingly, the local volume on the satellite still mounts into the cluster (Wow!) even though the satellite will not continue booting.

What am I missing here?

Thanks!