AIX stuck at "rpc.lockd"

[Nigel Reed]

I 'inherited' for want of a better word an RS6000 7009. Went through the
AIX install and the system gets stuck after
"0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 6968."

Right now I just have a serial connection to my laptop. There doesn't
appear to be a monitor port on the back of the machine. I don't have a
mouse or keyboard plugged into the machine because there isn't a
monitor.

When I try to bring it up in single user mode, I get

portmir: Target and monitor devices must be different.

So, what gives?

Regards
Nigel

--
http://www.sysadmininc.com (My daytime job)
Member of the Dallas Better Business Bureau and Plano Chamber of Commerce

http://www.british-expats.com (My spare time)

[Bill]

Nigel Reed <s...@www.nelgin.nu-slash-qconfirm.html.invalid> wrote in message news:<q9g7g1-...@wibble.nelgin.nu>...

> I 'inherited' for want of a better word an RS6000 7009. Went through the
> AIX install and the system gets stuck after
> "0513-059 The rpc.lockd Subsystem has been started. Subsystem PID is 6968."
>
> Right now I just have a serial connection to my laptop. There doesn't
> appear to be a monitor port on the back of the machine. I don't have a
> mouse or keyboard plugged into the machine because there isn't a
> monitor.
>
> When I try to bring it up in single user mode, I get
>
> portmir: Target and monitor devices must be different.
>
> So, what gives?
>
> Regards
> Nigel

Comment out rc.nfs from /etc/inittab. Remember that in inittab, a
comment is a ":" not a "#". rpc.lockd is part of NFS. Then try
again.

BV

[Nigel Reed]

Bill <bve...@komatsuna.com> wrote:
> Comment out rc.nfs from /etc/inittab. Remember that in inittab, a
> comment is a ":" not a "#". rpc.lockd is part of NFS. Then try
> again.

Finally got it into single user mode by chosing AIX Shell Prompt in the
diagnostics menu. nfs is turned off but it just hangs at the previous
statement.

I'm guessing it's not actually hanging but (it's about 4 years since I
touched an RS6000) I seem to remember that the serial port on the back
should have a splitter cable with tty0 and tty1. My guess is that tty0
is disabled and tty1 can't be got at since I don't have a splitter.

I think I tried to enable logins on console and that failed, and I think
I tried moving console to tty1 and making tty0 a regular login device
but no joy there either.

Finally, I assume the network on this beat is 10mb/s only and everything
else I have is committed to my 100mb/s network at home so I can't even
do a network login.

Suppose I just need to head to Radio Shack and pick up some 8 core and a
few D-connectors.

[James T. Sprinkle]

Hi! Here is a quick solution. Set the switch to service mode and boot up
into diagnostics. Then select Task Selection and then you should see an
option for AIX Shell or Shell Prompt or something similar. When you select
that, it will boot up into single user mode. Then you can run smitty
devices, select tty, select change/show characteristics of a tty, tty0, then
do the following:

Change BAUD rate to 38400 if you want a faster tty
ADD clocal to the end of STTY attributes for RUN time and also to STTY
attributes for LOGIN (These are the true solution to your problem)
At the very bottom, change Apply change to DATABASE only to yes and hit
enter

Once this is done, turn your key to Normal mode and reboot. It should come
up fine this time. (NOTE if you changed your baud rate in the tty config,
you will need to change it also in your windows terminal emulation software.

Hope this helps!

JaYmZ
Senior AIX Systems Programmer
City of Seattle

"Nigel Reed" <s...@www.nelgin.nu-slash-qconfirm.html.invalid> wrote in
message news:q9g7g1-...@wibble.nelgin.nu...

[mail_address=Nigel Reed]

James T. Sprinkle <oicmr...@hotmail.com> wrote:
> ADD clocal to the end of STTY attributes for RUN time and also to STTY
> attributes for LOGIN (These are the true solution to your problem)

That's what I missed. Thanks!