System booting into maintenance mode

[asidarin]

I have a 5.3 system that had to have parts replaced. We ended up
restoring using the mksysb.

Now when the system boots, it boots into maintenance mode. We exit
maintenance mode and it goes into Single user mode. We type "telinit
2" and it then starts up in multi-user mode. Everything is fine at
that point.

When I do a bootlist for normal mode, it returns that my hdisk3 is my
in the list which is correct.

I haven't tried anything with my bootinfo.

This system had (3) 73GB drives that were mirrored and an extra 300GB
drive.

Currently, I'm only using (1) 73GB as my boot and OS drive and the
300GB for the data.

Not sure where to look to make it boot into multi-user mode directly.

Help,

Thanks,

[Ted Linnell]

Have you looked at /etc/inittab. One of the top lines should specify
which run level to boot into.

Ted.
==============================================================
| Ted Linnell <edli...@acslink.net.au> |
| |
| Nunawading, Victoria , Australia |
==============================================================

[asidarin]

On Feb 27, 1:05 pm, Ted Linnell <edlinn...@acslink.net.au> wrote:

> asidarin <asida...@gmail.com> wrote:
> >I have a 5.3 system that had to have parts replaced.  We ended up
> >restoring using the mksysb.
>
> >Now when the system boots, it boots into maintenance mode.  We exit
> >maintenance mode and it goes into Single user mode.  We type "telinit
> >2" and it then starts up in multi-user mode.  Everything is fine at
> >that point.
>
> >When I do a bootlist for normal mode, it returns that my hdisk3 is my
> >in the list which is correct.
>
> >I haven't tried anything with my bootinfo.
>
> >This system had (3) 73GB drives that were mirrored and an extra 300GB
> >drive.
>
> >Currently, I'm only using (1) 73GB as my boot and OS drive and the
> >300GB for the data.
>
> >Not sure where to look to make it boot into multi-user mode directly.
>
> >Help,
>
> >Thanks,
>
>  Have you looked at /etc/inittab. One of the top lines should specify
> which run level to boot into.
>
> Ted.
> ==============================================================

> | Ted Linnell                 <edlinn...@acslink.net.au>     |

> |                                  |
> | Nunawading, Victoria , Australia                           |
> ==============================================================

Yes, it is set to Run level 2. I forgot to add that.

Thanks,

[Tony]

In comp.unix.aix, asidarin <asid...@gmail.com> wrote:

>Yes, it is set to Run level 2. I forgot to add that.

