10-15-2009
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.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi friends,
i am getting the following error while booting my system which has SCo UNIX .
=========================
H iinit
PANIC: srmountfun-Error 22
mounting of rootdev hd(1/42)
cannot dump 40863 pages to dempdev hd(1/41) : Space for only 0 pages.
Dump not completed.
safe to power off... (3 Replies)
Discussion started by: sveera
3 Replies
2. SCO
hi, i m a newbie and installed sco unix on my machine. Also i installed win-xp. i tried to modify the boot.ini file but it does not give me a choice in the begining.
please guide me on this. do we get a boot loader for unix like LILO or GRUB?
:confused: (3 Replies)
Discussion started by: 187final
3 Replies
3. Solaris
I'm running solaris 2.5.1. My main development server is DEAD, i can't even boot off the cdrom, it powers up, acts like it is starting the boot process but then says cannot find boot device. I've done the search here on this site and saw the other posts, but at the ok prompt it won't even let me... (3 Replies)
Discussion started by: kymberm
3 Replies
4. SCO
anyone know where I can download or get a boot disk for sco unix v/386? I have an old PC running sco unix v/386 3.2. I dont have an install or boot disk. I need to reset the root password. I have looked all over the internet and cannot find it anywhere. any help would be greatly appreciated.... (5 Replies)
Discussion started by: format
5 Replies
5. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
6. Hardware
Hello, I am new to the UNIX community, however I have a beginner's level understanding of a majority of the basic commands in UNIX.
Today, my teacher gave me her old AT&T UNIX PC. I brought it home, turned it on, and got a completely green screen. I turned it off, and back on and it booted... (12 Replies)
Discussion started by: _dhoepp
12 Replies
7. UNIX for Dummies Questions & Answers
UNIX sco release 5.05 system does not boot:cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/bootWhat to do? (2 Replies)
Discussion started by: Joaoalpande
2 Replies
8. SCO
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (1 Reply)
Discussion started by: Joaoalpande
1 Replies
9. UNIX for Advanced & Expert Users
UNIX sco release 5.05 system does not boot:
cannot open device hd(40)/boot
stage 1 boot failure: error loading hd(40)/boot
what to do? (5 Replies)
Discussion started by: Joaoalpande
5 Replies
10. SCO
hi
i have image SCo Unix 5.0.6 and I want transfer on my HP ML350 G5
after Transfer show this message :
boot not found
cannot open
stage 1 boot failure: error loading hd (40)/boot
this hp server used smart array E200i and P400 and sco not recognized HDD
tanks (7 Replies)
Discussion started by: moein.mojtaba
7 Replies
FSCK(1) General Commands Manual FSCK(1)
NAME
fsck, fsck1 - perform file system consistency check
SYNOPSIS
fsck [-aclmrs] [device] ...
OPTIONS
-a Automatically repair inconsistencies
-c Check and list only the specified i-nodes
-l List the files and directories in the filesytem
-r Prompt user for repairs if inconsistencies are found
-s List the superblock of the file system
EXAMPLES
fsck /dev/hd4 # Check file system on /dev/hd4
fsck -a /dev/at0 # Automatically fix errors on /dev/at0
fsck -l /dev/fd0 # List the contents of /dev/fd0
fsck -c 2 3 /dev/hd3
# Check and list /dev/hd3 i-nodes 2 & 3
DESCRIPTION
Fsck performs consistency checks on the file systems which reside on the specified devices. Fsck1 is an alternate version for use on obso-
lete V1 file systems. When either the -a or -r flags are given, the file system will be repaired if errors are found. Before running fsck
on a mounted file system, it must first be unmounted. Trying to repair a mounted file system is dangerous and should not be attempted.
To repair the root file system (which cannot be unmounted), first type CTRL-F9 at the console to kill any and all processes. Log back in
as root, type sync to force any buffered changes to disk, run fsck on the root file system and immediately reboot the computer by typing
reboot.
It is necessary to kill all processes before repairing the root file system to prevent them from modifying any disk blocks while fsck is
running. This is only necessary for the root file system, any other file system can simply be unmounted before it is checked.
SEE ALSO
mkfs(1), mount(1).
FSCK(1)