How do I add a 2nd or 3rd disk drive to my Sco Unixware 7 system?

It is fairly straightforward to add another drive to a UnixWare 7/OpenSever 6 system,

thanks to the command 'diskadd.' You don't need to do anything to the system before
you install the drive. After shutting down, installed the drive with the correct
termination, and jumpered it for the correct scsi id and auto-spinup, you can restore
power and run your HBA BIOS setup program to match your HBA to your drive
capabilities (on an Adaptec scsi HBA like a 2940UW, you would press CTRL-A
during POST). Then boot into multiuser mode, login as root, and run:

diskadd c0b0t1d0

The diskadd program will take you through:

fdisk -- Is invoked to allow you to create a partition

disksetup -- Is run which helps you to do the following:
* Surface Analysis (not necessary for scsi drives)
* Create the VTOC (Volume Table of Contents)
* Write the bad track and bad sector table to the drive
* Create the layout of slices on the new drive (up to 13 of them)
* Use mkfs to make filesystems
* Creates the lost+found directories automatically in any filesystem.
* Creates the mount point directories.
* Mounts the filesystems.
* Updates the vfstab file.

The 'disksetup' program walks you through all the steps via a simple
series of questions. It is well written and works smoothly. You will
need to know how many MB you want each slice to be, and what they
will be called, and that's about it.

*********************
Some caveats:

1) UnixWare 7/OpenServer 6 uses a slice representation like

c0b0t0d0xx for almost everything that needs a drive named.

2) That naming has no partition information in it !!

So you can't specify what partition you mean when you type
c0b0t0d0s4 to refer to a slice.

3) The only way for UnixWare 7/OpenServer 6 to know what partition

contains slice 4, is for it to mark that partition active.

4) Thus you can only use one partition for filesystems on each
hard drive. And that one partition needs to be active for
the system to know where to go. The only exception is
when you use a whole additional partition for one filesystem
and no slices (call it /dev/dsk/c#b#t#d#p# <-- no s).
 5) In the active Unix partition, you can have 183 slices. Diskadd
only helps you create up to 13. Any additional slices need to be
hand created. On the 2nd drive with scsi id=1, the slices would
be 1 through b8 (because slices are listed in hex):

/dev/rdsk/c0b0t1d0s1
/dev/rdsk/c0b0t1d0s2
/dev/rdsk/c0b0t1d0s3
...
/dev/rdsk/c0b0t1d0sb6
/dev/rdsk/c0b0t1d0sb7 <--- Slice #'s are in hex, b7 = 183.

I couldn't get 184 to work; so for now, I'll claim 183.

6) The situation where you would have more than one partition on
another drive is where you need a raw partition for Database
storage or you are using the trick of one filesystem taking up a
whole partition with no slices in it.

Information derived from: - http://www.zenez.com/tmp/ou8faqz/cache/89.html

Additional Information regarding naming of disks in SCO unixware:

SCSI and non-SCSI disks

Disk device filenames have either of the two following forms:

/dev/[r]dsk/cCbBtTdDsS

/dev/[r]dsk/cCbBtTdDpP

[r]dsk
/rdsk denotes a raw (character) device; /dsk indicates a block device.

cC
C is the occurrence of the host adapter board or IDE controller in the system (that
is, card number). C can range from 0 to 31.

bB
B is the HBA bus number, ranging from 0 to 7 (dependent on the add-on adapter).
This is always 0 for IDE disks.

tT
T is the SCSI target controller number (ID). The value of T can range from 0 to 31.
The first IDE disk is target 0, and the second is target 1.

dD
D is the logical unit number of the disk device, ranging from 0 to 31. This is always
0 for IDE disks.

sS
 S is the disk slice number, ranging from 0 to b7 (hex).

pP
P is the fdisk(1M) partition number. P can range from 0 to 4, to specify an entry in
the fdisk partition table. The p0 node corresponds to the whole disk, the p1 to p4
nodes correspond to partitions as they are displayed by the fdisk command.

Man pages of Programs called by the “diskadd” program.

