Link to home
Start Free TrialLog in
Avatar of tegelert
tegelert

asked on

Solaris 8, boot /proc is not procfs mount point

When I boot my Solaris 8 system running on SunBlade 100 I get several error messages and the system won't boot.
A summary of the messages is shown below
The system just stops on the word done as show below.
Can you please explain the cause of these messages and what I might do to fix it. The system seemed to be running fine before I powered off and rebooted. I've booted to cdrom in single user mode and ran fsck, which found a few problems which I fixed, but didn't fix this problem.
Also below I've pasted my /etc/vfstab file.
--------------------------------------------------
Rebooting with command: boot
Boot device: disk File and args:
...
The system is coming down for administration. Please wait.
/sbin/rcS: /etc/nologin: cannot create
Unmounting remote filesystems: done.
pkill: /proc is not a procfs mount point (Comment: This message is repeating several times)
pgrep: /proc is not a procfs mount point
/usr/bin/ps: getexecname() failed
Killing user processes: pkill: /proc is not a procfs mount point
done.

---------------------------------------------------------------------------
fd      -      /dev/fd      fd      -      no      -
/proc      -      /proc      proc      -      no      -
/dev/dsk/c0t0d0s1      -      -      swap      -      no      -
/dev/dsk/c0t0d0s0      /dev/rdsk/c0t0d0s0      /      ufs      1      no      -
swap      -      /tmp      tmpfs      -      yes      -
cqghe.cqg.com:/release  -       /release        nfs     -       yes     rw
SOLUTION
Avatar of yuzh
yuzh

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
ASKER CERTIFIED SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tegelert
tegelert

ASKER

Before I had a chance to try these answers, I reinstalled OS and started from scratch.  It fixed the problem, but obviously not an ideal solution.  The answers are useful info anyway so it may be helpful to a future inquiry.
Thanks