Free 14-Day Evaluations    
Product Downloads    

Sign in     


DESKTOP MOBILE DOWNLOAD PURCHASE SUPPORT INFO COMPANY
 Home  >>  Support  >>  UNIX Technical Support

Checking for Bad Media in Unix

Question: I can't seem to set my machine to read the media TERM came on. Could it be bad media?

Answer: Do the following:

  1. Verify that the correct extraction command is being used. Double-check your release notes.

  2. Verify that the correct device name is being used for the media being read. if you are unsure of the device name and it is not listed in the Installation and Set up of Term section in the manual, you can search for the correct device name by inserting the release media in the appropriate drive and type in the following at a system prompt:

    # for x in `ls /dev/rfd*` (use the tick character, not the single quote)

    > do >

    echo "Device: $x "

    > tar xvf $x

    > done

    #

    This will cause the tar command to be used on all the selected devices until the correct one is found. In order for this to work correctly, you must loop through the right files and directory. An example of some directory specifications are as follows:

    Interactive UNIX system V/386 /dev/rdsk/* (disks)

    SCO XENIX/UNlX /dev/rfd* (disks)

    Sun Microsystems /dev/rst/* (CT)

    ICL DRS /dev/rmt/* (CT)

    Currently, Century Software provides its UNIX releases on the following formats:

    Tan 5.25 Diskette: 360K

    Black 5.25 Diskette: 1.2M

    Black 3.5- Diskette: 720K

    Black 3.5- Diskette: 1.44M

    Cartridge Tape: Low density

  3. Remove media, re-insert and try again.

  4. If the release has multiple diskettes, try executing the extraction command on each diskette received. lf all diskettes fail, reboot the system and repeat steps 1 through 4. Occasionally, UNIX drives can get messed up and require rebooting to correct. lf only one diskette fails, it is an indication that the diskette is bad. Call Century Software Customer Support.

  5. lf all diskettes fail again, try using a non-Century Software diskette. lf it fails to read, the diskette drive probably requires cleaning. lf the non-Century Software disk works, the TERM product diskettes are damaged. Call Century Software Customer Support.

    Cartridge Tapes: lf you are having problems reading a cartridge tape, follow the steps above. lf the above steps fall, be sure to use the blocking option with the tar command. Century Software's tapes are usually written with a block size of 20. For example:

    tar xvfb /dev/rct0 20

    lf adding the block size option doesn't help, try using the dd command as follows:

    dd if = /dev/ < device > | tar xvf -

    lf this command doesn't work, try:

    dd if = /dev/ < device > conv = swab | tar xvf -

    The first command does a data dump and pipes it through tar. The second command does a data dump, byte swaps the files and pipes it through tar. Some tape drives (i.e. NCR towers) do byte swapping when reading and/or writing tapes. If the above fails, it is probably due to bad media. Contact Century Software Customer Support.

    This will cause the tar command to be used on all the selected devices until the correct one is found. In order for this to work correctly, you must loop through the right files and directory. An example of some directory specifications are as follows:

    Interactive UNIX system V/386 /dev/rdsk/* (disks)

    SCO XENIX/UNlX /dev/rfd* (disks)

    Sun Microsystems /dev/rst/* (CT)

    ICL DRS /dev/rmt/* (CT)

    Currently, Century Software provides its UNIX releases on the following formats:

    Tan 5.25 Diskette: 360K

    Black 5.25 Diskette: 1.2M

    Black 3.5- Diskette: 720K

    Black 3.5- Diskette: 1.44M

    Cartridge Tape: Low density

  6. Remove media, re-insert and try again.

  7. If the release has multiple diskettes, try executing the extraction command on each diskette received. lf all diskettes fail, reboot the system and repeat steps 1 through 4. Occasionally, UNIX drives can get messed up and require rebooting to correct. lf only one diskette fails, it is an indication that the diskette is bad. Call Century Software Customer Support.

  8. lf all diskettes fail again, try using a non-Century Software diskette. lf it fails to read, the diskette drive probably requires cleaning. lf the non-Century Software disk works, the TERM product diskettes are damaged. Call Century Software Customer Support.

    Cartridge Tapes: lf you are having problems reading a cartridge tape, follow the steps above. lf the above steps fall, be sure to use the blocking option with the tar command. Century Software's tapes are usually written with a block size of 20. For example:

    tar xvfb /dev/rct0 20

    lf adding the block size option doesn't help, try using the dd command as follows:

    dd if = /dev/ < device > | tar xvf -

    lf this command doesn't work, try:

    dd if = /dev/ < device > conv = swab | tar xvf -

    The first command does a data dump and pipes it through tar. The second command does a data dump, byte swaps the files and pipes it through tar. Some tape drives (i.e. NCR towers) do byte swapping when reading and/or writing tapes. If the above fails, it is probably due to bad media. Contact Century Software Customer Support.


  Copyright © 2019 Century Software, Inc. All Rights Reserved  TERMS OF USE PRIVACY POLICY EULA