Problem
While attempting an in-place upgrade from SCO OpenServer 5.0.2 to SCO OpenServer 5.0.5, the upgrade halts with the following error message just after entering the license details:
There is no /etc/default/boot file present in the boot filesystem. You must boot your old system and create this file with DEFBOOTSTR the root entry defined. See man page boot (F). Cannot determine the root filesystem location.
Cause
As part of the in-place upgrade, when booting off the new installation media, the installation attempts to mount the boot filesystem (/stand) from the hard disk, and then read the DEFBOOTSTR entry in /stand/etc/default/boot in order to determine the location of the root filesystem.
There may be various causes of this message, including (as the message implies) an absence of the /stand/etc/default/boot file on the hard disk (in which case the suggested action within the message should be taken).
However, this is quite a generic message reported when a check on
the existence of this file fails. This could potentially occur in
a variety of circumstances. One such circumstance is described here
on a system with multiple host adapters.The installation scripts may fail to locate the root disk, instead locating a data disk (on a different disk controller) and assume that this is the root disk as part of their polling mechanism. They then may mount the filesystem on division 0 (which would be boot on the root disk) and check for etc/default/boot within this filesystem (which will fail if it is not the real root disk).
This has been seen on a system with an Adaptec (alad) based controller with the root disk and a CD-ROM connected, and a Mylex controller with data disks (non-root) attached (3 x RAID 5 system drives).
Solution
To avoid possible misrecognition of the root disk, use an explicit bootstring that specifies the location of the root disk (and the CD-ROM for completeness) when booting from the newer operating system media.
For the example system described above with Adaptec and Mylex controllers, at the Boot: prompt enter the following:
defbootstr Sdsk=alad(0,0,0) Srom=alad(0,5,0)This states that the root disk is on the Adaptec controller at SCSI ID 0 (first instance of controller and first channel/bus), and the CD-ROM is also on the Adaptec controller at SCSI ID 5.
No reference is made to the data disks connected to the Mylex controller as they are not involved in the upgrade (but their configuration will remain as they are statically defined with the kernel link kit already).
A similar effect could be obtained by physically disconnecting or offlining additional data disks for the period of the upgrade so that the only disk to be detected by the installation scripts would be the root disk.
NOTES: This is just one possible cause of this issue. For details on how
to gather further debug information from the upgrade installation
scripts, see ta110414, "How can I generate and save a debug logfile
for an OpenServer 5 installation or upgrade?". See also
SCO OpenServer 5.0.5 Release Notes, page 43SCO OpenServer Handbookboot(HW) man pageta105682, "'There is no default bootstring entry in /etc/default/boot' when upgrading from OpenServer 5.0.2 to 5.0.4."
ta110414, "How can I generate and save a debug logfile for an SCO OpenServer 5 installation or upgrade?"