Technical article 103157

System hangs "Type CONTROL-d" or "Current System Time" prompts.

OpenServer 5.0.0OpenServer 5.0.2OpenServer 5.0.4OpenServer 5.0.5OpenServer 5.0.6OpenServer 5.0.7

Written · Last revised

Problem

Note:  If you are running SCO UNIX System V/386 Release 3.2
(the original version) please refer to TA106242 in this
database entitled, "Can't go multi-user with ^D; console stty
setting are incorrect".

This article only pertains to the products listed in the RELEASE section above.

One of the following scenarios occur:

(1) The system hangs at the following prompt:

Type CONTROL-d to proceed with normal startup, (or give root password for system maintenance):

Sometimes the system will continue if a special control key combination such as <Ctrl>X, <Ctrl><Enter>, or <Ctrl><Del> is entered.

(2) The system hangs after fsck is run during system boot.

(3) The system hangs at the following prompt:

Current System Time is <current date-time> Enter new Time ([yymmdd]hhmm):

(4) Cannot run Xsight or ODT-VIEW in SCO Open Desktop due to "term type not known" error.

Cause

One possible cause of these symptoms is that the /etc/ioctl.syscon
file has been corrupted.  This can be caused by using init 0, init 1
or init S.  In particular, this is caused by changing the run level
with one of these commands when there is not a user or superuser
logged in on the primary console multiscreen (/dev/tty01). The
ioctl.syscon file gets rewritten with the stty values that
/dev/console has when one of the above commands were executed.
The device node /dev/console is typically linked to /dev/tty01,
and if nobody is logged in on /dev/tty01, The stty settings
will not be correct.

Solution

If the /etc/ioctl.syscon file is corrupted, the following steps
will correct it.  Note that if the file is not corrupted, these
steps should not be harmful.
Note:     DO NOT follow these steps under SCO UNIX System V/386 Release
          3.2 Operating System (the original version)!  There is a similar,
          but separate script for that release of SCO UNIX System V/386.
1. Boot UNIX automatically.  To do this, enter "unix auto" at the
boot prompt:
Boot:
unix auto
Note:     Do not attempt to reply to any prompts that appear before
          the login prompt.
2. Next, log in as root and delete the damaged file.  First,
   list the directory entry to determine if it is a symbolic
   link:
# ls -l /etc/ioctl.syscon

If the entry is not a symbolic link, simply remove the file:

# rm /etc/ioctl.syscon

Else, it the entry is a symbolic link, you must remove the base file that the symbolic link points to:

# rm <fullpathname>
where <fullpathname> is the full path name of the base
file.  The base file is listed after the "->" in the
directory entry listing.

3. Then shutdown and reboot the system:

# init 6
The problem should now be fixed.
Note:     A corrupted ioctl.syscon file can cause a number of strange
          symptoms.  The above procedure is worth a try in any situation
          that appears to be related to the above problem scenarios.
==============================================================================
Note:     If the above solution did not work, you may examine the following
          alternative:
# stty -g > /etc/ioctl.syscon
# sync
# haltsys
This alternative approach must be taken on tty01 only.  The reason
that a shutdown command is not issued, is to avoid conflicts with
the `stty -g` entry in /etc/rc0 during the shutdown routine.
==============================================================================

The system will hang on boot after the fsck or:

"kernel: i/o bufs = nnnk"

message and before the CONTROL-d prompt if one of the following device files is not linked to the others:

/dev/console      /dev/syscon        /dev/systty

In particular, if /dev/console is linked to another device such as /dev/tty02, the system will hang before the CONTROL-d prompt.

To check for this condition, enter the following commands as root:

# cd /dev
# l -i console syscon systty

The output should look something like this (the leading 32 may be replaced by another number, and the date will be different):

32 crw------- 3 bin      terminal    3,  1 Jun 27 09:24 console
32 crw------- 3 bin      terminal    3,  1 Jun 27 09:24 syscon
32 crw------- 3 bin      terminal    3,  1 Jun 27 09:24 systty
All three entries should match except for the name.  If one of
the entries does not match, use the rm and link commands to
fix it.  For example if console did not match syscon and systty,
you would enter the following commands as root:
# rm console
# ln syscon console
Then repeat the l -i command above to verify that the files are
correctly linked.  The problem should now be fixed.
NOTE:     You may be able to gain access to the server to boot into Multi User
          mode CTRL-J rather than CTRL-D.

Alternatively, boot into Multi-User mode and use the network to gain access to the server.

See also

ta104588, "Rebuild ttys file from inittab including pseudo ttys
after   crash."

From the Xinuos technical article database, record 103157. Reproduced with permission. The original is at www.sco.com/ta/103157, 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.