I’m having problems with my system recently. Today I did a shutdown and when
the machine restarted after it booted and before it ran sysinit.3 it gave me
the message “unable to exec /bin/sh : no such file or directory”. This
machine has run without problems for over a year and I don’t think that I
did anything obvious to cause this. I was able to boot off of a floppy and
mount the hard drive without any problems. I then did a chkfsys. It found
some ‘RECOVERABLE’ blocks which I had it fix but this didn’t seem to help. I
get the same results when booting again or trying altboot. What is this
caused by and how can I fix it? Everything appears to be present on the hard
drive.
Thanks,
Suzanne Artzberger
/bin/sh should be a link to something, normally /bin/ksh. Try booting with your
floppy, mount your hard disk and check if this link is present. If not, add it
and try again.
Suzanne Artzberger wrote:
I’m having problems with my system recently. Today I did a shutdown and when
the machine restarted after it booted and before it ran sysinit.3 it gave me
the message “unable to exec /bin/sh : no such file or directory”. This
machine has run without problems for over a year and I don’t think that I
did anything obvious to cause this. I was able to boot off of a floppy and
mount the hard drive without any problems. I then did a chkfsys. It found
some ‘RECOVERABLE’ blocks which I had it fix but this didn’t seem to help. I
get the same results when booting again or trying altboot. What is this
caused by and how can I fix it? Everything appears to be present on the hard
drive.
Thanks,
Suzanne Artzberger
Thanks Dean,
I checked this link and it already exists…
Dean Douthat <ddouthat@faac.com> wrote:
/bin/sh should be a link to something, normally /bin/ksh. Try booting
with your
floppy, mount your hard disk and check if this link is present. If not,
add it
and try again.
Suzanne Artzberger wrote:
I’m having problems with my system recently. Today I did a shutdown and
when
the machine restarted after it booted and before it ran sysinit.3 it
gave me
the message “unable to exec /bin/sh : no such file or directory”. This
machine has run without problems for over a year and I don’t think that
I
did anything obvious to cause this. I was able to boot off of a floppy
and
mount the hard drive without any problems. I then did a chkfsys. It
found
some ‘RECOVERABLE’ blocks which I had it fix but this didn’t seem to
help. I
get the same results when booting again or trying altboot. What is this
caused by and how can I fix it? Everything appears to be present on the
hard
drive.
Thanks,
Suzanne Artzberger