FDISK
fdisk [argument]
Description
This command is used to create and modify the partition table that is put in the first
sector of the hard disk. This table is used by the UnixWare system and other operating
systems (for example, MS-DOS) and by the first-stage bootstrap to identify parts of
the disk reserved for different operating systems, and to identify the partition
containing the second-stage bootstrap (the active partition). The optional argument
can be used to specify the raw device associated with the hard disk; the default value
is the raw device associated with the boot hard disk.

The program displays the partition table as it exists on the disk, and then presents a
menu allowing you to modify the table. The menu, questions, warnings, and error
messages are intended to be self-explanatory.

If there is no partition table on the disk, you are given the options to create a default
partition or to specify the initial table values. The default partitioning allows 100% of
the disk for the UnixWare system, and makes the UNIX system partition active. In
either case, when the initial table is created, fdisk also writes out the first-stage
bootstrap code (see sd01(7)) along with the partition table. After the initial table is
created, only the table is changed; the bootstrap is not modified.
Menu options
The following are the menu options given by the fdisk program:

Create a partition
Allows you to create a new partition. The maximum number of partitions is 4. The
program will prompt for the type of partition you want to make. You can select from
the following types:

1=UNIX System
2=pre-5.0DOS
3=post-4.0DOS
4=System
5=other

fdisk will then ask for the size of the partition as a percentage of the disk. For the
UnixWare operating system, the minimum UNIX system disk partition size is 60 MB
for the first disk and 40 MB for the second disk. You may also enter the letter c at this
point, and the program will ask for the starting cylinder number and size of the
partition in cylinders.
 Note: If you select type 4, (System), to create a System Configuration Partition,
fdisk will not prompt you for a starting cylinder number because the System
Configuration Partition is required to start at cylinder 0.

If a c is not entered, the program will determine the starting cylinder number where
the partition will fit. In either case, if the partition would overlap an existing partition,
or will not fit, a message is displayed and the program returns to the original menu.

Change Active (Boot from) partition

Allows you to specify the partition where the first-stage bootstrap will look for the
second-stage bootstrap, otherwise known as the active partition.

Delete a partition
Allows you to delete a previously created partition. Note that this will destroy all
data in that partition. Use this option with extreme caution.

Overwrite system master boot code

Overwrites the in-core boot code portion of the boot sector with the UNIX system
version of the master boot code. You will need to perform an update, using fdisk's
update menu option, to have the master boot code written to the disk. You should use
the overwrite menu option if you have had OS/2 installed on the disk previously,
because the OS/2 master boot will not boot UNIX. However, the overwrite option is
not necessary for machines that have had MS-DOS and then OS/2 installed on them.

Update
Writes the new version of the table created during this session with fdisk out to the
hard disk, and exits the program.

Exit
Exits without modifying the partition table.

Errors
Most messages will be self-explanatory. The following may appear immediately after
starting the program:

fdisk: cannot open <device>

This indicates that the device name argument is not valid.

fdisk: unable to get device parameters for device <device>

This indicates a problem with the configuration of the hard disk, or an error in the
hard disk driver.

fdisk: error reading partition table

This indicates that some error occurred when trying initially to read the hard disk.
This could be a problem with the hard disk controller or driver, or with the
configuration of the hard disk.

This message may appear after selecting the Update option from the menu.
fdisk: error writing boot record
This indicates that some error occurred when trying to write the new partition table
out to the hard disk. This could be a problem with the hard disk controller, the disk
itself, the driver, or the configuration of the hard disk.

Files

/dev/rdsk/cCbBtTdDs0

References
disk(7), vtoc(7)
Notices
Cautions
Use caution when using the fdisk command. If you select the option to delete a
partition, the data on that partition is lost and cannot be retrieved. If you delete a
partition accidentally, you will need a tape or disk backup to restore the lost data.
Compatibility
fdisk is compatible with MS-DOS Versions 3.2, 3.3, 4.0, and 5.0. Partitions set up
using the MS-DOS 4.0 fdisk command that are greater than 32 MB will appear in the
UNIX system display as other. Partitions can be created at sizes greater than 32 MB
for MS-DOS 5.0, and appear correctly as DOS partitions. Partitions created with MS-
DOS at any release level that are less than 32 MB will appear correctly as DOS
partitions.

