Technical article 114983

When my server boots it hangs after loading the kernel.

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

Written · Last revised

Problem

My server ran out of disk space in the root filesystem and, after a re-boot, the server is unable to boot or I have run "fsck" on the root filesystem with the "-y" option (to answer Yes to all questions) and CLEARED some of the files that "fsck" prompted me with.

It simply hangs after loading the kernel before the /etc/inittab entries are run.

For example,
%ida0     0x7000-0x701F  11   -  PCI slot=5 units=2 Compaq IDA/SMART (rev 5.28a)
%adapter  0x1000-0x10FF  10   -  type=cha ha=0 id=7 EISA slot=1 geo=B wid=16 Com
paq Fast-SCSI-2 (rev 5.28a)
%adapter  0x6000-0x60FF  11   -  type=cha ha=1 id=7 PCI slot=0 geo=B wid=16 Comp
aq Fast-SCSI-2 (rev 5.28a)
%adapter  0x6400-0x64FF  15   -  type=cha ha=2 id=7 PCI slot=0 geo=B wid=16 Comp
aq Fast-SCSI-2 (rev 5.28a)
%csmu     -               -   -  Compaq SCSI-2 Management driver (rev 5.28a)
%cled     -               -   -  Compaq ProLiant Storage System (rev 5.28a)
%cnet     0x5000-0x500F   5   -  Compaq Netelligent NIC  Slot2
%pcibios  -               -   -  PCI BIOS (2.16), Hardware Mechanism 1
%cpqw     -               -   -  Compaq Wellness driver (ver 5.28a)
%crom     -               -   -  Compaq rom driver (rev 5.28a)
%juke     -               -   -  type=S ha=2 id=4 lun=0 bus=0 ht=cha
%cd-rom   -               -   -  type=S ha=0 id=5 lun=0 bus=0 ht=cha
%tape     -               -   -  type=S ha=0 id=2 lun=0 bus=0 ht=cha
%tape     -               -   -  type=S ha=2 id=3 lun=0 bus=0 ht=cha
%disk     -               -   -  type=IDA0 unit=0 cyls=6165 hds=255 secs=32
mem: total = 523772k, kernel = 50288k, user = 473484k
swapdev = 1/41, swplo = 0, nswap = 2048000, swapmem = 1024000k
rootdev = 1/42, pipedev = 1/42, dumpdev = 1/41
kernel: Hz = 100, i/o bufs = 32768k (high bufs = 26588k)
CONFIG: Low buffers unavailable, converted to high buffers

Cause

It is possible that the /dev/console device file has become corrupted and the server is unable to display anything further to the console.

Solution

If you have created your Emergency Boot & Root Floppies or Generic Boot & Root Emergency Floppies, you can boot the server using:

ta104767, "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 original OpenServer Media Kit by contacting SCO Support for instructions.

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 check the /dev/console file to ensure it is correct.  This is how
it should look. It is also linked to /dev/syscon and /dev/systty.
# cd /dev
# ls -al /dev/console
crw-------   3 bin      terminal   3,  1 Jul 27 10:50 console

If it is not there or does not look like the above, then to recreate it, run the following commands:

# cp console console.old
# cp systty systty.old
# cp syscon syscon.old
# mknod /dev/console c 3 1
# ln /dev/console /dev/syscon
# ln /dev/console /dev/systty

Once complete, exit the shell and umount the filesystem so it will not be corrupted when you re-boot:

# exit
# umount /mnt
# haltsys

See also

ta112505, "Additional Notes on Emergency Recovery for SCO OpenServer
5.0.6."

ta110334, "How to recover from a lost or corrupted /usr/lib/libc.so.1 on OpenServer 5."

ta105591, "How is /etc/inittab affected by a kernel relink?"

ta105032, "My system panics with "PANIC: exit cannot exec /etc/init (PID 1) status 9."

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

ta104755, "No user licenses were found on this machine" error and system panics."

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