1.\" $NetBSD: up.4,v 1.10 2002/01/15 02:10:51 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: @(#)up.4 8.1 (Berkeley) 6/5/93 35.\" 36.Dd June 5, 1993 37.Dt UP 4 vax 38.Os 39.Sh NAME 40.Nm up 41.Nd unibus storage module controller/disk drives 42.Sh SYNOPSIS 43.Cd "sc0 at uba? csr 0176700 vector upintr 44.Cd "up0 at sc0 drive 0" 45.Sh DESCRIPTION 46NOTE: This driver has not been ported from 47.Bx 4.4 48yet. 49.Pp 50This is a generic 51.Tn UNIBUS 52storage module disk driver. 53It is specifically designed to work with the 54Emulex 55.Tn SC-21 56and 57.Tn SC-31 58controllers. 59It can be easily 60adapted to other controllers (although bootstrapping will 61not necessarily be directly possible.) 62.Pp 63The script 64.Xr MAKEDEV 8 65should be used to create the 66.Nm up 67special files; consult 68.Xr mknod 8 69if a special file needs to be made manually. 70It is recommended as a security precaution to not create special files 71for devices which may never be installed. 72.Sh DISK SUPPORT 73The driver interrogates the controller's holding register 74to determine the type of drive attached. The driver recognizes 75seven different drives: 76.Tn CDC 779762, 78.Tn CDC 799766, 80.Tn AMPEX DM Ns 980 , 81.Tn AMPEX 829300, 83.Tn AMPEX 84Capricorn, 85.Tn FUJITSU 86160, and 87.Tn FUJITSU 88Eagle 89(the Eagle is not supported by the SC-21). 90.Pp 91Special file names begin with 92.Sq Li up 93and 94.Sq Li rup 95for the block and character files respectively. The second 96component of the name, a drive unit number in the range of zero to 97seven, is represented by a 98.Sq Li ? 99in the disk layouts below. The last component of the name, the 100file system partition, is 101designated by a letter from 102.Sq Li a 103to 104.Sq Li h 105which also corresponds to a minor device number set: zero to seven, 106eight to 15, 16 to 23 and so forth for drive zero, drive two and drive 107three respectively (see 108.Xr physio 4 ) . 109The location and size (in 512 byte sectors) of the 110partitions for the above drives: 111.Bl -column header diskx undefined length 112.Tn CDC No 9762 partitions 113.Sy disk start length cyls 114 hp?a 0 15884 0-99 115 hp?b 16000 33440 100-309 116 hp?c 0 131680 0-822 117 hp?d 49600 15884 309-408 118 hp?e 65440 55936 409-758 119 hp?f 121440 10080 759-822 120 hp?g 49600 82080 309-822 121.Pp 122.Tn CDC No 9766 300M drive partitions 123.Sy disk start length cyl 124 up?a 0 15884 0-26 125 up?b 16416 33440 27-81 126 up?c 0 500384 0-822 127 up?d 341696 15884 562-588 128 up?e 358112 55936 589-680 129 up?f 414048 861760 681-822 130 up?g 341696 158528 562-822 131 up?h 49856 291346 82-561 132.Pp 133.Tn AMPEX DM Ns No 980 partitions 134.Sy disk start length cyls 135 hp?a 0 15884 0-99 136 hp?b 16000 33440 100-309 137 hp?c 0 131680 0-822 138 hp?d 49600 15884 309-408 139 hp?e 65440 55936 409-758 140 hp?f 121440 10080 759-822 141 hp?g 49600 82080 309-822 142.Pp 143.Tn AMPEX No 9300 300M drive partitions 144.Sy disk start length cyl 145 up?a 0 15884 0-26 146 up?b 16416 33440 27-81 147 up?c 0 495520 0-814 148 up?d 341696 15884 562-588 149 up?e 358112 55936 589-680 150 up?f 414048 81312 681-814 151 up?g 341696 153664 562-814 152 up?h 49856 291346 82-561 153.Pp 154.Tn AMPEX No Capricorn 330M drive partitions 155.Sy disk start length cyl 156 hp?a 0 15884 0-31 157 hp?b 16384 33440 32-97 158 hp?c 0 524288 0-1023 159 hp?d 342016 15884 668-699 160 hp?e 358400 55936 700-809 161 hp?f 414720 109408 810-1023 162 hp?g 342016 182112 668-1023 163 hp?h 50176 291346 98-667 164.Pp 165.Tn FUJITSU No 160M drive partitions 166.Sy disk start length cyl 167 up?a 0 15884 0-49 168 up?b 16000 33440 50-154 169 up?c 0 263360 0-822 170 up?d 49600 15884 155-204 171 up?e 65600 55936 205-379 172 up?f 121600 141600 380-822 173 up?g 49600 213600 155-822 174.Pp 175.Tn FUJITSU No Eagle partitions 176.Sy disk start length cyls 177 hp?a 0 15884 0-16 178 hp?b 16320 66880 17-86 179 hp?c 0 808320 0-841 180 hp?d 375360 15884 391-407 181 hp?e 391680 55936 408-727 182 hp?f 698880 109248 728-841 183 hp?g 375360 432768 391-841 184 hp?h 83520 291346 87-390 185.El 186.Pp 187The up?a partition is normally used for the root file system, 188the up?b partition as a paging area, 189and the up?c partition for pack-pack copying (it maps the entire disk). 190On 160M drives the up?g partition maps the rest of the pack. 191On other drives both up?g and up?h are used to map the 192remaining cylinders. 193.Sh FILES 194.Bl -tag -width Pa -compact 195.It Pa /dev/up[0-7][a-h] 196block files 197.It Pa /dev/rup[0-7][a-h] 198raw files 199.El 200.Sh DIAGNOSTICS 201.Bl -diag 202.It "up%d%c: hard error %sing fsbn %d[-%d] cs2=%b er1=%b er2=%b." 203An unrecoverable error occurred during transfer of the specified 204filesystem block number(s), 205which are logical block numbers on the indicated partition. 206The contents of the cs2, er1 and er2 registers are printed 207in octal and symbolically with bits decoded. 208The error was either unrecoverable, or a large number of retry attempts 209(including offset positioning and drive recalibration) could not 210recover the error. 211.Pp 212.It "up%d: write locked." 213The write protect switch was set on the drive 214when a write was attempted. The write operation is not recoverable. 215.Pp 216.It "up%d: not ready." 217The drive was spun down or off line when it was 218accessed. The i/o operation is not recoverable. 219.Pp 220.It "up%d: not ready (flakey)." 221The drive was not ready, but after 222printing the message about being not ready (which takes a fraction 223of a second) was ready. The operation is recovered if no further 224errors occur. 225.Pp 226.It "up%d%c: soft ecc reading fsbn %d[-%d]." 227A recoverable ECC error occurred on the 228specified sector of the specified disk partition. 229This happens normally 230a few times a week. If it happens more frequently than 231this the sectors where the errors are occurring should be checked to see 232if certain cylinders on the pack, spots on the carriage of the drive 233or heads are indicated. 234.Pp 235.It "sc%d: lost interrupt." 236A timer watching the controller detecting 237no interrupt for an extended period while an operation was outstanding. 238This indicates a hardware or software failure. There is currently a 239hardware/software problem with spinning down drives while they are 240being accessed which causes this error to occur. 241The error causes a 242.Tn UNIBUS 243reset, and retry of the pending operations. 244If the controller continues to lose interrupts, this error will recur 245a few seconds later. 246.El 247.Sh SEE ALSO 248.Xr hk 4 , 249.Xr hp 4 , 250.Xr uda 4 251.Sh HISTORY 252The 253.Nm up 254driver appeared in 255.Bx 4.0 . 256.Sh BUGS 257A program to analyze the logged error information (even in its 258present reduced form) is needed. 259.Pp 260The partition tables for the file systems should be read off of each 261pack, as they are never quite what any single installation would prefer, 262and this would make packs more portable. 263