The label of a created partition will be either DOS for MS-DOS 5.0 partitions or pre-
5.0DOS for any version of MS-DOS lower than 5.0. Note, however, that the version
of the partition can be pre-5.0DOS even when the operating system in use is MS-DOS
5.0. Therefore, do not depend on the partition label to determine which release of MS-
DOS is running.

The DOS 4.01 fdisk program assumes it can store diagnostic information in cylinder
1020 on the hard disk. If a UNIX system partition is created that uses cylinder 1020,
DOS 4.01 fdisk will be unable to create a DOS partition. Therefore, you must either
create the UNIX system partition at the front of the disk so that cylinder 1020 is not
used, or create the DOS partition using the UNIX System fdisk (not DOS fdisk) and
never delete it.

When setting up a DOS 4.01 partition on the hard disk to co-reside with a UNIX
partition that has already been set up, do not allow fdisk to create the largest possible
partition and make it active (as the fdisk prompt requests). Instead, you should
manually set it up to line up against the UNIX partition. Note that this applies to when
you boots DOS 4.01 from floppy disk (not from within UNIX) and runs fdisk.

Also note that there was a previous version of the fdisk command, intended for use
with the UNIX System bkrs (backup/restore) utility. The current version of fdisk is
used only for partitioning disks.
As noted in the section describing fdisk's menu options, you need to use the overwrite
option when installing UNIX on a disk that has had OS/2 installed on it. The
Overwrite system master boot code option overwrites the in-core boot code portion of
the boot sector with the UNIX system master boot code. This operation is necessary
because the OS/2 boot code will not boot UNIX. The overwrite is not necessary,
however, on systems that had MS-DOS and then OS/2 installed on them. To complete
the overwrite, you need to use the update menu option in fdisk.

MS-DOS and certain other operating systems do not support disk partitions starting
beyond or ending above cylinder 1023. These operating systems may not be able to
activate a partition that starts beyond cylinder 1023. If a partition starts before
cylinder 1023 and ends after cylinder 1023, the operating system may not be able to
use the disk space above cylinder 1023. If the partition table is updated via the DOS
fdisk command, inappropriate information may be recorded for these partitions. If this
occurs, you may not be able to boot from these partitions again. This could also occur
with certain other operating systems.

MKFS
mkfs(1M)
mkfs -- construct a filesystem (generic)

Synopsis
mkfs [-F FSType] [-V] [-m] [current_options] [-o specific_options]
special size [operands]
Description
mkfs constructs a filesystem by writing on the special file; special must be the first
argument. The filesystem is created based on the FSType, specific_options and
operands specified on the command line. mkfs waits 10 seconds before starting to
construct the filesystem. During this time the command can be aborted by entering a
delete (<Del>).

operands are FSType-specific and the FSType specific manual page of mkfs should
be consulted for a detailed description.

current_options are options supported by the s5-specific module of mkfs. Other

FSTypes do not necessarily support these options. specific_options indicate
suboptions specified in a comma-separated list of suboptions and/or keyword-attribute
pairs for interpretation by the FSType-specific module of the command.

The options are:

-F
Specify the FSType to be constructed. The FSType should either be specified here
or be determinable from /etc/vfstab by matching the special with an entry in the table.

-V
Echo the complete command line, but do not execute the command. The command
line is generated by using the options and arguments provided by the user and adding
to them information derived from /etc/vfstab. This option should be used to verify and
validate the command line.

-m
Return the command line which was used to create the filesystem. The filesystem
must already exist. This option provides a means of determining the command used in
constructing the filesystem. It cannot be used with current_options, specific_options,
or operands. It must be invoked by itself.

-o
Specify FSType-specific options.

special
mkfs constructs a filesystem by writing on the special file.

size
Specify the number of logical 512 byte sectors in the filesystem. The largest
filesystem size is determined by the FSType.

Files

/etc/vfstab
list of default parameters for each filesystem

Other References:

SCO Unixware 7 Documentation: http://uw714doc.sco.com/en/Navpages/index.html