DataMuseum.dk

Presents historical artifacts from the history of:

Rational R1000/400 DFS Tapes

This is an automatic "excavation" of a thematic subset of
artifacts from Datamuseum.dk's BitArchive.

See our Wiki for more about Rational R1000/400 DFS Tapes

Excavated with: AutoArchaeologist - Free & Open Source Software.


top - download

⟦2689ccc97⟧ HLP, TextFile

    Length: 3098 (0xc1a)
    Types: HLP, TextFile
    Names: »RDM.HLP«

Derivation

└─⟦24d56d853⟧ Bits:30000744 8mm tape, Rational 1000, DFS, D_12_6_5 SEQ293
    └─ ⟦this⟧ »RDM.HLP« 
└─⟦9031b0687⟧ Bits:30000407 8mm tape, Rational 1000, DFS, D_12_7_3
    └─ ⟦this⟧ »RDM.HLP« 

TextFile

RDM

The RDM program is used to recover disk defect information from
new disks which have not yet been formatted.  Some disk manufacturers
place information about disk defects on the disk itself to allow
the disk formating process to be as automatic as possible.  The
RDM program uses features of the SL-121 controller to retrieve
this information.  To run the RDM program either boot it from tape
or invoke it by typing:

    CLI> x rdm

The RMD program will ask several questions as follows:

    Enter unit number of virgin disk :

Type the disk unit number as set on the disk drive itself.

    Enter HDA serial number as shown on HDA :

Enter the disk's HDA serial number.  Note that this is different from
the disk drive's serial number as defects are tracked by HDA, not drive.

    Enter the number of bytes-per-sector as jumpered at the disk :

This information is required to calculate the sector number in which
a given defect is located.  For the disks which Rational currently
uses the answer to this question is:

    Fujitsu 2351 (EAGLE)     585
    Fujitsu 2361 (XP)        620

The answer to this question is vital.  Neither the program nor the
controller can determine if the information you have provided is
correct.  An incorrect answer will result in incorrect mapping of
disk defect locations and may result is loss of user data and system
downtime at a future point in time.

The RDM program will then extract information about the disk from the
controller's EEPROM and display it on the console and ask:

    Is this information correct [Y] ?

If these values are incorrect for the disk to be used you must run
the SLEW program and changes the controller's EEPROM parameters before
you can recover the disks' defect information.

The RDM program will proceed to read the defect map from the disk
into memory.  If there are disk errors during the process the RDM
program will display information about the error and retry until
the defect information is recovered successfully.  If the defect
information is not legitimate the RDM program will inform you of
the error and terminate.  If the defect information is legitimate
the RDM program will display each defective block in terms of
cylinder, track, and sector.  When the entire disk has been processed
the program will display the total number of defects found.

Once the disk has been processed the RDM program will write the
defect information to either a DFS disk or MT format tape.  The
information will be placed in a file named:

    <hda-serial-number>.DEFECTS

This file is required to format a disk with the RECOVERY program.  Once
the disk has been formatted the defect information recovered with RDM
is no longer available.  The file generated by RDM is the only source
of this data and should be retained until the disk is no longer in
use.  The RDM program will ask about writing the defect information to
either a file or tape.  Answer the questions appropriately.  If the
RDM program was invoked from a disk it will terminate.  If it was
booted from tape it will restart; crash the machine to terminate it.