Commit | Line | Data |
---|---|---|
3f6ba420 C |
1 | .TH FORMAT 8V "25 February 1983" |
2 | .UC 4 | |
3 | .SH NAME | |
4 | format \- how to format disk packs | |
5 | .SH DESCRIPTION | |
6 | .PP | |
7 | There are two ways to format disk packs. The simplest is to | |
8 | use the | |
9 | .I format | |
10 | program. The alternative is to use the DEC standard formatting | |
11 | software which operates under the DEC diagnostic supervisor. | |
12 | This manual page describes the operation of | |
13 | .IR format , | |
14 | then concludes with some remarks about using the DEC formatter. | |
15 | .PP | |
16 | .I Format | |
17 | is a standalone program used to | |
18 | format and write-checks disks prior to constructing | |
19 | file systems. | |
20 | In addition to the formatting | |
21 | operation, | |
22 | .I format | |
23 | records any bad sectors encountered | |
24 | according to DEC standard 144. | |
25 | Formatting is performed one track at a | |
26 | time by writing the appropriate | |
27 | headers and a test pattern and then applying | |
28 | a write check using the controller's ``write check header and data'' | |
29 | command. | |
30 | A sector is marked bad if an unrecoverable media | |
31 | error is detected, or if a correctable | |
32 | ECC error greater than 5 bits in length | |
33 | is detected (such errors are indicated as | |
34 | ``ECC'' in the summary printed upon | |
35 | completing the format operation). | |
36 | After the entire disk | |
37 | has been formatted and checked, | |
38 | the total number of errors are reported, | |
39 | any bad sectors and skip sectors are marked, | |
40 | and a bad sector forwarding table | |
41 | is written to the disk in the first five | |
42 | even numbered sectors of the last track. | |
43 | .I Format | |
44 | may be used on any UNIBUS or MASSBUS drive | |
45 | supported by the \fIup\fP and \fIhp\fP device | |
46 | drivers. | |
47 | .PP | |
48 | The test pattern used during the media check | |
49 | may be selected from one of: 0xf00f (RH750 worst case), | |
50 | 0xec6d (media worst case), and 0xa5a5 (alternating | |
51 | 1's and 0's). | |
52 | Normally the media worst case pattern is used. | |
53 | .PP | |
54 | Each time | |
55 | .I format | |
56 | is run a completely new bad sector table is generated | |
57 | based on errors encountered while formatting. | |
58 | The device driver, however, will always attempt to | |
59 | read any existing bad sector table when the device is | |
60 | first opened. | |
61 | Thus, if a disk pack has never previously been formatted, | |
62 | or has been formatted with different sectoring, | |
63 | five error messages will be printed when the driver attempts | |
64 | to read the bad sector table; these diagnostics should be ignored. | |
65 | .PP | |
66 | Formatting a 400 megabyte disk on a MASSBUS disk controller | |
67 | usually takes about 25 minutes. | |
68 | Formatting on a UNIBUS disk controller takes significantly | |
69 | longer. | |
70 | For every tenth cylinder formatted | |
71 | .I format | |
72 | prints a message indicating the current sector being formatted. | |
73 | (This message is just to reassure people that nothing is | |
74 | is amiss.) | |
75 | .PP | |
76 | .I Format | |
77 | uses the standard notation of the standalone i/o library | |
78 | in identifying a drive to be formatted. A drive is | |
79 | specified as | |
80 | .IR zz ( x , y ), | |
81 | where | |
82 | .I zz | |
83 | refers to the controller type (either | |
84 | .I hp | |
85 | or | |
86 | .IR up ), | |
87 | .I x | |
88 | is the number unit number of the drive; | |
89 | 8 times the UNIBUS or MASSBUS | |
90 | adaptor number plus the MASSBUS drive number or UNIBUS | |
91 | drive unit number; and | |
92 | .I y | |
93 | is the file system partition | |
94 | on drive | |
95 | .I x | |
96 | (this should always be 0). | |
97 | For example, ``hp(1,0)'' indicates that drive | |
98 | 1 on MASSBUS adaptor 0 should be formatted; while | |
99 | ``up(8,0)'' indicates UNIBUS drive 0 on UNIBUS adaptor 1 | |
100 | should be formatted. | |
101 | .PP | |
102 | Before each formatting attempt, | |
103 | .I format | |
104 | prompts the user in case debugging should be enabled | |
105 | in the appropriate device driver. A carriage return | |
106 | disables debugging information. | |
107 | .PP | |
108 | .I Format | |
109 | should be used prior to building file systems (with | |
110 | .IR newfs (8)) | |
111 | to insure all sectors with uncorrectable media errors | |
112 | are remapped. If a drive develops uncorrectable | |
113 | defects after formatting, the program | |
114 | .IR badsect (8) | |
115 | must be used. | |
116 | .SH EXAMPLE | |
117 | A sample run of | |
118 | .I format | |
119 | is shown below. | |
120 | In this example (using a VAX-11/780), | |
121 | .I format | |
122 | is loaded from the console floppy; | |
123 | on an 11/750 | |
124 | .I format | |
125 | will be loaded from the root file system. | |
126 | Boldface means user input. | |
127 | As usual, ``#'' and ``@'' may be used to edit input. | |
128 | .nf | |
129 | .in +0.5i | |
130 | .ta 1i | |
131 | .sp 1 | |
132 | >>>\fBL FORMAT\fP | |
133 | LOAD DONE, 00004400 BYTES LOADED | |
134 | >>>\fBS 2\fP | |
135 | Disk format/check utility | |
136 | .sp | |
137 | Debugging level (1=bse, 2=ecc, 3=bse+ecc)? | |
138 | Disk name? \fBhp(8,0)\fR | |
139 | Formatting unit 0 on hp1 verify (yes/no)? \fByes\fP | |
140 | Is this really what you want to do (y/n)? \fBy\fR | |
141 | Device data: #cylinders=842, #tracks=20, #sectors=48 | |
142 | Available test patterns are: | |
143 | 1 - (f00f) rh750 worst case | |
144 | 2 - (ec6d) media worst case | |
145 | 3 - (a5a5) alternating 1's and 0's | |
146 | Pattern (one of the above, other to restart)? \fB2\fP | |
147 | Start formatting...make sure the drive is online | |
148 | ... | |
149 | (\fIsoft ecc's and other errors are reported as they occur\fP) | |
150 | ... | |
151 | (\fIif 4 write check errors were found, the program terminates like this...\fP) | |
152 | ... | |
153 | Errors: | |
154 | Write check: 4 | |
155 | Bad sector: 0 | |
156 | ECC: 0 | |
157 | Skip sector: 0 | |
158 | Total of 4 hard errors found. | |
159 | Writing bad sector table at block 524256 | |
160 | (\fI524256 is the block # of the first block in the bad sector table\fP) | |
161 | Done | |
162 | (\fI...program restarts to allow formatting other disks\fP) | |
163 | (\fI...to abort halt machine with ^P\fP) | |
164 | .in -0.5i | |
165 | .fi | |
166 | .sp 1 | |
167 | .SH DIAGNOSTICS | |
168 | The diagnostics are intended to be self explanatory. | |
169 | .SH "USING DEC SOFTWARE TO FORMAT" | |
170 | .PP | |
171 | .B | |
172 | Warning: These instructions are for people with 11/780 CPU's. The | |
173 | steps needed for 11/750 or 11/730 cpu's are similar, but not | |
174 | covered in detail here. | |
175 | .I | |
176 | .PP | |
177 | The formatting procedures are different for each type of disk. Listed | |
178 | here are the formatting procedures for RK07's, RP0X, and RM0X | |
179 | disks. | |
180 | .PP | |
181 | You should shut down UNIX and halt the machine to do any disk formatting. | |
182 | Make certain you put in the pack you want formatted. It is also a good idea | |
183 | to spin down or write protect the disks you don't want to format, just in case. | |
184 | .PP | |
185 | .B Formatting a RK07. | |
186 | Load the console floppy labled, "RX11 VAX DSK LD DEV #1" in | |
187 | the console disk drive, and type the following commands: | |
188 | .nf | |
189 | >>>BOOT | |
190 | DIAGNOSTIC SUPERVISOR. ZZ-ESSAA-X5.0-119 23-JAN-1980 12:44:40.03 | |
191 | DS>ATTACH DW780 SBI DW0 3 5 | |
192 | DS>ATTACH RK611 DMA | |
193 | DS>ATTACH RK07 DW0 DMA0 | |
194 | DS>SELECT DMA0 | |
195 | DS>LOAD EVRAC | |
196 | DS>START/SEC:PACKINIT | |
197 | .fi | |
198 | .PP | |
199 | .B Formatting a RP0X. | |
200 | Follow the above procedures except that the | |
201 | ATTACH and SELECT lines should read: | |
202 | .nf | |
203 | DS>ATTACH RH780 SBI RH0 8 5 | |
204 | DS>ATTACH RP0X RH0 DBA0 (RP0X is, e.g. RP06) | |
205 | DS>SELECT DBA0 | |
206 | .fi | |
207 | .PP | |
208 | This is for drive 0 on mba0; use 9 instead of 8 for mba1, etc. | |
209 | .PP | |
210 | .B Formatting a RM0X. | |
211 | Follow the above procedures except that the | |
212 | ATTACH and SELECT lines should read: | |
213 | .nf | |
214 | DS>ATTACH RH780 SBI RH0 8 5 | |
215 | DS>ATTACH RM0X RH0 DRA0 | |
216 | DS>SELECT DRA0 | |
217 | .fi | |
218 | .PP | |
219 | Don't forget to put your UNIX console floppy back | |
220 | in the floppy disk drive. | |
221 | .SH SEE ALSO | |
222 | bad144(8), | |
223 | badsect(8), | |
224 | newfs(8) | |
225 | .SH BUGS | |
226 | An equivalent facility should be available which operates under | |
227 | a running UNIX system. | |
228 | .PP | |
229 | It should be possible to define more | |
230 | precisely what a ``hard ECC'' error is; e.g. the maximum unacceptable | |
231 | ECC width. |