System won't boot into multiuser

[Richard Daly]

This morning I found my workstation to have rebooted itself over the weekend, it was hung on the boot process with error "INIT:Comand respawning to quickly, will retry in 5 mins"

When I boot in single user mode and mount /usr just about every command I execute comes back with the error

"PID xxx killed due to text modification or page I/O error, Bus error (coredump)"

Anyone any ideas how to resolve this??

RD

[Michael Elleby III_1]

Hello-

Have you tried booting the system into single user mode, and then to review your /etc/inittab to see what process is failing?

Mike-

[Ken Hubnik_2]

Here is a thread for your info.

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=c5762ac117cb7a7f2a/screen=ckiDisplayDocument?docId=200000055293010

http://us-support2.external.hp.com/cki/bin/doc.pl/sid=c5762ac117cb7a7f2a/screen=ckiDisplayDocument?docId=200000048161893

Hope this helps.

[Richard Daly]

Michael, I did try but I can't even read files I get the PID killed message when using more or vi in single user mode.

[Michael Elleby III_1]

Hello-

Ok, before you attempt to mount /usr, try running fsck on the lv to make sure all is ok.

I'm also curious to know if you've done any application or patch install recently that may have modified your kernel.

Mike

[Ken Hubnik_2]

--------------------------------------------------------------------------------
This typically happens because initd it trying to start some process and it can't. Since the process is set up to respaw, initd try again and again...so to slow it down, init waits 5 minutes hoping that things will be fixed by then.

First start by commenting out the line starting the samd, i.e. the line with /usr/sam/lbin/samd in /etc/inittab. Then tell initd to reread the configuration file (init q). Then try to debug why the samd process will not start...start by looking at syslog.

[Richard Daly]

I suspect the process it was trying to start is dtlogin, not 100% sure but it was for this reason that I booted into SU and wanted to put a sleep in the dtlogin startup script but then came across the PID killed error. I am wondering as it is virtually every command I run I get this error if the libs are corrupt.

I hadn't applied any patches or installed anything as the box is only really used to telnet and ssh to other machines.