| Upgrade Information: Page Two |
IMPORTANT
PLEASE READ THIS NOTE CAREFULLY IF YOU INTEND TO PERFORM A NON-DESTRUCTIVE UPGRADE FROM SCO UnixWare 2.0.x to 2.1.x
This document was included in the SCO UnixWare Upgrade Kit SV507058 (if purchased from Fujitsu Computers Ltd.).
(Continued..)
To disable the Mylex BIOS
(This can be done at any time, and it does not need to be re-enabled after the upgrade is complete).
- Reboot the server.
- As it reboots press Alt-M when prompted (just after the Mylex logo and firmware version are displayed).
- The message: BIOS disabled. No drives installed is displayed and the system boot continues
All data on the system must be securely backed up in before starting the upgrade.
First Alternative - Disconnecting All Discs (except System Disc)
- Shut down the system, remove all discs except the system disc from the system cabinet, and power off any peripheral cabinet.
- Perform the upgrade, checking that the Non-Destructive option is offered. The message target not responding will be displayed - this does not affect installation.
- When the upgrade is complete, shut down the system, replace all the discs and power on any peripheral cabinets.
Second Alternative - Remove dak Driver
- Just before the upgrade, on UnixWare 2.0.x, log in as root and enter the command pkgrm dak
- Then carry out the upgrade. If you use an HBA diskette that contains
the dak driver, you must use the option
to Enter DCU - this takes you into
the Device Configuration Utility. From there:
- Select Hardware Device Configuration.
- Page down to the Mylex DAC960P entry
- Change the Y in the first field to N.
- Press F10 to exit to the main menu.
- Select Apply Changes and exit the DCU and continue with the installation. Make sure you are offered a Non-Destructive upgrade.
- When the upgrade installation is complete log in as root and add the Mylex driver from the HBA diskette by typing pkgadd -d /dev/rdsk/f0 and selecting dak from the list.
- Reboot the server and check that the kernel rebuilds without errors.
- Check that the Mylex disks are seen by the operating system and that the data on them is intact.
Servers with Non-System Disks Connected by powerARRAY or powerCACHE
The procedure is essentially similar to that adopted for systems with a Mylex controller, detailed above. This applies where the system disc is not connected through the powerARRAY. The problems experienced are:
If the powerARRAY BIOS is not disabled, then during the upgrade the CD-ROM is not accessible.
If the powerARRAY driver is installed from the HBA disc during UnixWare installation, the kernel does not rebuild correctly, and the system starts a cycle of repeated rebooting.
To disable the powerARRAY BIOS (this can be done at any time, and it does not need to be re-enabled after the upgrade is complete):
- Reboot from the SCU diskette.
- Select Execute AMISCU.
- From the main SCU menu select Change Configuration Settings and wait until all .CFG files are loaded.
- From the boards listed select ICL powerARRAY (or CACHE).
- In the menu displayed, select BIOS Address, press Enter, and from the list select Disabled.
- Press ESC twice to go back to the main menu, then select Save Configuration.
- When completed, select Exit and reboot the system.
To upgrade a system with powerARRAY where the system disc is not connected through the powerARRAY, proceed as follows:
- Just before the upgrade, on UnixWare 2.0.x, log in as root and execute the command pkgrm pwra.
- Then carry out the upgrade. Use the standard HBA diskette, and do not insert the powerARRAY HBA diskette during the installation. Make sure you are offered a non-destructive upgrade.
- When the installation is complete, log in as root and add the powerARRAY driver from the HBA diskette by typing pkgadd -d /dev/rdsk/f0 and selecting pwra from the list.
If downgrading from UnixWare 2.1 to UnixWare 2.0.3 for any reason, then re-install the V2L0I6 version of the pwra driver if it is not done automatically
- Reboot the server and check that the kernel rebuilds without errors.
- Check that the powerARRAY disks are seen by the operating system and that the data on them is intact.
At each system boot, you may see 'SCB' errors from the powerARRAY driver. The cause of these messages is under investigation as a separate issue, and the messages may safely be ignored.
(This document is in three parts, it is continued here).
