Search Text         
Search Tips?
Search By   And   Or   Boolean   Exact Match   TA #
Search In   Whole Doc   Keywords Sort By  
Product   Sub Product  

View Technical Articles (sorted by Product) New/Updated in the last:    7 days      14 days      30 days             
TA # Date Created Date Updated Resolved Issue?   Printer Friendly Version of This TA   Print Article
  E-mail This TA   E-mail Article
104978 01/29/1996 05:57 PM 10/24/2002 05:20 PM
Yes No
idmkreg reports "error updating space.c for Stp" when the kernel is relinking.
Keywords
openserver osr5 v5 5.0.0 idmkreg error updating space.s for Stp kernel link_unix remove revert scsi tape dat driver device.dat space.c space.h mscsi Stp Stp0 Stp_tape_cfg gen_Stp_route mkdev link error 5.0.2 5.0.4 5.0.5 5.0.6 502 504 505 506
Release
SCO OpenServer Enterprise System Release 5.0.5, 5.0.6
SCO OpenServer Desktop System Release 5.0.5, 5.0.6
SCO OpenServer Host System Release 5.0.5, 5.0.6
SCO OpenServer Enterprise System Release 5.0.0, 5.0.2, 5.0.4
SCO OpenServer Host System Release 5.0.0, 5.0.2, 5.0.4
SCO OpenServer Desktop System Release 5.0.0, 5.0.2, 5.0.4

Problem
          I have configured a number of SCSI tapes using the mkdev(ADM)
          command.  When I relink the kernel, this message is displayed:

                idmkreg : error updating space.c for Stp

          I have tried removing all of the tape devices, again using
          mkdev(ADM).  When I view the current SCSI tape configuration
          using this utility, it indicates that there are no longer any
          SCSI tape devices configured.  However, this did not prevent
          the error message from being reported when I once again tried
          to relink the kernel.


Solution
          The system's tape configuration has become corrupt.

          The following steps detail how to correct this inconsistency by
          removing all additional tape devices from the kernel configuration
          files leaving just the necessary configuration for the Stp0 device
          (scsitape(HW)).

          When you have one tape drive configured, check and modify these
          files as follows:

          * /etc/conf/pack.d/Stp/device.dat

          Remove all other Stp entries leaving just the Stp0 one. The
          Stp0 entry should look like this:

          Stp0:
                  INDEX=Stp0
                  PATH=node0,node1
                  node0=D_SUBSYS,SCSI Tape,0,D_TAPE_SUBSYS,,NULL
                  node1=D_UNIT,Drive 0,0,0,D_REMOVABLE D_NODE,NULL
                  D_USER_MSG=SCSI Tape Drive,8,0,,NULL
                  D_REWIND_NODE = 0
                  D_CTL_NODE = 128
                  D_NOREWIND_NODE = 8


          * /etc/conf/pack.d/Stp/space.c

          The "#define Stp0 0" in this file should read "#define Stp0 68608".


          * /etc/conf/pack.d/Stp/space.h

          Remove the necessary elements in the Stp_tape_cfg array to leave
          just one gen_Stp_route element.


          * /etc/conf/cf.d/mscsi

          Insert an appropriate entry here for your first tape device, for
          example:

                *ha     attach  number  ID      lun     bus
                arad    Stp     0       2       0       0

          Note: Specify the driver name for your SCSI host adapter in the
          first field. In this example, the Adaptec AIC-7770 Host Adapter
          driver "arad" is being used.


          * /etc/conf/sdevice.d/Stp

          Ensure that only one Stp line exists in this file and that it looks
          like:

                Stp    Y    1    0    0    0    0    0    0    0

          Remove any additional lines of this type, if there are any.


          Also, you should remove all of the device nodes associated with
          tape devices in the /dev directory, for example:

                /dev/rStp*
                /dev/nrStp*
                /dev/xStp*

                /dev/rct*
                /dev/erct*
                /dev/nrct*
                /dev/xct*

          The necessary tape device nodes will then be re-created once
          the kernel has been relinked, and the environment re-created.
          (As a backup precaution, you may wish to archive these device
          nodes to a file by using the cpio(C) utility before you remove
          them.)

          This should now allow the kernel to be relinked and the kernel
          environment re-created with just one SCSI tape configured.
          Subsequent kernel device configuration can now be resumed.



Related Articles
•  Recover OpenServer 5 root filesystem after crash if backups, boot/root exist.
•  I've installed my system and now I need to know about configuring it.
•  I changed system locale and now the calendar server does not start.
•  I get "Error UX: ld: Error: 'objectfile'.o: fatal error: cannot link OpenServer object into Intel iABI target" when trying to compile with C++ binary.
•  What is SLS OSS623A, the SMP Supplement for SCO OpenServer Release 5.0.5 and 5.0.4?
Back to Search ResultsBack to Search Results