Technical article 114965

I have upgraded my controller from a 2940 to a 2940U2W and my now my server fails to find the root disk.

OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

I have upgraded my controller from a 2940 (alad) to a 2940U2W (blad), and now when I boot the server fails to find the root disk.

Cause

The "blad" driver for the 2940U2W needs to be installed as the primary root disk.

Solution

If you are using an AIC-7890 Adaptec chipset (AHA-2940U2W), then "blad325" should be the specified driver.

This driver can be obtained from Adaptec's website at:

http://www.adaptec.com/worldwide/support/supportindex.html

Select the drivers for the "Ultra2 Family." The driver is a self-extracting executable file, which will generate a Boot Time Loadable Driver (BTLD) disk.

This disk can be mounted on any OpenServer server with the command:

mount /dev/fd0 /mnt

You will then be able to see in more detail the available drivers.

The latest BIOS for this card is located at the following website:

http://www.adaptec.com/worldwide/common/search.html
Search for "2940U2W bios"

To install the driver, you can use the "installpkg" command at the root prompt and follow the instructions there to load the "blad325" driver before replacing the controller.

If, however, you have already replaced the controller, you can use either a set of Generic OpenServer 5.0.[56] Emergency Boot & Root floppies or the OpenServer 5.0.[56] Media Kit, which has support for the "blad325" driver.

If you have created your Generic Boot & Root Emergency floppies for OpenServer 5.0.[56], you can boot the server using:

Technical Article 104767, "Recover OpenServer 5 root filesystem after crash if backups, boot/root exist."

If you do not have the Emergency Boot & Root floppies, you can boot your server using the OpenServer 5.0.[56] Media Kit, the details of which can be provided by contacting your SCO Support provider.

At the # prompt, run the following commands to check the root filesystem, mount it and start a new shell with /mnt as the root directory.

# fsck -ofull -d /dev/hd0root
# mount /dev/hd0root /mnt
# /etc/chroot /mnt /bin/sh

Now, also mount the /stand filesystem to put your revised kernel in place:

# mount /dev/boot /stand

Run the "installpkg" command and insert your floppy disk as required. When prompted, type "Y" to make the "blad325" the default controller for your root disk.

This should update /etc/conf/cf.d/mscsi and /etc/conf/pack.d/blad files with the new driver information.

To re-link your kernel, run:
# /etc/conf/cf.d/link_unix -y

Afterwards, check that the kernel in /etc/conf/cf.d/unix has been copied to /stand. If not:

# cd /stand
# cp unix.old unix.orig
# cp unix unix.old
# cp /etc/conf/cf.d/unix .

Now, unmount the directories and exit the shell before re-booting to ensure your root filesystem is not corrupted.

# cd /
# umount /stand
# exit
# umount /mnt
# haltsys

Remove the floppy disk and the new root controller should now be your "blad" controller.

NOTE:      This process can be used for installing other SCSI controllers.

Check the BIOS settings of the Adaptec controller at boot time by pressing <Ctrl><A> when prompted.

See also

ta113363, "How do I install OpenServer 5.0.4 on an Adaptec 2940U2W with an IDE CD-ROM?"

ta104767, "Recover OpenServer 5 root filesystem after crash if backups, boot/root exist."

From the Xinuos technical article database, record 114965. Reproduced with permission. The original is at www.sco.com/ta/114965, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.