Annotation of 43BSDTahoe/man/man8/vax/drtest.8, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1983 Regents of the University of California.
                      2: .\" All rights reserved.  The Berkeley software License Agreement
                      3: .\" specifies the terms and conditions for redistribution.
                      4: .\"
                      5: .\"    @(#)drtest.8    6.2 (Berkeley) 5/19/86
                      6: .\"
                      7: .TH DRTEST 8 "May 19, 1986"
                      8: .UC 5
                      9: .SH NAME
                     10: drtest \- standalone disk test program
                     11: .SH DESCRIPTION
                     12: .PP
                     13: .I Drtest
                     14: is a standalone program used to read a disk 
                     15: track by track. 
                     16: It was primarily intended as a test program 
                     17: for new standalone drivers, but has shown
                     18: useful in other contexts as well, such as 
                     19: verifying disks and running speed
                     20: tests. For example, when a disk has been formatted
                     21: (by format(8)), you can check that
                     22: hard errors has been taken care of by running 
                     23: .IR drtest .
                     24: No hard errors should be found, but in many cases 
                     25: quite a few soft ECC errors will be reported.
                     26: .PP
                     27: While
                     28: .I drtest
                     29: is running, the cylinder number is printed on
                     30: the console for every 10th cylinder read.
                     31: .SH EXAMPLE
                     32: A sample run of 
                     33: .I drtest
                     34: is shown below.  
                     35: In this example (using a 750), 
                     36: .I drtest
                     37: is loaded from the root file system;
                     38: usually it
                     39: will be loaded from the machine's
                     40: console storage device.  Boldface means user input.
                     41: As usual, ``#'' and ``@'' may be used to edit input.
                     42: .nf
                     43: .in +5
                     44: .sp 1
                     45: >>>\fBB/3\fR
                     46: %%
                     47: loading hk(0,0)boot 
                     48: Boot
                     49: : \fBhk(0,0)drtest\fR
                     50: Test program for stand-alone up and hp driver
                     51: .sp 1
                     52: Debugging level (1=bse, 2=ecc, 3=bse+ecc)?
                     53: Enter disk name [type(adapter,unit), e.g. hp(1,3)]? \fBhp(0,0)\fR
                     54: Device data: #cylinders=1024, #tracks=16, #sectors=32
                     55: Testing hp(0,0), chunk size is 16384 bytes.
                     56: \fI(chunk size is the number of bytes read per disk access)\fP
                     57: Start ...Make sure hp(0,0) is online
                     58:  ...
                     59: \fI(errors are reported as they occur)\fP
                     60:  ...
                     61: \fI(...program restarts to allow checking other disks)\fP
                     62: \fI(...to abort halt machine with ^P)\fP
                     63: .in -5
                     64: .fi
                     65: .sp 1
                     66: .SH DIAGNOSTICS
                     67: The diagnostics are intended to be self explanatory. Note, however, that 
                     68: the device number
                     69: in the diagnostic messages is identified as  \fItypeX\fR instead of 
                     70: \fItype(a,u)\fR where \fIX\fR = a*8+u, e.g., hp(1,3) becomes hp11.
                     71: .SH SEE ALSO
                     72: format(8V), bad144(8)
                     73: .SH AUTHOR
                     74: Helge Skrivervik

unix.superglobalmegacorp.com

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.