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