Conference msgaxp::optical

819.0. "rw551 hsd30 install v3.4" by CSC32::R_ROBERTSON () Tue Apr 01 1997 17:41

    
    I am having difficulty with a RW551 install on
    a HSD30 (v27d firmware) System is a Alpha 2100
    with Alpha vms v6.2 and OSMS v3.4.
    When  Laserstar is starting up it hangs after
    starting jkconfig and never gives a message
    starting jkconfig and never gives a message
    (I have not been able to dial into this system)
    
    On the HSD30 doing a show optical full we get
    opt310 d990 dec rwz53 (drive 1 is indeed set to id 1)
    opt320 d995 dec rwz53 (drive 2 is id 2)
    Show Loader full
    ldr300 dec rw551
    
    
    laserstar$startup has
    drives=($255$dka990,$255$dka995,jua0)
    
    JU$startup has
    jua0
    $255$dua999
    
    >>>show device  has
    dub990.4.100.8.0 $255$dka990 [drv009] RZ1
    dub995...........$255$dka995 [drv   ] RZ1
    dub999...........$255$dua999 [drv   ] HSX2
    
    $show dev dk and du showed the three devices
    but I do not remember their state I will
    check with the customer tommorow, but
    trying to do a mcr scsi inq to either
    jua0 or $255$dua999 failed with a timeout.
    
    I had the customer physically check the
    scsi id's on the jukebox. Juke is properly
    terminated.
    
    any ideas?
    
     Buffer: HATFIELD.MEATS                              | Write | Insert |
    Forward
    
    41 lines written to file DISK35:[R_ROBERTSON]HATFIELD.MEATS;1
    
    Tuborg $ type hatfield.meats
    
    I am having difficulty with a RW551 install on
    a HSD30 (v27d firmware) System is a Alpha 2100
    with Alpha vms v6.2 and OSMS v3.4.
    When  Laserstar is starting up it hangs after
    starting jkconfig and never gives a message
    (I have not been able to dial into this system)
    
    On the HSD30 doing a show optical full we get
    opt310 d990 dec rwz53 (drive 1 is indeed set to id 1)
    opt320 d995 dec rwz53 (drive 2 is id 2)
    Show Loader full
    ldr300 dec rw551
    
    
    laserstar$startup has
    drives=($255$dka990,$255$dka995,jua0)
    
    JU$startup has
    jua0
    $255$dua999
    
    >>>show device  has
    dub990.4.100.8.0 $255$dka990 [drv009] RZ1
    dub995...........$255$dka995 [drv   ] RZ1
    dub999...........$255$dua999 [drv   ] HSX2
    
    $show dev dk and du showed the three devices
    but I do not remember their state I will
    check with the customer tommorow, but
    trying to do a mcr scsi inq to either
    jua0 or $255$dua999 failed with a timeout.
    
    I had the customer physically check the
    scsi id's on the jukebox. Juke is properly
    terminated.
    
    any ideas?
    
    

    Robby,
    
    Sorry, but I don't see anything major to look for.  I would start
    with getting the JU device to respond to a SCSI MAP command.  It
    looks like a standard troubleshooting problem.
    
    Rob

    Should sysman have set exclude statements for dka and dua devices
    ie. io set exclude=(dka990,dka995,dua999) or
    should it have io set exclude=(dub,990,dub995,dub999)
    The reason I ask this is when the customer reads what he
    gets at >>> prompt the devices are referred to as:
    
    dub990.4.0.100.8.0 $255$dka990[drv009] rz1
    dub995............ $255$dka995[drv...] rz1
    dub999............ $255$dua999[drv...] hsx-2
    

    There should be no devices associated with the jukebox "excluded".
    The IO SET EXCLUDE only applies to direct connections not HSx
    connections.
    
    Rob