04-23-2008
I don't think you need the SMS diskette at all if you can access the installed AIX (as it seems to be the case). Use either the "diag" utility to change the boot list or use the "bootlist" command directly.
Right now i have no AIX machine at hand so you will have to consult the manpage for details, AFAIR it is something like "bootlist -k <n|m> <device> <device> ..." where "-k n" is the boot list for normal mode boot and "-k m" is the boot list in maintenance mode. These two lists are managed separately.
You might have to really shutdown and restart the system (not just a "shutdown -Fr", but a "shutdown -Fh", then turn the key to "maint" and then power on again) to boot the machine in maintenance mode.
I hope this helps.
bakunin
6 More Discussions You Might Find Interesting
1. AIX
Hello Gurus,
i'm quite new person in AIX world, actually i'm SAP consultant. But due to my job faced with AIX.
Trying to configure new server for installation SAP. We have 4 disks one of them (hdisk3) has VG rootvg. How i can extend rootvg with another disk?
i tried:
# extendvg rootvg hdisk0... (2 Replies)
Discussion started by: sapbcer
2 Replies
2. High Performance Computing
A lightweight scheduler that supports high-throughput computing (HTC) applications on Blue Gene/P. (NEW: 06/12/2008 in grid)
More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
3. Solaris
I've got a console that seems to be hung. all other services (ip, etc) work perfectly. in fact, its still in production... we just don't have console access. so i there are two consoles on this guy.. scfc0 and scfc1. using iompadm from fujitsu, this is what i got:
# ./iompadm -c FJSVscf3 info... (1 Reply)
Discussion started by: pupp
1 Replies
4. Red Hat
We have a Red Hat linux server running on IBM x445 hardware. There are external disks in an IBM EXP300 disk enclosure. The system is running RAID 5. One of the four IBM disks (73.4 GB 10k FRU 06P5760) has become faulty. The system is still up and running OK because of the RAID. In that same EXP300... (3 Replies)
Discussion started by: pdudley
3 Replies
5. AIX
Hello everyone,
I'm working on a for-fun project where I'm assembling a mass of various old computers, including a number of earlier UNIX workstations. They will be on display at a number of east coast conferences (HOPE, Shmoocon, etc).
I'm trying to find a Thinkpad 860, 850, 820 or one... (1 Reply)
Discussion started by: telmnstr
1 Replies
6. AIX
Hi There,
I have zero information and zero knowledge for IBM virtual machine except Amazon cloud and VMware ESXi (Only Linux OS available).
Anyone could provide me the following answer -
Can IBM VM been deploy on X86 and X64 (Intel Chip)?
If answer is yes any chance to deploy AIX OS... (13 Replies)
Discussion started by: chenyung
13 Replies
LEARN ABOUT FREEBSD
reboot
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