topic Someone modified /etc/rc to 440 and now system will not boot in Operating System - HP-UX

Someone modified /etc/rc to 440 and now system will not boot

mark_5 — Fri, 29 Jun 2001 14:07:23 GMT

We have a FEP running HP-RT OS and the /etc/rc file was chmod'ed to 440. Now system will not boot and it seems the the console port will not respond. To make matters worse we have no Media, but have a tape backup. Any help would be appreciated.

Re: Someone modified /etc/rc to 440 and now system will not boot

Sachin Patel — Fri, 29 Jun 2001 14:17:14 GMT

Hi
Did you try to bring system up on single user mode?
type hpux -isl on ipl> prompt or even bo -isl will work too

Sachin

Re: Someone modified /etc/rc to 440 and now system will not boot

Emmanuel Eyer — Fri, 06 Jul 2001 10:12:41 GMT

Oops! Bad luck, I'm afraid. As far as I remember some experiences, /etc/rc (or /sbin/rc) is required even for single user mode. Boot on a support media (CD or tape), mount the root disk, chmod the file. If you have no media available you are in a bad situation...

Re: Someone modified /etc/rc to 440 and now system will not boot

Bill McNAMARA_1 — Fri, 06 Jul 2001 10:27:37 GMT

If the system doesn't boot with this method
ISL> hpux -lm -is
You'll not be able to repair unless you have an ignite tape or install cd (rescue option)
The ignite tape can be from another server.
Boot off it from BCH bo tape, no to ISL, then ignite launches. Interact with ugnite to get a shell. from the shell you can mount your / fs and rename the directory back.

Later,
Bill

Re: Someone modified /etc/rc to 440 and now system will not boot

Ravi_8 — Fri, 06 Jul 2001 10:39:20 GMT

hi,
feel pity for you,
without the installation cd or ignite tape u can't recover now. manage to get installation cd , boot from cd get the shell and change the rc files mode and reboot.

Re: Someone modified /etc/rc to 440 and now system will not boot

Vincent Fleming — Fri, 06 Jul 2001 12:55:10 GMT

In a real pinch, you might be able to install the root disk from your dead system in another (working) system, mount the partition that contains /, and fix the problem, put the disk back in the dead system, and off you go.

I'm not too sure how LVM would react to this, however. I've done this with older UNIX systems that do not have LVM.

Good luck.