Problems with booting

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

When you booted from the flow was the file /bin/sh there
(it is a link I beleive).

Was the +x permission set correctly?


“Suzanne Artzberger” <SuzanneArtzberger@compuserve.com> wrote in message
news:8opk4h$cmo$1@inn.qnx.com

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

I checked the link and it was there. I’ll check on the +x permission.

Thanks.

Mario Charest <mcharest@zinformatic.com> wrote in message
news:8ori1h$d0o$1@inn.qnx.com

When you booted from the flow was the file /bin/sh there
(it is a link I beleive).

Was the +x permission set correctly?


“Suzanne Artzberger” <> SuzanneArtzberger@compuserve.com> > wrote in message
news:8opk4h$cmo$> 1@inn.qnx.com> …
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
\

do a ls -l /bin/sh
it should be link to /bin./ksh


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