1.\" $NetBSD: hp.4,v 1.10 2002/01/15 02:08:10 wiz Exp $ 2.\" 3.\" Copyright (c) 1991, 1993, 19801988 4.\" The Regents of the University of California. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by the University of 17.\" California, Berkeley and its contributors. 18.\" 4. Neither the name of the University nor the names of its contributors 19.\" may be used to endorse or promote products derived from this software 20.\" without specific prior written permission. 21.\" 22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 25.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 32.\" SUCH DAMAGE. 33.\" 34.\" from: @(#)hp.4 8.1 (Berkeley) 6/5/93 35.\" 36.Dd June 5, 1993 37.Dt HP 4 vax 38.Os 39.Sh NAME 40.Nm hp 41.Nd 42.Tn MASSBUS 43disk interface 44.Sh SYNOPSIS 45.Cd "hp0 at mba0 drive 0" 46.Cd "hp* at mba? drive ?" 47.Sh DESCRIPTION 48The 49.Nm hp 50driver 51is a generic Massbus disk driver which handles the standard 52.Tn DEC 53controllers. 54It is typical of a block-device disk driver; block 55.Tn I/O 56is 57described in 58.Xr physio 4 . 59.Pp 60The script 61.Xr MAKEDEV 8 62should be used to create the special files; if a special file 63needs to be created by hand consult 64.Xr mknod 8 . 65It is recommended as a security precaution to not create special files 66for devices which may never be installed. 67.Pp 68The first sector of each disk contains both a first-stage bootstrap program 69and a disk label containing geometry information and partition layouts (see 70.Xr disklabel 5 . 71This sector is normally write-protected, and disk-to-disk copies should 72avoid copying this sector. 73The label may be updated with 74.Xr disklabel 8 , 75which can also be used to write-enable and write-disable the sector. 76The next 15 sectors contain a second-stage bootstrap program. 77.Sh DISK SUPPORT 78During autoconfiguration or whenever a drive comes on line for the first time, 79or when a drive is opened after all partitions are closed, 80the first sector of the drive is examined for a disk label. 81If a label is found, the geometry of the drive and the partition tables 82are taken from it. 83If no label is found, a fake label is created by the driver, enough 84so that a real label can be written. 85.Pp 86The hp?a partition is normally used for the root file system, 87the hp?b partition as a paging area, 88and the hp?c partition for pack-pack copying (it maps the entire disk). 89On disks larger than about 205 Megabytes, the hp?h partition 90is inserted prior to the hp?d or hp?g partition; 91the hp?g partition then maps the remainder of the pack. 92.Sh FILES 93.Bl -tag -width /dev/rhp[0-7][a-h] -compact 94.It Pa /dev/hp[0-7][a-h] 95block files 96.It Pa /dev/rhp[0-7][a-h] 97raw files 98.El 99.Sh DIAGNOSTICS 100.Bl -diag 101.It "hp%d%c: hard error %sing fsbn %d [of %d-%d] (hp%d bn %d cn %d tn %d sn %d) mbsr=%b er1=%b er2=%b." 102An unrecoverable error occurred during transfer of the specified 103filesystem block number, 104which is a logical block number on the indicated partition. 105If the transfer involved multiple blocks, the block range is printed as well. 106The parenthesized fields list the actual disk sector number 107relative to the beginning of the drive, 108as well as the cylinder, track and sector number of the block. 109The 110.Tn MASSBUS 111status register is printed in hexadecimal and 112with the error bits decoded if any error bits other than 113.Tn MBEXC 114and 115.Tn DTABT 116are set. In any case the contents of the two error registers are also printed 117in octal and symbolically with bits decoded. 118(Note that er2 is what old 119.Tn RP06 120manuals would call 121.Tn RPER3 ; 122the terminology 123is that of the 124.Tn RM 125disks). 126The error was either unrecoverable, or a large number of retry attempts 127(including offset positioning and drive recalibration) could not 128recover the error. 129.Pp 130.It "hp%d%c: soft ecc reading fsbn %d [of %d-%d] (hp%d bn %d cn %d tn %d sn %d)." 131A recoverable 132.Tn ECC 133error occurred on the 134specified sector of the specified disk partition. 135If the transfer involved multiple blocks, the block range is printed as well. 136The parenthesized fields list the actual disk sector number 137relative to the beginning of the drive, 138as well as the cylinder, track and sector number of the block. 139This happens normally 140a few times a week. If it happens more frequently than 141this the sectors where the errors are occurring should be checked to see 142if certain cylinders on the pack, spots on the carriage of the drive 143or heads are indicated. 144.Pp 145.El 146.Sh SEE ALSO 147.Xr physio 4 , 148.Xr up 4 , 149.Xr disklabel 5 , 150.Xr MAKEDEV 8 , 151.Xr disklabel 8 , 152.Xr mknod 8 153.Sh HISTORY 154The 155.Nm 156driver appeared in 157.Bx 4.0 . 158.br 159A new 160.Nm 161driver showed up in 162.Nx 1.2 . 163.Sh BUGS 164.Tn DEC Ns -standard 165.Xr bad144 8 166bad-block handling should be used. 167.Pp 168.Tn DEC Ns -standard 169error logging should be supported. 170.Pp 171A program to analyze the logged error information (even in its 172present reduced form) is needed. 173