The notes in this chapter discuss the following topics:
Do not attempt to install DIGITAL UNIX Version 4.0E without first reading the notes appropriate to your processor in Chapter 3. Failure to read these notes can result in installation problems. Also, before you start your installation, be sure to review the hardware documentation that came with your system.
The following notes apply to the installation process in general.
To verify that you have installed all the correct elements from the
DIGITAL UNIX Version 4.0E software kit, check the DIGITAL UNIX
revision level that appears in the
/etc/motd
file. The correct version string is:
DIGITAL UNIX 4.0E
For information about disk space requirements, see
Appendix A,
Appendix B,
and
Section 8.27.
If you want to add optional subsets after you install
DIGITAL UNIX Version 4.0E, use the
df
command to determine free disk space in blocks.
Starting in DIGITAL UNIX Version 4.0D, a recommended disk partition table is available for 1 GB (for example, RZ26) and larger disks during a full text-based or graphical installation. You have the option of applying the recommended disk partition table or using your existing disk partition table when you choose to install the operating system onto a single disk. If your operating system is installed across multiple disks, this option will not be offered to you.
For single disk installations, you should choose the recommended disk partition table over the default partition table.
The recommended partition table creates the partitions listed in Table 2-1. Note that these partition sizes are the recommended sizes for Version 4.0E. They are subject to change in future releases as the size of DIGITAL UNIX continues to grow.
| Partition | Description |
a
|
The size of the
a
partition is 128 MB, regardless of the size of the disk.
For example, a 1 GB disk and a 4 GB disk would both have
a 128 MB
a
partition if you select the recommended disk partitions.
|
b
|
The size of the
b
partition is either its default value for a given disk or
128 MB, whichever is larger. For example, an RZ28 has a
default
b
partition size of 196 MB. This default size will be
maintained, instead of reducing it to 128 MB.
|
g
|
The size of the
g
partition is 700 MB, regardless of the size of the disk.
For example, a 1 GB disk and a 4 GB disk would both have
a 700 MB
g
partition if you select the recommended disk partitions.
Note that if you will be installing many layered products, this value may be too small. Also, if sufficient disk space is available, you may want to consider making this value larger for future expansion. |
h
|
The size of the
h
partition is whatever space is left over, unless it is
less than 100 MB, in which case the space is added to
the size of
g.
In the case of a 1 GB disk, approximately 45 MB
would be left over,
so it would be included in the size of
g
instead of
h.
|
Partitions
d,
e,
and
f
are evenly split between the size of
g
added to
h,
and they overlap
g
and
h.
If the disk has an existing partition table with
a,
b,
and
g
partitions each greater than 90% of their recommended sizes, then the
existing partition table is accepted as the recommended partition
table.
If you use
installupdate
to update an existing system, you will not be offered the new
partition sizes because the procedure updates the system on your
existing partitions. You may wish to adjust your disk partitions to
meet or exceed the recommendations in
Table 2-1
before you begin the update. If you have a small system disk, you
may want to migrate to a 1 GB or larger disk at this time.
A new item,
Inst_disklabel,
has been introduced in the Configuration Description
File (CDF) to support the recommended disk partition table.
(You can use CDFs to perform installation cloning as described in
Appendix C of the DIGITAL UNIX Version 4.0B
Installation Guide.)
The
Inst_disklabel
item has several attributes associated with it.
Table 2-2
lists these attributes.
| Attribute | Description |
name
|
A required attribute that specifies the software name of disk to which
the recommended partition will be applied (for example,
rz0)
|
a_size
|
The size of the
a
partition in 512-byte blocks
|
a_offset
|
The offset of the
a
partition (from block 0) in 512-byte blocks
|
b_size
|
The size of the
b
partition in 512-byte blocks
|
b_offset
|
The offset of the
b
partition (from block 0) in 512-byte blocks
|
c_size
|
The size of the
c
partition in 512-byte blocks
|
c_offset
|
The offset of the
c
partition (from block 0) in 512-byte blocks
|
d_size
|
The size of the
d
partition in 512-byte blocks
|
d_offset
|
The offset of the
d
partition (from block 0) in 512-byte blocks
|
e_size
|
The size of the
e
partition in 512-byte blocks
|
e_offset
|
The offset of the
e
partition (from block 0) in 512-byte blocks
|
f_size
|
The size of the
f
partition in 512-byte blocks
|
f_offset
|
The offset of the
f
partition (from block 0) in 512-byte blocks
|
g_size
|
The size of the
g
partition in 512-byte blocks
|
g_offset
|
The offset of the
g
partition (from block 0) in 512-byte blocks
|
h_size
|
The size of the
h
partition in 512-byte blocks
|
h_offset
|
The offset of the
h
partition (from block 0) in 512-byte blocks
|
When performing installation cloning, you can specify multiple
Inst_disklabel
items so that several disks can be repartitioned automatically during
the cloning process, based on the values contained within the
individual items.
The following example shows how an
Inst_disklabel
item might appear within a CDF file:
install:
_item=Inst_disklabel
name=rz1
a_size=262144
a_offset=0
b_size=262144
b_offset=262144
g_size=1090979
g_offset=524288
h_size=435593
h_offset=1615267
_action=create
To start a RIS installation on an AlphaServer 1200, 4000, 4100, 8200,
or 8400, you must no longer specify the
n
option with the
boot
console firmware command, as in the following example:
>>>
boot -fl n ewa0
If you specify the
n
option, the RIS installation kernel will panic. You can safely
initiate a RIS installation by omitting the
n
option:
>>>
boot ewa0
Sometimes the following error message is displayed during the installation of worldwide subsets and the installation procedure aborts:
/usr/sbin/setld: /usr/lbin/depord: arg list too long
This problem occurs when too many subsets are chosen and the shell runs out of memory during installation. You can work around this problem by choosing fewer subsets to install at first, and then installing additional subsets at a later time.
During the installation process, you may encounter the following benign message:
I/O error (errno 5) for block (
xxx
,
xxx
) on device
xxx
,
x
The installation will complete successfully and the message can be ignored.
The installation process may display the following messages during a RIS installation of some subsets:
Broken Pipe
The installation will complete successfully and the message can be ignored.
To update your DIGITAL UNIX operating system software to
Version 4.0E, you must use the
installupdate
utility or full installation procedures as described in the
Installation Guide.
Version 4.0E supports update installations from DIGITAL UNIX
Version 4.0B, Version 4.0C, and Version 4.0D. See the
DIGITAL UNIX Software Product Description
for more information about disk space requirements before executing
installupdate.
Note that the
-i
flag for the
installupdate
command will be retired in a future version of DIGITAL UNIX. See
Section 8.28
for more information.
The following sections apply to the update installation procedure.
The DDR database format has been updated in Version 4.0D to include previously unrecognized SCSI device types and IDE/ATAPI entries.
If you are updating from DIGITAL UNIX Version 4.0B or Version 4.0C to Version 4.0E, during the update installation process, the DDR database is converted to the new format, but the running kernel is still based on the older DDR database format. Hence, when the kernel is notified of the DDR update, it reports the apparent discrepancy in database formats by sending the following messages to the console:
DDR: Invalid Database Header DDR: Invalid Database Header
You can ignore these messages. At the end of the update
installation, a new kernel is built with the updated
ddr.mod
binary and the resulting kernel properly recognizes the database.
After the update installation, there should be no further warnings from the DDR subsystem, unless the system is booted with an older preupdate kernel. If this happens, the kernel sends the same messages to the console and indicates that it is using the defaults for each device.
This problem does not occur if you are updating from DIGITAL UNIX Version 4.0D to Version 4.0E.
To protect your data on AdvFS file domains, perform the following
procedure on them before you update your operating system to
Version 4.0E. All steps in the procedure must be executed by a user
with
root
privileges:
shutdown
command to bring the system to single-user mode.
umount
command to unmount all local file systems.
verify
utility on each local file system and if there are problems with the
file systems, correct them before going further.
mount
command to mount all of the verified local file systems.
quotacheck
command to fix the quotas on the mounted local file systems. If there
are problems running
quotacheck
on a local file system, you may have to edit the
/etc/fstab
file to fix the problem.
After successfully completing these steps, you can update your system. DIGITAL strongly recommends that you fix any problems before you update.
When installing the AdvFS Advanced Utilities Version 4.0E into a DMS software environment, subset AFAADVDAEMON435 may fail with the following error:
Loading 1 of 1 subset(s).... awk: Cannot find or open file ./etc/services.
The source line number is 2.
Advanced File System Daemon, v4.0e, r435 Copying from /mnt/AFA435/kit (disk) Verifying
1 of 1 subset(s) installed successfully.
Backing up ./etc/services to ./etc/services.advfsd.back.... cp: ./etc/services: No such file or directory Backup failed. Root filesystem is full. ./etc/services file not modified.
Aborting installation.... setld: "Advanced File System Daemon, v4.0e, r435" (AFAADVDAEMON435) failed in subset control program (POST_L).
If this occurs, select the DMU option
c
(CONFIGURE software environments) to
configure the target software environment, and then reinstall the failed
daemon subset.
The PATHWORKS product has been added to the list of layered products that will halt an update installation if detected during the analysis phase of the update. If the update installation detects the PATHWORKS product, it will output a message and exit without modifying the system. In order to complete the update installation, you must manually remove the PATHWORKS product. Refer to section 2.8.2.1 of the Installation Guide for details about layered products that halt the update installation and how to remove those products.
The following sections provide information on installing DIGITAL UNIX Server Extensions.
If you install the Chinese subsets from a RIS server, the following error may occur:
Common Chinese Unicode Support
Copying from
server-name
(inet)
setld: cannot access server mapping (rcp: ris3.alpha/rp_mapping: No such file or directory)
setld: Load from
server-name
failed, subset IOSZHUCSBASE425
Verifying setld: There were verification errors for "Common Chinese Unicode Support (IOSZHUCSBASE425)
This error causes the system to abort the installation process. The problem may happen in other Chinese subsets also.
The error occurs because of the large number of software subsets in the Worldwide kit.
To avoid this problem, create a RIS area with fewer subsets or Chinese subsets only. To do this, choose option 1 from the following menu when installing subsets to the RIS area:
Choose one of the following options:
1) Extract software from [kit location] 2) Create symbolic link to [kit location]
Enter your choice:
Do not choose to extract all software subsets; only extract those subsets that are necessary for installation.