diff options
Diffstat (limited to 'static/netbsd/man8/man8.vax')
| -rw-r--r-- | static/netbsd/man8/man8.vax/Makefile | 4 | ||||
| -rw-r--r-- | static/netbsd/man8/man8.vax/boot.8 | 321 | ||||
| -rw-r--r-- | static/netbsd/man8/man8.vax/crash.8 | 205 | ||||
| -rw-r--r-- | static/netbsd/man8/man8.vax/drtest.8 | 112 | ||||
| -rw-r--r-- | static/netbsd/man8/man8.vax/format.8 | 295 |
5 files changed, 937 insertions, 0 deletions
diff --git a/static/netbsd/man8/man8.vax/Makefile b/static/netbsd/man8/man8.vax/Makefile new file mode 100644 index 00000000..5b657add --- /dev/null +++ b/static/netbsd/man8/man8.vax/Makefile @@ -0,0 +1,4 @@ +MAN = $(wildcard *.8) + +include ../../../mandoc.mk + diff --git a/static/netbsd/man8/man8.vax/boot.8 b/static/netbsd/man8/man8.vax/boot.8 new file mode 100644 index 00000000..741c1f7f --- /dev/null +++ b/static/netbsd/man8/man8.vax/boot.8 @@ -0,0 +1,321 @@ +.\" $NetBSD: boot.8,v 1.15 2018/03/18 10:54:54 ragge Exp $ +.\" +.\" Copyright (c) 1980, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" @(#)boot_vax.8 8.2 (Berkeley) 4/19/94 +.\" +.Dd April 19, 1994 +.Dt BOOT 8 vax +.Os +.Sh NAME +.Nm boot +.Nd +system bootstrapping procedures +.Sh DESCRIPTION +.Ss Power fail and crash recovery +Normally, the system will reboot itself at power-up or after crashes. +Provided the auto-restart is enabled on the machine front panel, +an automatic consistency check of the file systems will be performed, +and unless this fails, the system will resume multi-user operations. +.Pp +.Ss Cold starts +These are processor-type dependent. +On an 11/780, there are two floppy files for each disk controller, +both of which cause boots from unit 0 of the root file system +of a controller located on mba0 or uba0. +One gives a single user shell, while the other invokes the multi-user +automatic reboot. +Thus these files are +.Tn HPS +and +.Tn HPM +for the single +and multi-user boot from +.Tn MASSBUS +RP06/RM03/RM05 disks, +.Tn UPS +and +.Tn UPM +for +.Tn UNIBUS +storage module controller and disks +such as the +.Tn EMULEX +SC-21 +and +.Tn AMPEX +9300 pair, +.Tn RAS +and +.Tn RAM +to boot from +.Tn MSCP +controllers and disks such as the RA81, +or +.Tn HKS +and +.Tn HKM +for RK07 disks. +There is also a script for booting from the default device, +which is normally a copy of one of the standard multi-user boot scripts, +but which may be modified to perform other actions +or to boot from a different unit. +The situation on the 8600 is similar, with scripts loaded from the console RL02. +.Pp +Giving the command +.Pp +.Dl >>>BOOT HPM +.Pp +would boot the system from (e.g.) an RP06 and run the automatic consistency +check as described in +.Xr fsck 8 . +(Note that it may +be necessary to type control-P +and halt the processor +to gain the attention of the +.Tn LSI-11 +before getting the >>> prompt.) +The command +.Pp +.Dl >>>BOOT ANY +.Pp +invokes a version of the boot program in a way which allows you to +specify any system as the system to be booted. +It reads from the console a device specification (see below) followed +immediately by a pathname. +.Pp +The scripts may be modified for local configuration if necessary. +The flags are placed in register 11 (as defined in +.In sys/reboot.h ) . +The boot device is specified in register 10. +The encoding of this register is also defined in +.In sys/reboot.h . +The current encoding has a historical basis, and is shown in the following +table: +.Pp +.Bd -unfilled -offset indent -compact +bits usage +0-7 boot device type (the device major number) +8-15 disk partition +16-19 drive unit +20-23 controller number +24-27 adaptor number (UNIBUS or MASSBUS as appropriate) +.Ed +.Pp +The adaptor number corresponds to the normal configuration on the 11/750, +and to the order in which adaptors are found on the 11/780 and 8600 +(generally the same as the numbers used by +.Ux ) . +.Pp +On an 11/750, the reset button will boot from the device +selected by the front panel boot device switch. +In systems with RK07's, position B normally selects the RK07 for boot. +This will boot multi-user. +To boot from RK07 with boot flags you may specify +.Pp +.Bd -unfilled -offset indent -compact +.Li \&>>>B/ Ns Fl n No DMA0 +.Ed +.Pp +where, giving a +.Ar n +of 1 causes the boot program +to ask for the name of the system to be bootstrapped, +giving a +.Ar n +of 2 causes the boot program to come up single +user, and a +.Ar n +of 3 causes both of these actions to occur. +The ``DM'' specifies RK07, the ``A'' represents the adaptor number +.Pf ( Tn UNIBUS +or +.Tn MASSBUS ) , +and the ``0'' is the drive unit number. +Other disk types which may be used are DB +.Pq Tn MASSBUS , +DD (TU58), +and DU +.Pf ( Tn UDA-50/RA +disk). +A non-zero disk partition can be used by adding (partition times 1000 hex) +to +.Ar n . +.Pp +The boot procedure on the Micro +.Tn VAX +II +is similar. +A switch on the back panel sets the power-up action +to autoboot or to halt. +When halted, the processor may be booted using the same syntax +as on the 11/750. +.Pp +The 11/750 boot procedure uses the boot ROMs to load block 0 off of +the specified device. +The +.Pa /usr/mdec +directory contains a number +of bootstrap programs for the various disks which should be placed +in a new pack by +.Xr disklabel 8 . +Similarly, the Micro +.Tn VAX +II boot procedure loads a boot parameter block +from block 0 of the disk. +The +.Ic rdboot +.Dq bootstrap +contains the correct parameters for an +.Tn MSCP +disk such +as the RD53. +.Pp +On any processor, the +.Em boot +program +finds the corresponding file on the given device +.Pf ( Pa netbsd +by default), loads that file +into memory location zero, and starts the program at the entry address +specified in the program header (after clearing off the high bit +of the specified entry address). +.Pp +The file specifications used with +.Dq BOOT ANY +or +.Dq \&B/3 +are of the form: +.Pp +.Dl device(adaptor,controller,unit,minor) +.Pp +where +.Ar device +is the type of the device to be searched, +.Ar adaptor +is the +.Tn UNIBUS +or +.Tn MASSBUS +number of the adaptor to which the device is attached, +.Ar controller +is the unit number of the controller or +.Tn MASSBUS +tape formatter on that adaptor, +.Ar unit +is the unit number of the disk or transport slave unit of the tape, +and +.Ar minor +is the disk partition or tape file number. +Leading adaptor or controller numbers default to 0. +Normal line editing characters can be used when typing the file specification. +The following list of supported devices may vary from installation to +installation: +.Pp +.Bd -unfilled -offset indent -compact +hp MASSBUS disk drive +up UNIBUS storage module drive +ht TE16,TU45,TU77 on MASSBUS +kra storage module on a KDB50 +mt TU78 on MASSBUS +hk RK07 on UNIBUS +ra storage module on a MSCP-compatible UNIBUS controller +rb storage module on a 730 IDC +rl RL02 on UNIBUS +tm TM11 emulation tape drives on UNIBUS +tms TMSCP-compatible tape +ts TS11 on UNIBUS +ut UNIBUS TU45 emulator +.Ed +.Pp +For example, +to boot from a file system which starts at cylinder 0 +of unit 0 of a +.Tn MASSBUS +disk, type +.Ql hp(0,0)netbsd +to the boot prompt; +.Ql hp(2,0,1,0)netbsd +would specify drive 1 on +.Tn MASSBUS +adaptor 2; +.Ql up(0,0)netbsd +would specify a +.Tn UNIBUS +drive, +.Ql hk(0,0)netbsd +would specify +an RK07 disk drive, +.Ql ra(1,0,0,0)netbsd +would specify a +.Tn UDA50 +disk drive on a second +.Tn UNIBUS , +and +.Ql rb(0,0)netbsd +would specify a +disk on a 730 +.Tn IDC . +For tapes, the minor device number gives a file offset; +.Ql mt(1,2,3,4) +would specify the fifth file on slave 3 of the formatter +at +.Ql drive +2 on mba 1. +.Pp +On an 11/750 with patchable control store, +microcode patches will be installed by +.Em boot +if the file +.Pa pcs750.bin +exists in the root of the filesystem from which the system is booted. +.Pp +In an emergency, the bootstrap methods described in the paper +.%T Installing and Operating 4.3bsd +can be used to boot from a distribution tape. +.Sh FILES +.Bl -tag -width /usr/mdec/xxboot -compact +.It Pa /netbsd +system code +.It Pa /boot +system bootstrap +.It Pa /usr/mdec/xxboot +sector 0-15 boot block +.It Pa /pcs750.bin +microcode patch file on 750 +.El +.Sh SEE ALSO +.Xr arff 8 , +.Xr halt 8 , +.Xr reboot 8 , +.Xr shutdown 8 +.Sh HISTORY +The +.Nm +command appeared in +.Bx 4.0 . diff --git a/static/netbsd/man8/man8.vax/crash.8 b/static/netbsd/man8/man8.vax/crash.8 new file mode 100644 index 00000000..b3684591 --- /dev/null +++ b/static/netbsd/man8/man8.vax/crash.8 @@ -0,0 +1,205 @@ +.\" $NetBSD: crash.8,v 1.12 2009/03/09 19:24:32 joerg Exp $ +.\" +.\" Copyright (c) 1980, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)crash.8 8.1 (Berkeley) 6/5/93 +.\" +.Dd June 5, 1993 +.Dt CRASH 8 vax +.Os +.Sh NAME +.Nm crash +.Nd UNIX system failures +.Sh DESCRIPTION +This section explains what happens when the system crashes +and (very briefly) how to analyze crash dumps. +.Pp +When the system crashes voluntarily it prints a message of the form +.Pp +.Dl panic: why i gave up the ghost +.Pp +on the console, takes a dump on a mass storage peripheral, +and then invokes an automatic reboot procedure as +described in +.Xr reboot 8 . +(If auto-reboot is disabled on the front panel of the machine the system +will simply halt at this point.) +Unless some unexpected inconsistency is encountered in the state +of the file systems due to hardware or software failure, the system +will then resume multi-user operations. +.Pp +The system has a large number of internal consistency checks; if one +of these fails, then it will panic with a very short message indicating +which one failed. +In many instances, this will be the name of the routine which detected +the error, or a two-word description of the inconsistency. +A full understanding of most panic messages requires perusal of the +source code for the system. +.Pp +The most common cause of system failures is hardware failure, which +can reflect itself in different ways. Here are the messages which +are most likely, with some hints as to causes. +Left unstated in all cases is the possibility that hardware or software +error produced the message in some unexpected way. +.Bl -tag -width 8n -compact +.It iinit +This cryptic panic message results from a failure to mount the root filesystem +during the bootstrap process. +Either the root filesystem has been corrupted, +or the system is attempting to use the wrong device as root filesystem. +Usually, an alternative copy of the system binary or an alternative root +filesystem can be used to bring up the system to investigate. +.It Can't exec /sbin/init +This is not a panic message, as reboots are likely to be futile. +Late in the bootstrap procedure, the system was unable to locate +and execute the initialization process, +.Xr init 8 . +The root filesystem is incorrect or has been corrupted, or the mode +or type of /sbin/init forbids execution. +.It IO err in push +.It hard IO err in swap +The system encountered an error trying to write to the paging device +or an error in reading critical information from a disk drive. +The offending disk should be fixed if it is broken or unreliable. +.It realloccg: bad optim +.It ialloc: dup alloc +.It alloccgblk: cyl groups corrupted +.It ialloccg: map corrupted +.It free: freeing free block +.It free: freeing free frag +.It ifree: freeing free inode +.It alloccg: map corrupted +These panic messages are among those that may be produced +when filesystem inconsistencies are detected. +The problem generally results from a failure to repair damaged filesystems +after a crash, hardware failures, or other condition that should not +normally occur. +A filesystem check will normally correct the problem. +.It timeout table overflow +This really shouldn't be a panic, but until the data structure +involved is made to be extensible, running out of entries causes a crash. +If this happens, make the timeout table bigger. +.It KSP not valid +.It SBI fault +.It CHM? in kernel +These indicate either a serious bug in the system or, more often, +a glitch or failing hardware. +If SBI faults recur, check out the hardware or call +field service. If the other faults recur, there is likely a bug somewhere +in the system, although these can be caused by a flakey processor. +Run processor microdiagnostics. +.It machine check %x: Em description +.It \0\0\0machine dependent machine-check information +Machine checks are different on each type of CPU. +Most of the internal processor registers are saved at the time of the fault +and are printed on the console. +For most processors, there is one line that summarizes the type of machine +check. +Often, the nature of the problem is apparent from this message +and/or the contents of key registers. +The VAX Hardware Handbook should be consulted, +and, if necessary, your friendly field service people should be informed +of the problem. +.It trap type %d, code=%x, pc=%x +A unexpected trap has occurred within the system; the trap types are: +.Bd -literal -offset indent +0 reserved addressing fault +1 privileged instruction fault +2 reserved operand fault +3 bpt instruction fault +4 xfc instruction fault +5 system call trap +6 arithmetic trap +7 ast delivery trap +8 segmentation fault +9 protection fault +10 trace trap +11 compatibility mode fault +12 page fault +13 page table fault +.Ed +.Pp +The favorite trap types in system crashes are trap types 8 and 9, +indicating +a wild reference. The code is the referenced address, and the pc at the +time of the fault is printed. These problems tend to be easy to track +down if they are kernel bugs since the processor stops cold, but random +flakiness seems to cause this sometimes. +The debugger can be used to locate the instruction and subroutine +corresponding to the PC value. +If that is insufficient to suggest the nature of the problem, +more detailed examination of the system status at the time of the trap +usually can produce an explanation. +.It init died +The system initialization process has exited. This is bad news, as no new +users will then be able to log in. Rebooting is the only fix, so the +system just does it right away. +.It out of mbufs: map full +The network has exhausted its private page map for network buffers. +This usually indicates that buffers are being lost, and rather than +allow the system to slowly degrade, it reboots immediately. +The map may be made larger if necessary. +.El +.Pp +That completes the list of panic types you are likely to see. +.Pp +When the system crashes it writes (or at least attempts to write) +an image of memory into the back end of the dump device, +usually the same as the primary swap +area. After the system is rebooted, the program +.Xr savecore 8 +runs and preserves a copy of this core image and the current +system in a specified directory for later perusal. See +.Xr savecore 8 +for details. +.Pp +To analyze a dump you should begin by running +.Ic adb +with the +.Fl k +flag on the system load image and core dump. +If the core image is the result of a panic, +the panic message is printed. +Normally the command +.Dq $c +will provide a stack trace from the point of +the crash and this will provide a clue as to +what went wrong. +For more detail +see +.Dq Using ADB to Debug the UNIX Kernel . +.Sh SEE ALSO +.Xr gdb 1 , +.Xr reboot 8 +.br +.Dq VAX 11/780 System Maintenance Guide +and +.Dq VAX Hardware Handbook +for more information about machine checks. +.br +.Dq Using ADB to Debug the UNIX Kernel diff --git a/static/netbsd/man8/man8.vax/drtest.8 b/static/netbsd/man8/man8.vax/drtest.8 new file mode 100644 index 00000000..e67ddaa9 --- /dev/null +++ b/static/netbsd/man8/man8.vax/drtest.8 @@ -0,0 +1,112 @@ +.\" $NetBSD: drtest.8,v 1.16 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" Copyright (c) 1983, 1991, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)drtest.8 8.1 (Berkeley) 6/5/93 +.\" +.Dd February 17, 2017 +.Dt DRTEST 8 vax +.Os +.Sh NAME +.Nm drtest +.Nd stand-alone disk test program +.Sh DESCRIPTION +.Nm +is a stand-alone program used to read a disk +track by track. +It was primarily intended as a test program +for new stand-alone drivers, but has shown +useful in other contexts as well, such as +verifying disks and running speed +tests. For example, when a disk has been formatted +(by +.Xr vax/format 8 ) , +you can check that +hard errors has been taken care of by running +.Nm . +No hard errors should be found, but in many cases +quite a few soft +.Tn ECC +errors will be reported. +.Pp +While +.Nm +is running, the cylinder number is printed on +the console for every 10th cylinder read. +.Sh EXAMPLES +A sample run of +.Nm +is shown below. +In this example (using a 750), +.Nm +is loaded from the root file system; +usually it +will be loaded from the machine's +console storage device. Boldface means user input. +As usual, ``#'' and ``@'' may be used to edit input. +.Pp +.Bd -unfilled -offset indent -compact +.Li \&>>> Ns Sy B/3 +.Li \&%% +.Li \&loading hk(0,0)boot +.Li \&Boot +.Li \&: Sy \&hk(0,0)drtest +.Li Test program for stand-alone up and hp driver +.Pp +.Li Debugging level (1=bse, 2=ecc, 3=bse+ecc)? +.Li Enter disk name [type(adapter,unit),\ e.g.\ hp(1,3)]? Sy hp(0,0) +.Li Device data: #cylinders=1024, #tracks=16, #sectors=32 +.Li Testing hp(0,0), chunk size is 16384 bytes. +.Em (chunk\ size\ is\ the\ number\ of\ bytes read per disk access) +.Li Start ...Make sure hp(0,0) is online +.Li \ ... +.Em (errors are reported as they occur) +.Li \ ... +.Em (...program restarts to allow checking other disks) +.Em (...to abort halt machine with \&^P) +.Ed +.Sh DIAGNOSTICS +The diagnostics are intended to be self explanatory. Note, however, that +the device number +in the diagnostic messages is identified as +.Em typeX +instead of +.Em type(a,u) +where +.Ar X +\&= a*8+u, e.g., hp(1,3) becomes hp11. +.Sh SEE ALSO +.Xr bad144 8 , +.Xr vax/format 8 +.Sh HISTORY +The +.Nm +command appeared in +.Bx 4.2 . +.Sh AUTHORS +.An Helge Skrivervik diff --git a/static/netbsd/man8/man8.vax/format.8 b/static/netbsd/man8/man8.vax/format.8 new file mode 100644 index 00000000..9cfd7040 --- /dev/null +++ b/static/netbsd/man8/man8.vax/format.8 @@ -0,0 +1,295 @@ +.\" $NetBSD: format.8,v 1.14 2017/07/03 21:31:00 wiz Exp $ +.\" +.\" Copyright (c) 1980, 1983, 1993 +.\" The Regents of the University of California. All rights reserved. +.\" +.\" Redistribution and use in source and binary forms, with or without +.\" modification, are permitted provided that the following conditions +.\" are met: +.\" 1. Redistributions of source code must retain the above copyright +.\" notice, this list of conditions and the following disclaimer. +.\" 2. Redistributions in binary form must reproduce the above copyright +.\" notice, this list of conditions and the following disclaimer in the +.\" documentation and/or other materials provided with the distribution. +.\" 3. Neither the name of the University nor the names of its contributors +.\" may be used to endorse or promote products derived from this software +.\" without specific prior written permission. +.\" +.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND +.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE +.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE +.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL +.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS +.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT +.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY +.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF +.\" SUCH DAMAGE. +.\" +.\" from: @(#)format.8 8.1 (Berkeley) 6/5/93 +.\" +.Dd February 17, 2017 +.Dt FORMAT 8 vax +.Os +.Sh NAME +.Nm format +.Nd how to format disk packs +.Sh DESCRIPTION +There are two ways to format disk packs. The simplest is to +use the +.Nm +program. +The alternative is to use the DEC standard formatting software which +operates under the DEC diagnostic supervisor. +This manual page describes the operation of +.Nm , +then concludes with some remarks about using the DEC formatter. +.Pp +.Nm +is a standalone program used to format and check disks prior to +constructing file systems. +In addition to the formatting operation, +.Nm +records any bad sectors encountered according to DEC standard 144. +Formatting is performed one track at a time by writing the appropriate +headers and a test pattern and then checking the sector by reading and +verifying the pattern, using the controller's ECC for error detection. +A sector is marked bad if an unrecoverable media error is detected, or +if a correctable ECC error too many bits in length is detected (such +errors are indicated as +.Dq ECC +in the summary printed upon completing the format operation). +After the entire disk has been formatted and checked, the total number +of errors are reported, any bad sectors and skip sectors are marked, +and a bad sector forwarding table is written to the disk in the first +five even numbered sectors of the last track. +It is also possible to reformat sections of the disk in units of +tracks. +.Nm +may be used on any +.Tn UNIBUS +or +.Tn MASSBUS +drive supported by the +.Em up +and +.Em hp +device drivers which uses 4-byte headers (everything except RP's). +.Pp +The test pattern used during the media check may be selected from one +of: 0xf00f (RH750 worst case), 0xec6d (media worst case), and 0xa5a5 +(alternating 1's and 0's). +Normally the media worst case pattern is used. +.Pp +.Nm +also has an option to perform an extended +.Dq severe burn-in , +which makes a number of passes using different patterns. +The number of passes can be selected at run time, up to a maximum of +48, with provision for additional passes or termination after the +preselected number of passes. +This test runs for many hours, depending on the disk and processor. +.Pp +Each time +.Nm +is run to format an entire disk, a completely new bad sector table is +generated based on errors encountered while formatting. +The device driver, however, will always attempt to read any existing +bad sector table when the device is first opened. +Thus, if a disk pack has never previously been formatted, or has been +formatted with different sectoring, five error messages will be +printed when the driver attempts to read the bad sector table; these +diagnostics should be ignored. +.Pp +Formatting a 400 megabyte disk on a +.Tn MASSBUS +disk controller usually takes about 20 minutes. +Formatting on a +.Tn UNIBUS +disk controller takes significantly longer. +For every hundredth cylinder formatted +.Nm +prints a message indicating the current cylinder being formatted. +(This message is just to reassure people that nothing is amiss.) +.Pp +.Nm +uses the standard notation of the standalone I/O library in +identifying a drive to be formatted. +A drive is specified as +.Em zz(x,y) , +where +.Em zz +refers to the controller type (either +.Em hp +or +.Em up ) , +.Em x +is the unit number of the drive; 8 times the +.Tn UNIBUS +or +.Tn MASSBUS +adaptor number plus the +.Tn MASSBUS +drive number or +.Tn UNIBUS +drive unit number; and +.Em y +is the file system partition on drive +.Em x +(this should always be 0). +For example, +.Dq hp(1,0) +indicates that drive 1 on +.Tn MASSBUS +adaptor 0 should be formatted; while +.Dq up(10,0) +indicates that +.Tn UNIBUS +drive 2 on +.Tn UNIBUS +adaptor 1 should be formatted. +.Pp +Before each formatting attempt, +.Nm +prompts the user in case debugging should be enabled in the +appropriate device driver. +A carriage return disables debugging information. +.Pp +.Nm +should be used prior to building file systems (with +.Xr newfs 8 +to ensure that all sectors with uncorrectable media errors are +remapped. +If a drive develops uncorrectable defects after formatting, either +.Xr bad144 8 +or +.Xr badsect 8 +should be able to avoid the bad sectors. +.Sh EXAMPLES +A sample run of +.Nm +is shown below. +In this example (using a +.Tn VAX-11/780 ) , +.Nm +is loaded from the console floppy; +on an 11/750 +.Nm +will be loaded from the root file system with +.Xr vax/boot 8 +following a +.Dq B/3 +command. +Boldface means user input. +As usual, +.Dq # +and +.Dq @ +may be used to edit input. +.Bd -literal -offset 0.5i +>>>\fBL FORMAT\fP + LOAD DONE, 00004400 BYTES LOADED +>>>\fBS 2\fP +Disk format/check utility +.sp +Enable debugging (0=none, 1=bse, 2=ecc, 3=bse+ecc)? \fB0\fP +Device to format? \fBhp(8,0)\fP +(\fIerror messages may occur as old bad sector table is read\fP) +Formatting drive hp0 on adaptor 1: verify (yes/no)? \fByes\fP +Device data: #cylinders=842, #tracks=20, #sectors=48 +Starting cylinder (0): +Starting track (0): +Ending cylinder (841): +Ending track (19): +Available test patterns are: +.Ed +.Bd -literal -offset 1.5i -compact +1 - (f00f) RH750 worst case +2 - (ec6d) media worst case +3 - (a5a5) alternating 1's and 0's +4 - (ffff) Severe burnin (up to 48 passes) +.Ed +.Bd -literal -offset 0.5i -compact +Pattern (one of the above, other to restart)? \fB2\fP +Maximum number of bit errors to allow for soft ECC (3): +Start formatting...make sure the drive is online + ... +(\fIsoft ecc's and other errors are reported as they occur\fP) + ... +(\fIif 4 write check errors were found, the program terminates like this...\fP) + ... +Errors: +Bad sector: 0 +Write check: 4 +Hard ECC: 0 +Other hard: 0 +Marked bad: 0 +Skipped: 0 +Total of 4 hard errors revectored. +Writing bad sector table at block 808272 +(\fI808272 is the block # of the first block in the bad sector table\fP) +Done +(\fI...program restarts to allow formatting other disks\fP) +(\fI...to abort halt machine with ^P\fP) +.Ed +.Sh DIAGNOSTICS +The diagnostics are intended to be self explanatory. +.Sh USING DEC SOFTWARE TO FORMAT +.Em Warning: These instructions are for people with 11/780 CPUs. +The steps needed for 11/750 or 11/730 CPU's are similar, but not +covered in detail here. +.Pp +The formatting procedures are different for each type of disk. +Listed here are the formatting procedures for RK07's, RP0X, and RM0X +disks. +.Pp +You should shut down UNIX and halt the machine to do any disk formatting. +Make certain you put in the pack you want formatted. +It is also a good idea to spin down or write protect the disks you +don't want to format, just in case. +.Ss Formatting an RK07 +Load the console floppy labeled, +.Dq RX11 VAX DSK LD DEV #1 +in the console disk drive, and type the following commands: +.Bd -literal -offset indent +>>>BOOT +DIAGNOSTIC SUPERVISOR. ZZ-ESSAA-X5.0-119 23-JAN-1980 12:44:40.03 +DS>ATTACH DW780 SBI DW0 3 5 +DS>ATTACH RK611 DMA +DS>ATTACH RK07 DW0 DMA0 +DS>SELECT DMA0 +DS>LOAD EVRAC +DS>START/SEC:PACKINIT +.Ed +.Ss Formatting an RP0X +Follow the above procedures except that the +ATTACH and SELECT lines should read: +.Bd -literal -offset indent +DS>ATTACH RH780 SBI RH0 8 5 +DS>ATTACH RP0X RH0 DBA0 (RP0X is, e.g., RP06) +DS>SELECT DBA0 +.Ed +.Pp +This is for drive 0 on mba0; use 9 instead of 8 for mba1, etc. +.Ss Formatting an RM0X +Follow the above procedures except that the +ATTACH and SELECT lines should read: +.Bd -literal -offset indent +DS>ATTACH RH780 SBI RH0 8 5 +DS>ATTACH RM0X RH0 DRA0 +DS>SELECT DRA0 +.Ed +.Pp +Don't forget to put your UNIX console floppy back in the floppy disk +drive. +.Sh SEE ALSO +.Xr bad144 8 , +.Xr badsect 8 , +.Xr newfs 8 +.Sh BUGS +An equivalent facility should be available which operates under a +running UNIX system. +.Pp +It should be possible to reformat or verify part or all of a disk, +then update the existing bad sector table. |