Upgrading a non-primary hard disk

You can protect any filesystem on a non-primary hard disk by selecting the Upgrade installation type or the Preserve option for setting up the secondary hard disk. If neither of these options is available, or if you do not select either one, select the Defer disk setup option during the installation, or remove the additional hard disks before beginning the installation.

If you select Preserve for the second hard disk, you must run divvy for that disk after the installation is complete. Within divvy, select n and name the preserved partitions, then exit. Then, run mkdev fs, as described in step 4.

Follow the numbered procedure in this section for any non-primary disk that you plan to remove before the installation, or for which you plan to select the Defer disk setup option.

1. Before the installation, run fdisk(ADM) for each affected hard disk. For example, for the second hard disk, enter:
   
   fdisk -f /dev/rhd10

   Enter 1 at the main fdisk menu. Record the numbers of the fdisk partitions that hold your UNIX filesystems, then exit fdisk.
   

2. Also before the installation, run divvy(ADM) for each affected partition and record the information. For example, for the active partition on the second hard disk, enter:
   
   /etc/divvy /dev/hd1a

   Copy the information from your screen into the following table:

   Secondary Hard Disk Filesystems

   Name	Type	New FS	#	First Block	Last Block

   Exit divvy by selecting quit, then exit.

3. After you install the SCO OpenServer system, follow the instructions for using mkdev hd in ``Adding hard disks''. (mkdev hd runs fdisk and divvy.) During mkdev hd, make sure that:

   • You accept the default size for the badtrk table.

   • The partition numbers in the fdisk partition table match those you recorded before the installation.

   • The information you recorded in the ``Secondary Hard Disk Filesystems'' table is in the new divvy table.

   • You select n and name each filesystem. (The divvy utility now creates device nodes for the divisions if they do not already exist, so you must change the divvy-generated names to match the original names.)

   ---

   CAUTION: Do not select c within divvy. Doing so destroys the contents of the selected filesystem. Only select c if you have a complete backup of the filesystem, and you want to remake the filesystem into a different format. You must then restore all the data to that filesystem.

   ---

4. For each affected filesystem, enter:
   
   mkdev fs

   Select option 1 to add a new filesystem. When prompted, enter the full pathname of the device from /dev. For example, to add a filesystem called u, enter /dev/u.

   When prompted, enter the name of the directory on which the filesystem is mounted. For example, a filesystem called u is usually mounted on the directory /u.
   

   Specify how you want the filesystem mounted when the system enters multiuser mode:

   • mount automatically at system startup (select 1)

   • mount only at the request of the system administrator (select 2)

   • prompt for mount choice at system startup (select 3)

   When asked whether or not users will be allowed to mount the filesystem, it is usual to respond n for security reasons. (In any case, users running backups must have both sysadmin and backup authorizations. See ``Assigning subsystem authorizations''.)

5. Exit mkdev fs.

6. If you want to mount the filesystem now, enter the following command (/u is used in this example):
   
   mount /dev/u /u