reboot.tproj/boot_vax.8

   1 .\" Copyright (c) 1980, 1991, 1993
   2 .\"     The Regents of the University of California.  All rights reserved.
   3 .\"
   4 .\" Redistribution and use in source and binary forms, with or without
   5 .\" modification, are permitted provided that the following conditions
   6 .\" are met:
   7 .\" 1. Redistributions of source code must retain the above copyright
   8 .\"    notice, this list of conditions and the following disclaimer.
   9 .\" 2. Redistributions in binary form must reproduce the above copyright
  10 .\"    notice, this list of conditions and the following disclaimer in the
  11 .\"    documentation and/or other materials provided with the distribution.
  12 .\" 3. All advertising materials mentioning features or use of this software
  13 .\"    must display the following acknowledgement:
  14 .\"     This product includes software developed by the University of
  15 .\"     California, Berkeley and its contributors.
  16 .\" 4. Neither the name of the University nor the names of its contributors
  17 .\"    may be used to endorse or promote products derived from this software
  18 .\"    without specific prior written permission.
  19 .\"
  20 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
  21 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  22 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
  23 .\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
  24 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
  25 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
  26 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
  27 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
  28 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
  29 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
  30 .\" SUCH DAMAGE.
  31 .\"
  32 .\"     @(#)boot_vax.8  8.2 (Berkeley) 4/19/94
  33 .\"
  34 .Dd April 19, 1994
  35 .Dt BOOT 8 vax
  36 .Os
  37 .Sh NAME
  38 .Nm boot
  39 .Nd
  40 system bootstrapping procedures
  41 .Sh DESCRIPTION
  42 .Sy Power fail and crash recovery.
  43 Normally, the system will reboot itself at power-up or after crashes.
  44 Provided the auto-restart is enabled on the machine front panel,
  45 an automatic consistency check of the file systems will be performed,
  46 and unless this fails, the system will resume multi-user operations.
  47 .Pp
  48 .Sy Cold starts.
  49 These are processor-type dependent.
  50 On an 11/780, there are two floppy files for each disk controller,
  51 both of which cause boots from unit 0 of the root file system
  52 of a controller located on mba0 or uba0.
  53 One gives a single user shell, while the other invokes the multi-user
  54 automatic reboot.
  55 Thus these files are
  56 .Tn HPS
  57 and
  58 .Tn HPM
  59 for the single
  60 and multi-user boot from
  61 .Tn MASSBUS
  62 RP06/RM03/RM05 disks,
  63 .Tn UPS
  64 and
  65 .Tn UPM
  66 for
  67 .Tn UNIBUS
  68 storage module controller and disks
  69 such as the
  70 .Tn EMULEX
  71 SC-21
  72 and
  73 .Tn AMPEX
  74 9300 pair,
  75 .Tn RAS
  76 and
  77 .Tn RAM
  78 to boot from
  79 .Tn MSCP
  80 controllers and disks such as the RA81,
  81 or
  82 .Tn HKS
  83 and
  84 .Tn HKM
  85 for RK07 disks.
  86 There is also a script for booting from the default device,
  87 which is normally a copy of one of the standard multi-user boot scripts,
  88 but which may be modified to perform other actions
  89 or to boot from a different unit.
  90 The situation on the 8600 is similar, with scripts loaded from the console RL02.
  91 .Pp
  92 Giving the command
  93 .Pp
  94 .Dl >>>BOOT HPM
  95 .Pp
  96 would boot the system from (e.g.) an RP06 and run the automatic consistency
  97 check as described in
  98 .Xr fsck 8 .
  99 (Note that it may
 100 be necessary to type control-P
 101 and halt the processor
 102 to gain the attention of the
 103 .Tn LSI-11
 104 before getting the >>> prompt.)
 105 The command
 106 .Pp
 107 .Dl >>>BOOT ANY
 108 .Pp
 109 invokes a version of the boot program in a way which allows you to
 110 specify any system as the system to be booted.
 111 It reads from the console a device specification (see below) followed
 112 immediately by a pathname.
 113 .Pp
 114 The scripts may be modified for local configuration if necessary.
 115 The flags are placed in register 11 (as defined in
 116 .Aq Pa sys/reboot.h ) .
 117 The boot device is specified in register 10.
 118 The encoding of this register is also defined in
 119 .Aq Pa sys/reboot.h .
 120 The current encoding has a historical basis, and is shown in the following
 121 table:
 122 .Pp
 123 .Bd -unfilled -offset indent -compact
 124 bits    usage
 125 0-7     boot device type (the device major number)
 126 8-15    disk partition
 127 16-19   drive unit
 128 20-23   controller number
 129 24-27   adaptor number (UNIBUS or MASSBUS as appropriate)
 130 .Ed
 131 .Pp
 132 The adaptor number corresponds to the normal configuration on the 11/750,
 133 and to the order in which adaptors are found on the 11/780 and 8600
 134 (generally the same as the numbers used by
 135 .Tn UNIX ) .
 136 .Pp
 137 On an 11/750, the reset button will boot from the device
 138 selected by the front panel boot device switch.  In systems
 139 with RK07's, position B normally selects the RK07 for boot.
 140 This will boot multi-user.  To boot from RK07 with boot flags you
 141 may specify
 142 .Pp
 143 .Bd -unfilled -offset indent -compact
 144 .Li \&>>>B/ Ns Fl n No DMA0
 145 .Ed
 146 .Pp
 147 where, giving a
 148 .Ar n
 149 of 1 causes the boot program
 150 to ask for the name of the system to be bootstrapped,
 151 giving a
 152 .Ar n
 153 of 2 causes the boot program to come up single
 154 user, and a
 155 .Ar n
 156 of 3 causes both of these actions to occur.
 157 The ``DM'' specifies RK07, the ``A'' represents the adaptor number
 158 .Pf ( Tn UNIBUS
 159 or
 160 .Tn MASSBUS ) ,
 161 and the ``0'' is the drive unit number.
 162 Other disk types which may be used are DB
 163 .Pq Tn MASSBUS ,
 164 DD (TU58),
 165 and DU
 166 .Pf ( Tn UDA-50/RA
 167 disk).
 168 A non-zero disk partition can be used by adding (partition times 1000 hex)
 169 to
 170 .Ar  n .
 171 .Pp
 172 The boot procedure on the Micro
 173 .Tn VAX
 174 II
 175 is similar.
 176 A switch on the back panel sets the power-up action
 177 to autoboot or to halt.
 178 When halted, the processor may be booted using the same syntax
 179 as on the 11/750.
 180 .Pp
 181 The 11/750 boot procedure uses the boot roms to load block 0 off of
 182 the specified device.  The /usr/mdec directory contains a number
 183 of bootstrap programs for the various disks which should be placed
 184 in a new pack by
 185 .Xr disklabel 8 .
 186 Similarly, the Micro
 187 .Tn VAX
 188 II boot procedure loads a boot parameter block
 189 from block 0 of the disk.
 190 The
 191 .Xr rdboot
 192 .Dq bootstrap
 193 contains the correct parameters for an
 194 .Tn MSCP
 195 disk such
 196 as the RD53.
 197 .Pp
 198 On any processor, the
 199 .Em boot
 200 program
 201 finds the corresponding file on the given device
 202 .Pf ( Pa vmunix
 203 by default), loads that file
 204 into memory location zero, and starts the program at the entry address
 205 specified in the program header (after clearing off the high bit
 206 of the specified entry address).
 207 .Pp
 208 The file specifications used with
 209 .Dq BOOT ANY
 210 or
 211 .Dq \&B/3
 212 are of the form:
 213 .Pp
 214 .Dl device(adaptor,controller,unit,minor)
 215 .Pp
 216 where
 217 .Ar device
 218 is the type of the device to be searched,
 219 .Ar adaptor
 220 is the
 221 .Tn UNIBUS
 222 or
 223 .Tn MASSBUS
 224 number of the adaptor to which the device is attached,
 225 .Ar controller
 226 is the unit number of the controller or
 227 .Tn MASSBUS
 228 tape formatter on that adaptor,
 229 .Ar unit
 230 is the unit number of the disk or transport slave unit of the tape,
 231 and
 232 .Ar minor
 233 is the disk partition or tape file number.
 234 Leading adaptor or controller numbers default to 0.
 235 Normal line editing characters can be used when typing the file specification.
 236 The following list of supported devices may vary from installation to
 237 installation:
 238 .Pp
 239 .Bd -unfilled -offset indent -compact
 240 hp      MASSBUS disk drive
 241 up      UNIBUS storage module drive
 242 ht      TE16,TU45,TU77 on MASSBUS
 243 kra     storage module on a KDB50
 244 mt      TU78 on MASSBUS
 245 hk      RK07 on UNIBUS
 246 ra      storage module on a MSCP-compatible UNIBUS controller
 247 rb      storage module on a 730 IDC
 248 rl      RL02 on UNIBUS
 249 tm      TM11 emulation tape drives on UNIBUS
 250 tms     TMSCP-compatible tape
 251 ts      TS11 on UNIBUS
 252 ut      UNIBUS TU45 emulator
 253 .Ed
 254 .Pp
 255 For example,
 256 to boot from a file system which starts at cylinder 0
 257 of unit 0 of a
 258 .Tn MASSBUS
 259 disk, type
 260 .Ql hp(0,0)vmunix
 261 to the boot prompt;
 262 .Ql hp(2,0,1,0)vmunix
 263 would specify drive 1 on
 264 .Tn MASSBUS
 265 adaptor 2;
 266 .Ql up(0,0)vmunix
 267 would specify a
 268 .Tn UNIBUS
 269 drive,
 270 .Ql hk(0,0)vmunix
 271 would specify
 272 an RK07 disk drive,
 273 .Ql ra(1,0,0,0)vmunix
 274 would specify a
 275 .Tn UDA50
 276 disk drive on a second
 277 .Tn UNIBUS ,
 278 and
 279 .Ql rb(0,0)vmunix
 280 would specify a
 281 disk on a 730
 282 .Tn IDC .
 283 For tapes, the minor device number gives a file offset;
 284 .Ql mt(1,2,3,4)
 285 would specify the fifth file on slave 3 of the formatter
 286 at
 287 .Ql drive
 288 2 on mba 1.
 289 .Pp
 290 On an 11/750 with patchable control store,
 291 microcode patches will be installed by
 292 .Em boot
 293 if the file
 294 .Pa psc750.bin
 295 exists in the root of the filesystem from which the system is booted.
 296 .Pp
 297 In an emergency, the bootstrap methods described in the paper
 298 .%T Installing and Operating 4.3bsd
 299 can be used to boot from a distribution tape.
 300 .Sh FILES
 301 .Bl -tag -width /usr/mdec/xxboot -compact
 302 .It Pa /vmunix
 303 system code
 304 .It Pa /boot
 305 system bootstrap
 306 .It Pa /usr/mdec/xxboot
 307 sector-0 boot block for 750, xx is disk type
 308 .It Pa /usr/mdec/bootxx
 309 second-stage boot for 750, xx is disk type
 310 .It Pa /pcs750.bin
 311 microcode patch file on 750
 312 .El
 313 .Sh SEE ALSO
 314 .Xr arff 8 ,
 315 .Xr halt 8 ,
 316 .Xr reboot 8 ,
 317 .Xr shutdown 8
 318 .Sh HISTORY
 319 The
 320 .Nm
 321 command appeared in
 322 .Bx 4.0 .