Ghost image doesn't seem to work. System still at 98%. Printer/spooler is not enabled. I can only get the system to single user mode.....

---------- Post updated at 01:33 PM ---------- Previous update was at 01:29 PM ----------

I've zeroed out messages as well. I can't seem to find the crash/dump files for SCO. Can't find the directory as to where it is as well.

Once you get the system to single user mode,
what is the output of:
#df -v
#dfspace
#uname -X


What messages, do you get when you try to go to multi user?

My experience is limited at the top to 5.0.5 and in those cases where my systems have hit the wall I've received a message telling me so. Nothing in your post indicates that you've hit 100% so I suspect that there are other issues rather than full file systems.

In single user you can disable any filesystems that normally attach going into multi and see if you can get into multi without them. that allows you to manually attach them to trace which ones are giving the problems. And in single you can get rid of the stuff that jgt mentioned, along with any core dumps.

You didn't mention printers. You might want to disable any that are used for the duration of troubleshooting. A printer job running wild could be one reason for the sudden buildup.

I would also suggest that you document some stuff:
Look in /dev for items hd* to see what you have for hard drives defined. Should be HD10 through HD1a and a similar set for 2nd and higher drives.
Run divvy on one section of every hard drive you have identified and document the information.
This information may be vital if you end up having to reinstall.

Once in single user you can run mkdev fs to remove other than the required filesystems of root, boot, and swap. They can be added back later, after you have resolved the multiuser issues.

Although JGT suggested that you try for 10mb free I've worked with systems with as little as 1K free while resolving problems. But I was prepared to floppy boot to get access to clean, if needed.

From single user does mkdev fd work? Would give some assurance that you could get back in if something goes "bump".

Don't understand the boot menuing but would be curious about using init from SU mode. Something like init 6 which should lead to multi IIRC.

jgt here are the outputs I got from what you asked.

#df -v
Mount Dir            Filesystem               Blocks                Used                 Free               %Used
/                       /dev/root                3373036             3298658            74378              98%  
/stand               /dev/boot                3373036             3298658            74378              98%
/u1                   /dev/u1                   3373036             3298658            74378              98%

#dfspace
dfspace:  not found

#uname -X
System = SCO_SV
Node = xxxxx 
Release = 3.2v5.0.5
KernelID = 98/07/02
Machine = Pentium II (D)
BusType = ISA
Serial = 2GA023210
Users = 2-User
OEM# = 0
Origin# = 1
Num Cpu = 2

You have the desktop version of Openserver. This allows two concurrent telnet users and one at the console.
The divvy table appears to be corrupted.
"df -v" reports all three file systems as the same size!!! (or did you do a typo)
Typically /root would be 1 to 3 gb
/stand about 15 or 20 megabytes
/u1 the balance of the disk.
/swap doesn't show, but is usually 2 * system memory.
Is there only one hard disk in the system?
In single user mode only /root and /stand should show in df -v.
Dfspace provides the same data as df -v except in megabytes.
You should have found dfspace in /etc, can you check your PATH.
It should include at least /etc /bin /tcb/bin /usr/bin

Run the following:
#divvy
The table should show the starting and ending 1k_block numbers for each file system.
Are there more file systems than reported by df -v?
Then run
#mount
to display all currently mounted files systems, and then
#mountall
This should tell you if there are additional file systems and their condition.
If any will not mount, run
#fsck /dev/??? (file system name)
then try mountall again.


Run both of the following:
#/tcb/bin/integrity -e , this will list all files that do not have the correct ownership and permissions. Change them with chmod, chgrp, chown as necessary.
Repeat this step until there is no output.
#/tcb/bin/authck -a , this will tell you if any system files associated with security are corrupted.

Quite often /etc/auth/system/ttys becomes corrupted if the system crashes or runs out of disk space, as this file is modified when users log on and off.
The file should look like:

console:t_devname=console:chkent:
tty01:t_devname=tty01:t_uid=root:t_logtime#1251921523:\
:t_unsucuid=root:t_unsuctime#1250890220:t_prevuid=root:t_prevtime#125192
2283:\
:chkent:
tty02:t_devname=tty02:t_uid=root:t_logtime#1201031571:\
:t_prevuid=root:t_prevtime#1201033323:chkent:
tty03:t_devname=tty03:t_uid=root:t_logtime#1230657866:\
:t_unsucuid=root:t_unsuctime#1230657857:t_prevuid=root:t_prevtime#123065
7926:\
:chkent:
tty04:t_devname=tty04:chkent:
tty05:t_devname=tty05:chkent:
tty06:t_devname=tty06:chkent:

You can make all lines look like tty04 through tty06, delete any extraneous data at the end of the file. tty01, 02, and 03 show current and the last logged in user at that tty. The number of lines in the file will depend on how many pseudo terminals are configured, but ttyp0 through 16 should be lots.

i have two drives installed, mirrored. just sifting some stuff around the office (serial cable to capture the outputs that you requested.

no typo though. i just copied what i see on the screen.