Any errors in the bootlog to indicate why it's failing to boot properly?
--
Tony Evans
Saving trees and wasting electrons since 1993
blog -> http://perceptionistruth.com/
books -> http://www.bookthing.co.uk/
[ anything below this line wasn't written by me ]

[asidarin]

On Feb 27, 2:16 pm, Tony <t...@darkstorm.invalid> wrote:

I'm only seeing "return code = 0" in the alog but I do see the
following lines:

rc.boot: executing "mount /var"
rc.boot: executing "copycore"
Changed: ipldevice
mergedev replaced 1 files in the hardfile /dev directory
...

Here are the last few lines of the alog -o -t boot:

Configuration time: 12 seconds

Saving Base Customize Data to boot disk
Starting the sync daemon
Mounting the platform dump file system, /var/adm/ras/platform
Starting the error daemon
System initialization completed.
Starting Multi-user Initialization
Performing auto-varyon of Volume Groups
Activating all paging spaces
0517-075 swapon: Paging device /dev/hd6 is already active.

The current volume is: /dev/hd1
Primary superblock is valid.

The current volume is: /dev/hd10opt
Primary superblock is valid.
Performing all automatic mounts
Multi-user initialization completed


The first not commented line in my /etc/inittab is:

init:2:initdefault:

A couple other things. This system might have been set up with a
graphics console on an HFT, but hasn't had one for a long time.
They had a 3151 terminal as a console until it died. We found out the
hard way that they didn't have a real console since then, they were
using a PC through the network for a while. Luckily, they found an
old terminal and the correct cable and was able to plug that into the
first serial port on the back of the system itself, a 9 ping port so
that we could boot off of CD and then restore the image.

I'm wondering if there is something with the hft or something wrong
with the terminal setup that is affecting it.

Thanks,

[Gerard H. Pille]

asidarin wrote:

> The first not commented line in my /etc/inittab is:
>
> init:2:initdefault:
>

What else do you have in /etc/inittab for that runlevel?

[asidarin]

I have an AIX 5.3 sys at here at the office and I did an eye-ball
check and they at least looked similar.

Here are the lines of my /etc/inittab



init:
2:initdefault:
brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 # Phase 3 of system
boot
powerfail::powerfail:/etc/rc.powerfail 2>&1 | alog -tboot > /dev/
console # Power Failure
Detection
mkatmpvc:2:once:/usr/sbin/mkatmpvc >/dev/console
2>&1
atmsvcd:2:once:/usr/sbin/atmsvcd >/dev/console
2>&1
load64bit:2:wait:/etc/methods/cfg64 >/dev/console 2>&1 # Enable 64-bit
execs
tunables:23456789:wait:/usr/sbin/tunrestore -R > /dev/console 2>&1 #
Set
tunables
rc:23456789:wait:/etc/rc 2>&1 | alog -tboot > /dev/console # Multi-
User checks
fbcheck:23456789:wait:/usr/sbin/fbcheck 2>&1 | alog -tboot > /dev/
console # run /etc/
firstboot
srcmstr:23456789:respawn:/usr/sbin/srcmstr # System Resource
Controller
rctcpip:23456789:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP
daemons
sniinst:2:wait:/var/adm/sni/sniprei > /dev/console
2>&1
rcnfs:23456789:wait:/etc/rc.nfs > /dev/console 2>&1 # Start NFS
Daemons
cron:23456789:respawn:/usr/sbin/
cron
piobe:2:wait:/usr/lib/lpd/pioinit_cp >/dev/null 2>&1 # pb
cleanup
qdaemon:23456789:wait:/usr/bin/startsrc -
sqdaemon
writesrv:23456789:wait:/usr/bin/startsrc -
swritesrv
uprintfd:23456789:respawn:/usr/sbin/
uprintfd
shdaemon:2:off:/usr/sbin/shdaemon >/dev/console 2>&1 # High
availability daemon
l2:2:wait:/etc/rc.d/rc
2
l3:3:wait:/etc/rc.d/rc
3
l4:4:wait:/etc/rc.d/rc
4
l5:5:wait:/etc/rc.d/rc
5
l6:6:wait:/etc/rc.d/rc
6
l7:7:wait:/etc/rc.d/rc
7
l8:8:wait:/etc/rc.d/rc
8
l9:9:wait:/etc/rc.d/rc
9
naudio::boot:/usr/sbin/naudio > /dev/
null
ntbl_reset:2:once:/usr/bin/
ntbl_reset_datafiles
rcml:2:once:/usr/sni/aix53/rc.ml > /dev/console
2>&1
logsymp:2:once:/usr/lib/ras/logsymptom # for system
dumps
perfstat:2:once:/usr/lib/perf/libperfstat_updt_dictionary >/dev/
console 2>&1
diagd:2:once:/usr/lpp/diagnostics/bin/diagd >/dev/console
2>&1
xmdaily:2:once:/usr/bin/xmwlm -L 2>&1 >/dev/null # Start xmwlm daily
recording
ctrmc:2:once:/usr/bin/startsrc -s ctrmc > /dev/console
2>&1
ha_star:h2:once:/etc/rc.ha_star >/dev/console
2>&1
vty1:2:off:/usr/sbin/getty /dev/
vty1
lft0:2:respawn:/usr/sbin/getty /dev/
lft0
api1:2:respawn:/usr/faxfx/etc/
APIscript
dt_nogb:2:wait:/etc/
rc.dt
cons:0123456789:respawn:/usr/sbin/getty /dev/
console
tty3:2:off:/usr/sbin/getty /dev/
tty3
tty2:2:respawn:/usr/sbin/getty /dev/
tty2
tty0:2:off:/usr/sbin/getty /dev/
tty0
tty1:2:respawn:/usr/sbin/getty -u /dev/
tty1


Thanks for your help,

[asidarin]

Sorry the format was terrible, didn't know it would do that. Am
trying again. Hope it works better.

Darin

[Gerard H. Pille]

asidarin wrote:
> On Feb 29, 3:11 pm, asidarin<asida...@gmail.com> wrote:
>> On Feb 28, 1:53 pm, "Gerard H. Pille"<g...@skynet.be> wrote:
>>
>>> asidarin wrote:
>>>> The first not commented line in my /etc/inittab is:
>>
>>>> init:2:initdefault:
>>
>>> What else do you have in /etc/inittab for that runlevel?
>>
>> I have an AIX 5.3 sys at here at the office and I did an eye-ball
>> check and they at least looked similar.
>>
>> Here are the lines of my /etc/inittab
>>

I wouldn't doubt your eyesight for a minute, but why not show the inittab from the problematic
system? Or copy it to the working system (in /tmp, not in /etc) and run a diff between the two.

[Gerard H. Pille]

"Some systems may have a key that you can turn to maintenance mode, as well."

[Gerard H. Pille]

asidarin wrote:
> On Feb 29, 3:11 pm, asidarin<asida...@gmail.com> wrote:
>> On Feb 28, 1:53 pm, "Gerard H. Pille"<g...@skynet.be> wrote:
>>
>>> asidarin wrote:
>>>> The first not commented line in my /etc/inittab is:
>>
>>>> init:2:initdefault:
>>
>>> What else do you have in /etc/inittab for that runlevel?
>>
>> I have an AIX 5.3 sys at here at the office and I did an eye-ball
>> check and they at least looked similar.
>>

The only command run before going to runlevel 2, is:

brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 # Phase 3 of system boot

Is /sbin/rc.boot executable at boot? What does it contain?

Any feedback from errpt?

[Michael Kraemer]

In article <4f4fc4a3$0$5047$ba62...@news.skynet.be>, "Gerard H. Pille"

<g...@skynet.be> writes:

> "Some systems may have a key that you can turn to maintenance mode, as well."

But those antiques won't run 5.3, no?

[asidarin]

On Mar 1, 12:56 pm, "Gerard H. Pille" <g...@skynet.be> wrote:
> asidarin wrote:
> > On Feb 29, 3:11 pm, asidarin<asida...@gmail.com>  wrote:
> >> On Feb 28, 1:53 pm, "Gerard H. Pille"<g...@skynet.be>  wrote:
>
> >>> asidarin wrote:
> >>>> The first not commented line in my /etc/inittab is:
>
> >>>>       init:2:initdefault:
>
> >>> What else do you have in /etc/inittab for that runlevel?
>
> >> I have an AIX 5.3 sys at here at the office and I did an eye-ball
> >> check and they at least looked similar.
>
> The only command run before going to runlevel 2, is:
>
> brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 # Phase 3 of system boot
>
> Is /sbin/rc.boot executable at boot?   What does it contain?
>
> Any feedback from errpt?

Sorry, it was snowing and I was thinking of getting out a little early
yesterday. And I thought there would be too many differences between
the files.

I did a diff on my 5.3 here against the 5.3 there for both the rc.boot
& inittab files. Here are some of the differeneces:

rc.boot:
4th line
my 5.3
# bos530 src/bos/sbin/rc.boot/rc.boot.sh 1.58.2.134

bad 5.3 (for lack of better description)
# bos53H src/bos/sbin/rc.boot/rc.boot.sh 1.58.2.149

I know this is a comment line in the file, but I can tell that these
weren't installed with the identical OS Disks.

For the next approx 225 lines, they are the same. Then in the bad
5.3, I get a function that is like:

cfg_iscsi_sw() {

But I don't have that in my my 5.3 system. Further down the bad 5.3,
it tests 'bootinfo -i' to see if it should run cfg_iscsi_sw(). I ran
it from the command line and it returned 0 and I don't have any iscsi
devices, so that makes sense.

Most of the rest of the bad 5.3 rc.boot file is similar, but the main
difference is that the bad 5.3 uses variables for things like
mounting /usr and slightly different paths, etc. Here is an example:

My 5.3:
# Mount /usr
/../usr/lib/methods/showled 0x517 "MOUNT /USR"
echo "rc.boot: executing \"fsck -fp /usr\"" \
>>/../tmp/boot_log
/../usr/sbin/fsck -fp /usr
echo "rc.boot: executing \"mount /usr\"" \
>>/../tmp/boot_log
/../usr/sbin/mount /usr
[ "$?" -ne 0 ] && loopled 0x518 "/USR MNT FAILED"


The bad 5.3:
# Mount /usr
/../usr/lib/methods/showled 0x517 "MOUNT /USR"
echo "rc.boot: executing \"fsck -fp /usr\"" \
>>/../tmp/boot_log
/../usr/sbin/fsck -fp /usr 2>&1 | \
/../usr/bin/tee -a /../tmp/boot_log
echo "rc.boot: executing \"mount /usr\"" \
>>/../tmp/boot_log
{ /../usr/sbin/mount /usr 2>&1; \
print $? >/../tmp/rc; } | \
/../usr/bin/tee -a /../tmp/boot_log
read rc </../tmp/rc
[ "$rc" -ne 0 ] && loopled 0x518 "/USR MNT FAILED"

Here is my 5.3 rc.boot info:
-rwxrwxr-- 1 root system 25024 Jul 12 2004 /sbin/rc.boot

And here is the bad 5.3 rc.boot info:
-rwxrwxr-- 1 root system 28846 Mar 26 2006 /sbin/rc.boot

As far as the inittab, other than the difference in terminal ports,
everything is the same from the init:2:initdefault: down to
rctcpip:...

After that line, the bad 5.3 has

sniinst:2:wait:/var/adm/sni/sniprei > /dev/console 2>&1

And my 5.3 doesn't have that line.

Also, my 5.3 has:

cons:0123456789:respawn:/usr/sbin/getty /dev/console

But the bad 5.3 has it much further down in the inittab file. In my
5.3 inittab it is on line 44, in the bad it line 70.

The bad 5.3 also has:

ntbl_reset:2:once:/usr/bin/ntbl_reset_datafiles
rcml:2:once:/usr/sni/aix53/rc.ml > /dev/console 2>&1

xmdaily:2:once:/usr/bin/xmwlm -L 2>&1 >/dev/null # Start xmwlm daily
recording

vty1:2:off:/usr/sbin/getty /dev/vty1

dt_nogb:2:wait:/etc/rc.dt


Also, I hadn't thought of looking at the errpt. The last time we
tried to boot was on Saturday, Feb 18th and we got a SysPlanar error
in errpt:
-----------------------------------------------------------
LABEL: SCAN_ERROR_CHRP
IDENTIFIER: BFE4C025

Date/Time: Sat Feb 18 07:19:59 PST 2012
Sequence Number: 18032
Machine Id: 0004BDF4D700
Node Id: risc36
Class: H
Type: PERM
Resource Name: sysplanar0
Resource Class: planar
Resource Type: sysplanar_rspc
Location:

Description
UNDETERMINED ERROR

Failure Causes
UNDETERMINED

Recommended Actions
RUN SYSTEM DIAGNOSTICS.


Thanks again for all of your help

[Gerard H. Pille]

asidarin wrote:
>
> Recommended Actions
> RUN SYSTEM DIAGNOSTICS.
>
>

Will you obey the machine? Next time he might start insulting you.

[asidarin]

I've asked the customer to call IBM Hardware to follow up on this.
But would this cause it to not to boot into multi-user mode but after
we are in diag, it allows us to continue on?

Thanks,

Darin

[Gerard H. Pille]

asidarin wrote:
> { /../usr/sbin/mount /usr 2>&1; \
> print $?>/../tmp/rc; } | \
> /../usr/bin/tee -a /../tmp/boot_log

What is the first line of rc.boot? I do not understand the above syntax, and I thought I knew
shell programming.

[asidarin]

Here are the first few lines of rc.boot on the bad 5.3 system:

#!/usr/bin/ksh
# IBM_PROLOG_BEGIN_TAG
# This is an automatically generated prolog.
#
# bos53H src/bos/sbin/rc.boot/rc.boot.sh 1.58.2.149
#
# Licensed Materials - Property of IBM
#
# (C) COPYRIGHT International Business Machines Corp. 1989,2006
# All Rights Reserved
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#
# IBM_PROLOG_END_TAG
# @(#)62 1.58.2.149 src/bos/sbin/rc.boot/rc.boot.sh, bosboot,
bos53H, h2006_12B8 3/22/06 11:15:05
#
# COMPONENT_NAME: (BOSBOOT) Base Operating System Boot
#
# FUNCTIONS: rc.boot.sh
#
# ORIGINS: 27
#
# (C) COPYRIGHT International Business Machines Corp. 1989, 1996
# All Rights Reserved
# Licensed Materials - Property of IBM
#
# US Government Users Restricted Rights - Use, duplication or
# disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
#

# local defines

[Gerard H. Pille]

You are lucky it allows you to continue on.

http://www.unix.com/aix/44561-aix-hangs-through-boot-process.html

[Gerard H. Pille]

My hardware knowledge dates back to the RS600, so rather rusty.

[Gerard H. Pille]

On 1 mrt, 22:59, asidarin <asida...@gmail.com> wrote:
> On Mar 1, 3:48 pm, "Gerard H. Pille" <g...@skynet.be> wrote:
>
> > asidarin wrote:
> > >                    { /../usr/sbin/mount /usr 2>&1; \
> > >                            print $?>/../tmp/rc; } | \
> > >                            /../usr/bin/tee -a /../tmp/boot_log
>
> > What is the first line of rc.boot?   I do not understand the above syntax, and I thought I knew
> > shell programming.
>
> Here are the first few lines of rc.boot on the bad 5.3 system:
>
> #!/usr/bin/ksh

So, I don't know everything about ksh, what a desillusion :-(