Conference mvblab::sable

2598.0. "Cant write dump if disk preferred to differnt controller" by CX3PST::CSC32::J_BECKER (There's no substitute for a good boot) Thu May 15 1997 01:39

              <<< VAXAXP::NOTES$:[NOTES$LIBRARY]VMSNOTES.NOTE;1 >>>
               -< VAX and Alpha VMS - Digital Internal Use Only >-
================================================================================
Note 598.0       Cant dump to disk if preferred to another path       No replies
CSC32::CSC32::J_BECKER "There's no substitute for a" 49 lines  15-MAY-1997 00:26
--------------------------------------------------------------------------------
    Customer has a three node 2100 cluster.  They boot from a disk on a
    dual redundant hsd30 disk.  After booting they may prefer the disk to
    the other controller as a load balancing exercise.  The system may
    crash at that point and it fails to write the dump.  The problem
    appears to be the dump code wants to write to the original boot path.  The
    code tries to bring the drive on line to that controller and fails. 
    Would the dump_dev variable (which is currently null) help here?
    
    vms 6.2, console 4.2  Two kfesb, one for each dssi path to the dual
    redundant hsd30's.  The original bugcheck reason was resolved.  We need
    to find out what happened to the dump code and if there is a way to
    get the dump code to find all possible paths.
    
    john becker
    csc
    cross posted in sable notesfile
    -----------------
    
    
    
     device dub0.3.0.6.1 no longer valid            lost a path to system disk!!
     device dub0.3.0.6.1 no longer valid
     device dub0.3.0.6.1 no longer valid
     device dub0.3.0.6.1 no longer valid
    
     cb_open: failed MSCP 1 6 0 3 0 0 0 DU 420011033938 HSD2, dub0.3.0.6.1
    
     **** Boot driver initialization routine returned failure = 00000084
                                                                    ^^^^
                                                            device off line
    
    **** OpenVMS (TM) Alpha Operating System V6.2     - BUGCHECK ****
    .
    .
    .
       SYS$BASE_IMAGE.EXE
           Nonpaged read only               80002000 8000D400
           Nonpaged read/write              89D84200 89DA1400
       SYS$PUBLIC_VECTORS.EXE
           Nonpaged read only               80000000 80001600
           Nonpaged read/write              89D80000 89D84200
    
     **** Memory dump canceled. IOVector = 00000000, Flags = 02016874
    
     halted CPU 0
    
    
    
                                   
    

If you put a list in dump_dev, then each device would be tried until
the dump can be written, or until the end of the list.