[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1256.0. "Write lock error on TK50???" by NUTMEG::RYAN () Thu Aug 10 1989 11:27

    I've got a VAXstation 3100 running VMS V5.1-1 with 2 RZ23's, an
    RZ55, and an external TK50 tape drive (MKB500:).  I haqd a borrowed
    tape unit on it for a while to build the system and no problem.
    But I recently got my own unit in and sporadicaly I get the following
    when trying to init a tape:
    
    $ INIT MKB500: RZ55BK
    %INIT-F-WRITLCK, write lock error
      
    This is the device:
                             
    $ sh dev/fu mkb500:
                       
    Magtape OPAL$MKB500:, device type TK50, is online, file-oriented
    device, error logging is enabled.
                       
        Error count                    3    Operations completed   11647
        Owner process                 ""    Owner UIC         [0,0]
        Owner process ID        00000000   Dev Prot S:RWED,O:RWED,G:RWED,W:RWED
        Reference count                0   Default buffer size             2048
        Density             833 (normal)    Format       Normal-11             
                                        
                                                                    
      Volume status:  no-unload on dismount,beginning-of-tape,write-locked, 
    odd parity.
    
    
    No the tape is not write locked.  The only fix seems to be a reboot
    and that's not always successful.  Autoconfig from SYSGEN has no
    effect.                    
                               
    Anyone had this problem?  Feel free to brutally point me to the
    right conference if this is the wrong place to ask.
                               

    Thnx,
    Jim                               

T.RTitleUserPersonal
Name
DateLines
1256.1STAR::MCLEMANWhen all else fails,throw your mouse.Thu Aug 10 1989 12:597
    Sounds like you have a flakey write lock mechanism on the drive. Try a 
    different unit and see if you can replicate it. (also for most device
    related questions, you should ask in VMSNOTES or MICROVAX)
    
    Jeff