Sponsored Content
Operating Systems AIX boot process stuck on "Welcome to AIX" banner Post 302302882 by nilleb on Wednesday 1st of April 2009 09:04:07 AM
Old 04-01-2009
boot process stuck on "Welcome to AIX" banner

Good afternoon,

I'm currently working on an IBM 9110-510, with an AIX 6.1 on it.

Currently, I've put an HyperTerminal on the machine vty0. Folowing the procedure given by a support guy(§details), I'm able to get to the AIX banner

Code:
-------------------------------------------------------------------------------
                                Welcome to AIX.
                       boot image timestamp: 11:15 03/02
                 The current time and date: 12:05:47 04/01/2009
        processor count: 1;  memory size: 880MB;  kernel size: 26367045
    boot device: /pci@800000020000002/pci@2,4/pci1069,b166@1/scsi@0/sd@5:2
-------------------------------------------------------------------------------

But nothing happens after this step. On the LED attached to the power on button I can read 0c46, which corresponds to a "Normal installation processing".

I have not changed the network cable through which the machine is connected to the network since at least one month, and this is the first time I get on this problem.

I have attached the complete boot log (ie. the messages I'm getting on the serial port).

I do not know how the AIX system boot process is supposed to work, but I'm willing to learn more about it.

§details:
-put a null modem cable on the 1st serial port of the machine
-reboot the machine
-press'd enter
-logged in
-select the boot type and the boot device
-wait
>>> only the "Welcome to AIX" banner is printed. No kernel boot logs. The LED is stuck on the 0c46 message.


Update: the complete serial port log is available on http://nilleb.com/pub/boot-log.zip
 

9 More Discussions You Might Find Interesting

1. Red Hat

how to turn off the banner "SSH-2.0-OpenSSH_5.2"?

how to turn off the banner "SSH-2.0-OpenSSH_5.2"? I am using RedHat Advanced Server 4 #telnet localhost 22 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. SSH-2.0-OpenSSH_5.2 (3 Replies)
Discussion started by: vishwanathhcl
3 Replies

2. Red Hat

"service" , "process" and " daemon" ?

Friends , Anybody plz tell me what is the basic difference between "service" , "process" and " daemon" ? Waiting for kind reply .. .. (1 Reply)
Discussion started by: shipon_97
1 Replies

3. Solaris

Printer Entries stuck "finished printing"

On Solaris 8, when I do a lpstat -o: I have tried cancel 140828p-16974, but the entries remain New prints to this printer and others work successfully. Can anyone suggest how to get rid of these entries. Thanks (2 Replies)
Discussion started by: pmm
2 Replies

4. AIX

"fuser -c -k /XXX/XXXXXXX" Fails and stuck on AIX 6100-05-01-1016

Hi I was wondering if anybody has come across in a failure of fuser command. We have a backup script that is: fuser -c -k /XXX/XXXXXXX sync;sync umount /XXX/XXXXXXX/ backup -0 -f /dev/rmt0.1 -u /dev/XXXXXXXlv mount /XXX/XXXXXXX/ sync;sync The script is called from crontab via an... (2 Replies)
Discussion started by: ggovotsis
2 Replies

5. UNIX for Advanced & Expert Users

Processes on FreeBSD are stuck in "pipewr" state

Hi Experts, I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state. Any pointer for this problem? Thanks, akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies

6. BSD

Process stuck in "pipewr" state

Hi Experts, I am executing "svn" checkout command through my java code on a freeBSD machine. SVN checkout gets started , but when I run "top" command on my freebsd machine, I have observed that "svn" processes are stuck in "pipewr" state. Any pointer for this problem? Thanks, akash (0 Replies)
Discussion started by: akash.mahakode
0 Replies

7. Shell Programming and Scripting

How to enable "banner" for a user in solaris?

Password: Using keyboard-interactive authentication. Do you agree with the banner terms (y/n)?: y (4 Replies)
Discussion started by: frintocf
4 Replies

8. UNIX for Advanced & Expert Users

AIX - io info get from "libperfstat" not match "iostat"

Hi, everyone. I need to write a program to get io info based on libperfstat. But the "write time" of a disk is just half of the value get from iostat. I'm confused and can't explain. Help please. How I calculate "write service time per sec": In iostat: write service... (0 Replies)
Discussion started by: jackliang
0 Replies

9. AIX

How to enable "TCP MD5 Signatures" and "https" on AIX?

I have searched many times but nothing found. Somebody help please :(:(:( (1 Reply)
Discussion started by: bobochacha29
1 Replies
REBOOT(8)						    BSD System Manager's Manual 						 REBOOT(8)

NAME
reboot, halt, fastboot, fasthalt -- stopping and restarting the system SYNOPSIS
halt [-lnpq] [-k kernel] reboot [-dlnpq] [-k kernel] fasthalt [-lnpq] [-k kernel] fastboot [-dlnpq] [-k kernel] DESCRIPTION
The halt and reboot utilities flush the file system cache to disk, send all running processes a SIGTERM (and subsequently a SIGKILL) and, respectively, halt or restart the system. The action is logged, including entering a shutdown record into the user accounting database. The options are as follows: -d The system is requested to create a crash dump. This option is supported only when rebooting, and it has no effect unless a dump device has previously been specified with dumpon(8). -k kernel Boot the specified kernel on the next system boot. If the kernel boots successfully, the default kernel will be booted on successive boots, this is a one-shot option. If the boot fails, the system will continue attempting to boot kernel until the boot process is interrupted and a valid kernel booted. This may change in the future. -l The halt or reboot is not logged to the system log. This option is intended for applications such as shutdown(8), that call reboot or halt and log this themselves. -n The file system cache is not flushed. This option should probably not be used. -p The system will turn off the power if it can. If the power down action fails, the system will halt or reboot normally, depending on whether halt or reboot was called. -q The system is halted or restarted quickly and ungracefully, and only the flushing of the file system cache is performed (if the -n option is not specified). This option should probably not be used. The fasthalt and fastboot utilities are nothing more than aliases for the halt and reboot utilities. Normally, the shutdown(8) utility is used when the system needs to be halted or restarted, giving users advance warning of their impending doom and cleanly terminating specific programs. SEE ALSO
getutxent(3), boot(8), dumpon(8), nextboot(8), savecore(8), shutdown(8), sync(8) HISTORY
A reboot utility appeared in Version 6 AT&T UNIX. BSD
October 11, 2010 BSD
All times are GMT -4. The time now is 04:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy