Technical article 127887

emergency_disk fails to build a kernel in OpenServer6 Definitive D1M0

OpenServer Definitive 2018OpenServer 6

Written

Problem

Trying to build emergency media for OpenServer6 Definitive D1M0, using the emergency_disk command fails with undefined symbol errors:

... Creation of the Emergency Recovery cdrom was NOT successful. Check the /tmp/drf_6509.log log file for the reason for failure.

The /tmp/drf_####.log error log contains:

... Building the mini-kernel. /usr/work_4428/.drf_mach/etc/conf/bin/idbuild The mini-kernel build failed with error = 1 Check the /tmp/drf_4438_kernerr file for the mini-kernel failure reasons.

The /tmp/drf_####kernerr error log contains:

... UX:idbuild: INFO: Root for this process is /usr/work_4428/.drf_mach

UX:acomp: WARNING: "/usr/include/sys/privilege.h", line 51:
typedef redeclared: priv_t
Undefined                       first referenced
symbol                              in file
npci_bus                            pci/_drv.o
apic_get_lapicid                    psm_msi/_drv.o

UX:ld: ERROR: Symbol referencing errors. No output written to /usr/work_4428/.drf_mach/stand/unix.nostrip

UX:idmkunix: ERROR: Cannot link-edit
/usr/work_4428/.drf_mach/stand/unix.nostrip

Solution

This issue is fixed in OpenServer6 Definitive D2M0.

If you have OpenServer6 Definitive D1M0, you can correct the problem by modifying the file, /usr/lib/drf/mini_kernel

Locate the variable assignment for STATIC_LIST, which should be on line 200:

STATIC_LIST="ansi asyc atup ca ....

Modify this list to include 2 additional driver names, psm_apic & psm_cfgtables, so that it looks like:

STATIC_LIST="psm_apic psm_cfgtables ansi asyc atup ca ....

After saving the file, you should be able to use emergency_disk as expected.

From the Xinuos technical article database, record 127887. Reproduced with permission. The original is at www.sco.com/ta/127887, which is reachable but blocked from search engines.

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.