![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to b.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 / tahoe|
Return to b.t CVS log | Up to [CSRG BSD Unix] / 43BSDReno / share / doc / smm / 01.setup / tahoe |
1.1 root 1: .\" Copyright (c) 1988 The 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: .\" @(#)b.t 1.4 (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 B \- installation troubleshooting
25: .ds CF \*(DY
26: .bp
27: .LG
28: .B
29: .ce
30: APPENDIX B \- 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: \fBBooting the generic system\fP
44: .LP
45: \fIcopy does not copy 205 records\fP
46: .LP
47: If a tape read error occurred,
48: clean your tape drive heads. If a disk write error occurred,
49: the disk formatting may have failed. If the disk pack is
50: removable, try another one. If you are currently running
51: UNIX, you can reboot your old system and use \fIdd\fP to
52: copy the mini-root file system into a disk partition
53: (assuming the destination is not in use by the running
54: system).
55: .LP
56: \fIboot prints ``not a directory''\fP
57: .LP
58: The
59: .I boot
60: program was unable to find the requested program because
61: it encountered something other than a directory while
62: searching the file system.
63: This usually suggests that
64: no file system is present on the disk partition supplied,
65: or the file system has been corrupted. First check to
66: make sure you typed the correct line to boot. If this
67: is the case and you are booting from the mini-root file
68: system, the mini-root was probably not copied correctly off the
69: tape (perhaps it was not placed in the correct disk partition).
70: Try reinstalling the mini-root file system or, if trying
71: to boot the true root file system, try booting from the
72: mini-root file system and run \fIfsck\fP on the restored
73: root file system to insure its integrity. Finally, as
74: a last resort, copy the \fIboot\fP program from the
75: mini-root file system to the newly installed root file system.
76: .LP
77: \fIboot prints ``bad format''\fP
78: .LP
79: The program you requested
80: .I boot
81: to load did not have a valid magic number in its header. This should
82: never happen on a distribution system. If you were trying to boot off
83: the root file system, reboot the system on the mini-root file system
84: and look at the program on the root file system. Try copying the copy
85: of vmunix on the mini-root to the root file system also.
86: .LP
87: \fIboot prints ``read short''\fP
88: .LP
89: The file header for the program contained a size larger
90: than the actual size of the file located on disk. This
91: is probably the result of file system corruption (or a
92: disk I/O error). Try booting again or creating a new
93: copy of the program to be loaded (see above).
94: .LP
95: This section contains common problems encountered when booting
96: the generic version of the system.
97: .LP
98: \fIsystem panics with ``panic: iinit''\fP
99: .LP
100: This occurred because the system was unable to mount
101: the root file system.
102: The root file system supplied at the ``root device?''
103: prompt was probably incorrect. Remember that when running on the
104: mini-root file system, this question must be answered
105: with something of the form \fIxx#\fP*, where \fIxx\fP is one of the
106: disk types listed in section 1.4, and \fI#\fP is the unit number.
107: If the answer had been ``dk0'', the system would have used the ``a''
108: partition on unit 0 of the ``dk'' drive, where presumably no file
109: system exists.
110: .LP
111: Alternatively, the file system on which you were trying
112: to run is corrupted. Try
113: reinstalling the appropriate file system.
114: .LP
115: \fIsystem crashes during autoconfiguration\fP
116: .LP
117: This is almost always caused by an
118: unsupported device being present at a
119: location where a supported device was expected.
120: You must disable the device in some way, either
121: by pulling it off the bus, or by moving the location
122: of the console status register (consult Appendix A
123: for a complete list of VERSAbus CSR's used in the generic system).
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.