![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to c.t CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 01.setup / vax|
Return to c.t CVS log | Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 01.setup / vax |
1.1 root 1: .\" Copyright (c) 1980, 1986, 1988 Regents of the University of California.
2: .\" All rights reserved.
3: .\"
4: .\" Redistribution and use in source and binary forms are permitted
5: .\" provided that the above copyright notice and this paragraph are
6: .\" duplicated in all such forms and that any documentation,
7: .\" advertising materials, and other materials related to such
8: .\" distribution and use acknowledge that the software was developed
9: .\" by the University of California, Berkeley. The name of the
10: .\" University may not be used to endorse or promote products derived
11: .\" from this software without specific prior written permission.
12: .\" THIS SOFTWARE IS PROVIDED ``AS IS'' AND WITHOUT ANY EXPRESS OR
13: .\" IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED
14: .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
15: .\"
16: .\" @(#)c.t 6.3 (Berkeley) 3/7/89
17: .\"
18: .de IR
19: \fI\\$1\fP\|\\$2
20: ..
21: .ds LH "Installing/Operating \*(4B
22: .nr H1 6
23: .nr H2 0
24: .ds RH "Appendix C \- installation troubleshooting
25: .ds CF \*(DY
26: .bp
27: .LG
28: .B
29: .ce
30: APPENDIX C \- INSTALLATION TROUBLESHOOTING
31: .sp 2
32: .R
33: .NL
34: .PP
35: This appendix lists and explains certain problems
36: that might be encountered while trying to install the \*(4B
37: distribution. The information provided here is
38: limited to the early steps in the installation process;
39: i.e. up to the point where the root file system is installed.
40: If you have a problem installing
41: the release consult this section before contacting our group.
42: .SH
43: \fBUsing the distribution console medium.\fP
44: .LP
45: This section describes problems that may occur when using
46: the programs provided on the distributed console medium:
47: TU58 cassette or RX01 floppy disk.
48: .LP
49: \fIprogram can not be loaded\fP.
50: .LP
51: Check to make
52: sure the correct floppy or cassette is being used.
53: If using a floppy, be sure it is not in upside down. If using
54: a cassette on an 11/730, be certain drive 0 is being used.
55: If a hard I/O error occurred while reading a floppy, try resetting
56: the console LSI-11 by powering it on and off. If you can not
57: boot the cassette's bootstrap monitor, verify that the standard
58: DEC console cassette can be read; if it can not, your cassette
59: drive is probably broken.
60: .LP
61: \fIprogram halts without warning\fP.
62: .LP
63: Check to make sure you have specified
64: the correct disk to format; consult sections 1.3 and 1.4 for a
65: discussion of
66: the VAX and UNIX device naming conventions. On 11/750's,
67: specifying a non-existent MASSBUS device will cause the
68: program to halt as it receives an interrupt (standalone
69: programs operate by polling devices).
70: .LP
71: If using a floppy, try reading the floppy under
72: your current system. If this works, copy the floppy to a new
73: one and begin again. If using a cassette on an 11/730,
74: do likewise.
75: .LP
76: \fIformat prints ``Known devices are ...''\fP.
77: .LP
78: You have requested
79: .I format
80: to work on a device for which it has no driver, or that does not exist;
81: only the listed devices are supported.
82: .LP
83: \fIformat, boot, or copy prints ``unknown drive type''\fP.
84: .LP
85: A MASSBUS disk was specified, but the associated MASSBUS
86: drive type register indicates a drive of unknown type.
87: This probably means you typed something wrong or your
88: hardware is incorrectly configured.
89: .LP
90: \fIformat, boot, or copy prints ``unknown device''\fP.
91: .LP
92: The device specified is probably not one of those supported
93: by the distribution; consult section 1.1. If the device
94: is listed in section 1.1, the drive may be dual-ported, or
95: for some other reason the driver was unable to decipher
96: its characteristics. If this is a MASSBUS drive, try
97: powering the MASSBUS adapter and/or controller on and
98: off to clear the drive type register.
99: .LP
100: \fIcopy does not copy 205 records\fP
101: .LP
102: If a tape read error occurred,
103: clean your tape drive heads. If a disk write error occurred,
104: the disk formatting may have failed. If the disk pack is
105: removable, try another one. If you are currently running
106: UNIX, you can reboot your old system and use \fIdd\fP to
107: copy the mini-root file system into a disk partition
108: (assuming the destination is not in use by the running
109: system).
110: .LP
111: \fIboot prints ``not a directory''\fP
112: .LP
113: The
114: .I boot
115: program was unable to find the requested program because
116: it encountered something other than a directory while
117: searching the file system.
118: This usually suggests that
119: no file system is present on the disk partition supplied,
120: or the file system has been corrupted. First check to
121: make sure you typed the correct line to boot. If this
122: is the case and you are booting from the mini-root file
123: system, the mini-root was probably not copied correctly off the
124: tape (perhaps it was not placed in the correct disk partition).
125: Try reinstalling the mini-root file system or, if trying
126: to boot the true root file system, try booting from the
127: mini-root file system and run \fIfsck\fP on the restored
128: root file system to insure its integrity. Finally, as
129: a last resort, copy the \fIboot\fP program from the
130: mini-root file system to the newly installed root file system.
131: .LP
132: \fIboot prints ``bad format''\fP
133: .LP
134: The program you requested
135: .I boot
136: to load did not have a 407, 410, or 413 magic number in its
137: header. This should never happen on a distribution system.
138: If you were trying to boot off the root file system, reboot
139: the system on the mini-root file system and look at the
140: program on the root file system. Try copying the copy
141: of vmunix on the mini-root to the root file system also.
142: .LP
143: \fIboot prints ``Short read''\fP
144: .LP
145: The file header for the program contained a size larger
146: than the actual size of the file located on disk. This
147: is probably the result of file system corruption (or a
148: disk I/O error). Try booting again or creating a new
149: copy of the program to be loaded (see above).
150: .SH
151: \fBBooting the generic system\fP
152: .LP
153: This section contains common problems encountered when booting
154: the generic version of the system.
155: .LP
156: \fIsystem panics with ``panic: iinit''\fP
157: .LP
158: This occurred because the system was unable to mount
159: the root file system.
160: The root file system supplied at the ``root device?''
161: prompt was probably incorrect. Remember that when running on the
162: mini-root file system, this question must be answered
163: with something of the form ``hp0*''. If the answer
164: had been ``hp0'', the system would have used the ``a''
165: partition on unit 0 of the ``hp'' drive, where presumably
166: no file system exists.
167: .LP
168: Alternatively, the file system on which you were trying
169: to run is corrupted. Try
170: reinstalling the appropriate file system.
171: .LP
172: \fIsystem selects incorrect root device\fP
173: .LP
174: That is, you try to boot the system single user with
175: ``B/2'' or ``B xxS'' but do not get the root file system
176: in the expected location. This is most likely caused
177: by your having many disks available more suited to be
178: a root file system than the one you wanted. For example,
179: if you have a ``up'' disk and an ``hk'' disk and install
180: the system on the ``hk'', then try to boot the system
181: to single-user mode, the heuristic used by the generic
182: system to select the root file system will choose the
183: ``up'' disk. The following list gives, in descending
184: order, those disks thought most suitable to be a root
185: file system: ``hp'', ``up'', ``ra'', ``rb'', ``rl'', ``hk''
186: (the position of ``rl'' is subject to argument).
187: To get the root device you want you must boot
188: using ``B/3'' or ``B ANY'', then supply the root device
189: at the prompt.
190: .LP
191: \fIsystem crashes during autoconfiguration\fP
192: .LP
193: This is almost always caused by an
194: unsupported UNIBUS device being present at a
195: location where a supported device was expected.
196: You must disable the device in some way, either
197: by pulling it off the bus, or by moving the location
198: of the console status register (consult Appendix A
199: for a complete list of UNIBUS csr's used in the generic system).
200: .LP
201: \fIsystem does not find device(s)\fP
202: .LP
203: The UNIBUS device is not at a standard location. Consult
204: the list of control status register addresses in Appendix
205: A, or wait to configure a system to your hardware.
206: .LP
207: Alternatively, certain devices are difficult to locate
208: during autoconfiguration. A classic example is the TS11
209: tape drive that does not autoconfigure properly if it is
210: rewinding when the system is rebooted. Tape drives should
211: configure properly if they are off-line, or are not performing
212: a tape movement. Disks that are dual-ported should
213: autoconfigure properly if the drive is not being simultaneously
214: accessed through the alternate port.
215: .SH
216: \fBBuilding console cassettes\fP
217: .LP
218: This sections describes common problems encountered
219: while constructing a console bootstrap cassette.
220: .LP
221: \fIsystem crashes\fP
222: .LP
223: You are trying to build a cassette for an 11/750.
224: On an 11/750 the system is booted by using a bootstrap
225: prom and sector 0 of the root file system. Refer
226: to section 2.1.5 or
227: .IR tu (4)
228: for the appropriate reprimand.
229: .LP
230: \fIsystem hangs\fP
231: .LP
232: You are using an MRSP prom on an 11/750 and think you
233: can ignore the instructions in this document. The
234: problem here is that the generic system only supports
235: the MRSP prom on an 11/730. Using it on an 11/750 requires
236: a special system configuration; consult
237: .IR tu (4)
238: for more information.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.