This was an important piece of information (Solaris 7 Jumbo Kernel Patch). Did you apply it and [I}then{/I} you could not boot? Did you apply the patch in single user mode?

Please answer these questions.

Also, please post the output from df -k.


If there is still space on /var/adm (whatever that partition is) then it should still write to the files. Another possiblity is that you have run out of inodes. Post your output from df -k.

Just out of curiosity, did you follow the steps outlined in the Document 20768 on Sunsolve?

no i did not apply the patch, i am not sure i know how to go about it, seems rather complicated.
I was trying to see if i still had the patch, locally on the disk soo i wont have to copy to diskette ( E220R dont even have diskette drives) etc, but after mounting /, i couldnt seem to find it.
I cannot copy the output of the df -k for u as the machine is off the network since it cant boot, but this is a transfer of the handwritten output below;

# mount /dev/dsk/c0t0d0s0 /a
#cd /
#cd /a
#df -k

Filesystem : /dev/dsk/c0t0d0s3
Kbytes : 12100380
used : 876196
avail : 11103181
capacity : 8%
mounted on : /a

Offcourse, on the server, this entry, along with others, is displayed horizontally.
With reference to chttp://sunsolve.sun.com/pub-cgi/retrieve.pl?doc=fsrdb%2F20768&zone_32=cannot%20write%20to%20utmp%20and%20utmpx%20files%20solaris%207 ,
i could not seem to find any matches when i did
ls -l /a/devices/pseudo/sys*
and i cant seem to find the post patch script 106541-05 either.
Please how do i go about this? i might be missing something.

Is there a chat room you belong to? i would like to chat with you as i try to resolve this problem, for advice. I am :: email removed :: and :: email #2 removed ::

Thanks.

__________________
Simbo Adeyemi ( Miss)
m.c.s.e.
m.c.p.
c.c.n.a.

Sorry, no, I don't use chat rooms - and unfortunately, I was not on this site this morning so I did not see your last message until now (can't use chat at work).

From what you posted - you didn't apply the patch.
This means the problem occurred due to the patch (according to the documentation). You must do Step 4 and below in the documentation. I've never used ftp to get a file onto a server booted from cdrom, but the documentation makes it sound like it is possible. Put the patch onto a disk (mount /dev/rdsk/c0t0d0s0 back to /a). ftp from your 'down' server to one that has the patch. Get the patch and then follow the rest of the steps.