01-09-2008
If there's no LCD error code, then the system didn't get very far. You'll need to boot from external media.
IBM - Booting in Service Mode
It's possible that the system is downlevel on firmware, and is not compatible with that AIX release/level. You may need to update the FW to proceed (although that usually involves having a bootable disk: catch-22!)
The message "AIX is starting" is issued if a hd5 with a AIX boot image is found on the bootable media. This message should get replaced with "Starting Kernel" once the kernel code has been read into memory. Sometimes this can be corrected with:
#
bosboot -ad /dev/hdiskx
once the system is booted from external media and the rootvg imported and mounted.
10 More Discussions You Might Find Interesting
1. AIX
Hai
I am new to AIX, currently in our shop we use AIX 4.3.3 , where we have hosted the websphere 3.5 applicaiton on it. The AIX server is getting hanged very frequently, when analyse we found the swap memory is increasing once it reaches the memory 100 the system is totaly in hung state, so... (5 Replies)
Discussion started by: vipin77
5 Replies
2. AIX
I've got an RS6K B50, and i've installed AIX 5.3, TL5. It installs fine, the only customisations i make to the BOS are to change the locale / keyboard layout to UK, and to choose not to install graphical software.
I have no video card in this box, and i connect via a serial console (null modem... (4 Replies)
Discussion started by: craigp84
4 Replies
3. Solaris
Hi all,
I have a SUN server Sun-Fire-V890 running solaris 9, with a remote system console .
Both the IP adresses of the server and the console are in a private network (address 10.67.xxx).
For some reasons I need to give the access to the server from outside address 194.xxx, but I prefer that... (2 Replies)
Discussion started by: aribault
2 Replies
4. AIX
To All:
I have this AIX machine (see boot process below). The problem was it hangs at:
The ctrmc Subsystem has been started. Subsystem PID is 11906..
I checked with other forums but their advise were just "strong punches in the air" with no specific explanation.
I really appreciate if... (6 Replies)
Discussion started by: aix_xia
6 Replies
5. AIX
Hi, can someone point me to the bootup file where I can add a samba start up script so I dont have to manually start samba everytime we reboot the server? Thanks. (8 Replies)
Discussion started by: NycUnxer
8 Replies
6. Ubuntu
Boot process hangs after reaching the following line:
Adding 5853176k swap on /dev/mapper/mch-swap_1. Priority:-1 extents:1 across:5853176kUsing knoppix 6.2 as LiveCD, and mounting the partitions, I got the following:
# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s... (0 Replies)
Discussion started by: fzaker
0 Replies
7. AIX
Hi all,
We have a old Power4 server with AIX version 5.3 installed. Upon boot up, it hangs right after the AIX welcome screen. On the diagnostic load progress LED indicator, I saw that it stopped at '0c32' then after awhile the LED would be blank. The screen on the monitor will hang at the black... (15 Replies)
Discussion started by: a_sim
15 Replies
8. AIX
Good afternoon there,
One of my friend gave me an old IBM 44P Model 170 (I've planned to use it to learn AIX that I don't know at all) (I know a bit GNU/Linux (Debian, Archlinux, Red Hat, Slackware)).
But, unfortunately, the computer doesn't start properly and I don't have any idea why ;(.
... (6 Replies)
Discussion started by: firstpost
6 Replies
9. Solaris
Hi Guys,
I have a SunBlade 1500 which I use to practice at home. Suddenly when I power on the server it just displays the solaris banner and Boot device: disk File and args: Then it stops and says " rebooting with command: boot"
It doesn't boot to the kernel. Is there anyway I can possibly... (5 Replies)
Discussion started by: cjashu
5 Replies
10. Solaris
Power server up runs through diagnostics.
Goes to the boot section and then the bit where the cursor is spinning and thats it. Hangs completely.
Any ideas? (10 Replies)
Discussion started by: psychocandy
10 Replies
LEARN ABOUT HPUX
vx_emerg_start
vx_emerg_start(1M) vx_emerg_start(1M)
NAME
vx_emerg_start - start Veritas Volume Manager from recovery media
SYNOPSIS
vx_emerg_start [-m] [-r root_daname] hostname
DESCRIPTION
The vx_emerg_start utility can be used to start Veritas Volume Manager (VxVM) when a system is booted from alternate media, or when a sys-
tem has been booted into Maintenance Mode Boot (MMB) mode. This allows a rootable VxVM configuration to be repaired in the event of a cat-
astrophic failure.
vx_emerg_start verifies that the /etc/vx/volboot file exists, and checks the command-line arguments against the contents of this file.
OPTIONS
-m Mounts the root file system contained on the rootvol volume after VxVM has been started. Prior to being mounted, the rootvol volume
is started and fsck is run on the root file system.
-r root_daname
Specifies the disk access name of one of the members of the root disk group that is to be imported. This option can be used to spec-
ify the appropriate root disk group when multiple generations of the same root disk group exist on the system under repair. If this
option is not specified, the desired root disk group may not be imported if multiple disk groups with the same name exist on the sys-
tem, and if one of these disk groups has a more recent timestamp.
ARGUMENTS
hostname
Specifies the system name (nodename) of the host system being repaired. This name is used to allow the desired root disk group to be
imported. It must match the name of the system being repaired, as it is unlikely to be recorded on the recovery media from which you
booted the system.
NOTES
HP-UX Maintenance Mode Boot (MMB) is intended for recovery from catastrophic failures that have prevented the target machine from booting.
If a VxVM root volume is mirrored, only one mirror is active when the system is in MMB mode. Any writes that are made to the root file sys-
tem in this mode can corrupt this file system when both mirrors are subsequently configured.
The vx_emerg_start script allows VxVM to be started while a system is in MMB mode, and marks the non-boot mirror plexes as stale. This
prevents corruption of the root volume or file system by forcing a subsequent recovery from the boot mirror to the non-boot mirrors to take
place.
USAGE
After VxVM has been started, various recovery options can be performed depending on the nature of the problem. It is recommended that you
use the vxprint command to determine the state of the configuration.
One common problem is when all the plexes of the root disk are stale as shown in the following sample output from vxprint:
v rootvol root DISABLED 393216 - ACTIVE -
pl rootvol-01 rootvol DISABLED 393216 - STALE -
sd rootdisk01-02 rootvol-01 ENABLED 393216 0 - -
pl rootvol-02 rootvol DISABLED 393216 - STALE -
pl rootvol-02 rootvol DISABLED 393216 - STALE -
sd rootdisk02-02 rootvol-02 ENABLED 393216 0 - -
In this case, the volume can usually be repaired by using the vxvol command as shown here:
vxvol -g 4.1ROOT -f start rootvol
If the volume is mirrored, it is put in read-write-back recovery mode. As the command is run in the foreground, it does not exit until the
recovery is complete. It is then recommended that you run fsck on the root file system, and mount it, before attempting to reboot the sys-
tem:
fsck -F vxfs -o full /dev/vx/rdsk/4.1ROOT/rootvol
mkdir /tmp_mnt
mount -F vxfs /dev/vx/dsk/4.1ROOT/rootvol /tmp_mnt
SEE ALSO
fsck(1M), mkdir(1M), mount(1M), vxintro(1M), vxprint(1M), vxvol(1M)
VxVM 5.0.31.1 24 Mar 2008 vx_emerg_start(1M)