Re: Partitioned cluster question (reboot during lost quorum)

JF Mezei wrote:

So the gist of it is to set every node'S EXPECTED vote to ensure that
they cannot boot alone if disconnected from the ethernet. And manually
set it to "1" TEMPORARILY if you really need a node to boot alone/first
before allowing others to join.

Y'all are trying to get "creative" again, eh?

If you want to boot outside the cluster, then I tend to prefer to avoid enabling NISCS_LOAD_PEA0 and I don't load VAXCLUSTER.

(consider the case when a node is known
to have the valid copy of shadow disk members, so you want that one to
boot first and mount them first so they become source of future copy
operations isntead of targets).

Consider the last time this has happened, too. I've been at this for over a decade, and I can't recall ever having run into this case. As a rule, the node with the valid copy will have the highest instantiation, and will be the source for the shadow copy operation, or there have been other "creative" activities with the shadow set members. When you get (incautiously) "creative" with shadowing -- just like with the cluster vote-related system parameters -- you can end up corrupting a disk.

Assuming I could not simply take the other shadow set member disks off-line (which is what I try do when I get "creative" with shadow sets, in addition to managing the MSCPMOUNT.COM or startup procedures around the MOUNT operations), I'd confirm the bootstrap state, and I'd confirm that all other nodes are down (hard), and I'd then drop the EXPECTED_VOTES setting to match the local voting node's VOTES setting during conversational bootstrap, and I'd then (try to) remember to then clear WRITESYSPARAMS, and then and only then complete the bootstrap.
.

Relevant Pages

  • Re: Mounting disks during STARTUP
    ... >> member get automatically added to the shadow set at boot time. ... > few minutes for other disks in a shadow set to become available before ... > Waiting a couple minutes during boot saved a lot of processing time. ...
    (comp.os.vms)
  • Re: Shadowing question: NOMASTER
    ... >shadow reside in a disk array enclosure. ... >one at a time, and still have access to the shadow set, even it it's ... >created with only one member at boot time. ... shutdown Server 1 you are dissolving the Shadow Set. ...
    (comp.os.vms)
  • Re: DFO and SET FILE/NOMOVE
    ... >> system disk. ... In other words, one must boot from, for example, the boot ... MOUNT/OVER=SHADOW and reconstruct the shadow set later. ... What about shadow sets with members on more ...
    (comp.os.vms)
  • Re: Mbr messed up?
    ... > to boot again, got a blue screen error, crashed. ... The BIOS loads this bootstrap code. ... program reads the partition table to find out which partition is marked ... Parallel installs of various Windows versions should not touch the MBR ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Same system disk for multiple architectures ?
    ... bootblock issues except for one server that has to boot from a disk before it can start serving MOP requests? ... I'm not aware of any VAX, Alpha or Integrity systems that must boot from disk to boot from the network -- the closest analogs are the Itanium bootstrap from a disk image and the VAX bootstrap from the tape controller. ... and decode boot block --> find and load primary bootstrap into memory ...
    (comp.os.vms)