NetNews Usenet Archive 1992 #31

home *** CD-ROM | disk | FTP | other *** search

/ NetNews Usenet Archive 1992 #31 / NN_1992_31.iso / spool / bit / listserv / aixl / 1908 next >

Wrap

Internet Message Format | 1992-12-21 | 42.2 KB

Xref: sparky bit.listserv.aix-l:1908 comp.unix.aix:12746 Path: sparky!uunet!pipex!bnr.co.uk!uknet!mcsun!Germany.EU.net!gate!g6150e!afx From: afx@muc.ibm.de (Andreas Siegert) Newsgroups: bit.listserv.aix-l,comp.unix.aix Subject: AIXTIPS NEWS 92430 Message-ID: <1992Dec21.131506.8924@muc.ibm.de> Date: 21 Dec 92 13:15:06 GMT Sender: news@muc.ibm.de (Newsagent-g6150) Reply-To: aixtips@ibm.de Followup-To: comp.unix.aix Organization: IBM AIX Field Support Center, Munich Lines: 768 This is AIXTIPS NEWS for customers released at Mon the 21. Dec 1992. Table of contents: 92430. Books for AIX PS/2 1.3 92434. SIGDANGER - What's the 'correct' way of handling it 92435. Address change for AIXSERV in the US 92436. The real story about mixing SCSI-1 and SCSI-2 devices 92440. How to get your keyboard back after unplugging it the from /6000? 92444. RISC SYSTEM LED RECOVER INFORMATION PACKAGE 92447. HOTW: What shared library funcs are loaded & running? Use GENLD ====================================================================== Note: The information in this document has not been submitted to any formal IBM test or review and is distributed on an "as is" basis without any warranty either expressed or implied. The use of this information is a customer responsibility and customers attempting to adapt these techniques to their own environment do so at their own risk. Some of the tips might reference internal TOOLS disks for more information. Please contact your IBM representative if you need those documents. Your AIXTIPS Team Internet: aixtips@ibm.de ====================================================================== >92430. Books for AIX PS/2 1.3 Note: AIX PS/2 1.3 is not announced in Europe, this is currently US only. Here is the list of doc's and disks from puborder S52G-9945-00 1 AIX PS/2 APPLICATION DEVELOPMENT TOOLK 28.44 92/12/08 S52G-9946-00 1 AIX PS/2 TEXT FORMATTING SYSTEM V-1.3 10.28 92/12/08 S52G-9947-00 1 AIX PS/2 DOS MERGE VERSION 1.3 11.20 92/12/08 S52G-9948-00 1 AIX PS/2 NETWORK FILE SYSTEM VERSION 1 4.49 92/12/08 S52G-9949-00 1 AIX PS/2 TRANS CTRL PROT/INTER PROT V- 9.67 92/12/08 S52G-9950-00 1 AIX PS/2 X.25 VERSION 1.3 8.96 92/12/08 S52G-9951-00 1 AIX PS/2 AIXWINDOWS ENVIROMENT FOR PS/120.00 92/12/08 S52G-9952-00 1 AIX PS/2 X-WINDOWS VERSION 1.3 76.00 92/12/08 S52G-9953-00 1 AIX PS/2 INED/INMAIL/INNET/INFTP VERSI 20.22 92/12/08 S52G-9954-00 1 AIX PS/2 OPERATING SYSTEM EXTENSIONS V 57.29 92/12/08 S52G-9955-00 1 AIX PS/2 XSTATION MANAGER VERSION 1.3 16.46 92/12/08 S52G-9965-00 1 AIX PS/2 OPERATING SYSTEM EXTENSION V- 67.69 92/12/08 S53G-0218-00 1 AIX PS/2 OPERATING SYSTEM VERSION 1.3 123.00 92/12/08 S53G-0219-00 1 AIX PS/2 OPERATING SYSTEM VERSION 1.3 108.00 92/12/08 S53G-0220-00 1 AIX PS/2 OPERATING SYSTEM VERSION 1.3 128.00 92/12/08 S53G-0221-00 1 AIX PS/2 OPERATING SYSTEM V-1.3 UPGRAD113.00 92/12/08 S53G-0226-00 1 AIX PS/2 OPER. SYS. EXT. V-1.3 UPGRADE 58.07 92/12/08 S53G-0227-00 1 AIX PS/2 OPER. SYS. EXT. V-1.3 UPGRADE 68.48 92/12/08 S53G-0228-00 1 AIX PS/2 APPLIC. DEV. TOOLKIT V-1.3 UP 12.00 92/12/08 S53G-0231-00 1 AIX PS/2 FORMATTING SYSYEM V-1.3 UPGRA 11.04 92/12/08 S53G-1159-00 1 AIX PS/2 DOS MERGE VERSION 1.3 UPGRADE 5.10 92/12/08 S53G-1162-00 1 AIX PS/2 INED/INMAIL/INNET/INFTP V-1.3 20.98 92/12/08 S53G-1165-00 1 AIX PS/2 NETWORK FILE SYSTEM V-1.3 UPG 6.04 92/12/08 S53G-1171-00 1 AIX PS/2 X.25 VERSION 1.3 UPGRADE 23.16 92/12/08 S53G-1174-00 1 AIX PS/2 AIXWINDOWS ENVIROMENT V-1.3 U121.00 92/12/08 S53G-1177-00 1 AIX PS/2 X-WINDOWS VERSION 1.3 UPGRADE 65.00 92/12/08 S53G-1180-00 1 AIX PS/2 XSTATION MANAGER V-1.3 UPGRAD 13.05 92/12/08 S53G-1882-00 1 AIX PS/2 XSTATION MANAGER V-1.3 1.11 92/12/08 S53G-1883-00 1 AIX PS/2 XSTA MGR V-1.3 ADD LIC UPGRAD 1.12 92/12/08 S53G-1884-00 1 AIX PS/2 X-WINDOWS VERSION 1.3 ADDITIO 1.11 92/12/08 S53G-1885-00 1 AIX PS/2 X-WIND. V-1.3 UPG ADD. LIC. 1.12 92/12/08 S53G-1886-00 1 AIX PS/2 AIXWIND ENVIR V-1.3 ADD LIC. 1.11 92/12/08 S53G-1887-00 1 AIX PS/2 AIXWIND ENV V-1.3 UPG ADD LIC 1.12 92/12/08 S53G-1888-00 1 AIX PS/2 X.25 VERSION 1.3 ADD LIC 1.11 92/12/08 S53G-1889-00 1 AIX PS/2 X.25 V-1.3 UPGRADE ADD LIC 1.12 92/12/08 S53G-1890-00 1 AIX PS/2 TCP/IP VERSION 1.3 ADD LIC 1.11 92/12/08 S53G-1891-00 1 AIX PS/2 TCP/IP V-1.3 UPG ADD LIC 1.12 92/12/08 S53G-1892-00 1 AIX PS/2 NET FILE SYS V-1.3 ADD LIC 1.11 92/12/08 S53G-1896-00 1 AIX PS/2 DOS MERGE V-1.3 ADD LIC 1.11 92/12/08 S53G-1897-00 1 AIX PS/2 DOS MERGE V-1.3 UPG ADD LIC 1.12 92/12/08 S53G-1898-00 1 AIX PS/2 TXT FORMAT SYS V-1.3 ADD LIC 1.11 92/12/08 S53G-1900-00 1 AIX PS/2 APPL DEV TKIT V-1.3 ADD LIC 1.11 92/12/08 S53G-1902-00 1 AIX PS/2 OP SYS V-1.3 EXT ADD LIC 1.11 92/12/08 S53G-1903-00 1 AIX PS/2 OP SYS V-1.3 EXT UPG ADD LIC 1.11 92/12/08 S53G-1904-00 1 AIX PS/2 OPER SYS V-1.3 ADD LIC 1.11 92/12/08 S53G-1905-00 1 AIX PS/2 OP SYS V-1.3 UPG ADD LIC 1.11 92/12/08 ====================================================================== >92434. SIGDANGER - What's the 'correct' way of handling it : 1) When does the AIX 3.2 generate SIGDANGER ? SIGDANGER is sent when the number of free pages falls below 512. : 2) If the condition persists, will AIX 3.2 start killing processes ? : If so, by what criteria will it choose its victim's (largest : memory consumer, youngest process,...)? When less than 128 pages remain, the system starts killing processes. It kills the youngest first in 3.2. It used to kill the largest. It will not kill any process that is catching SIGDANGER, unless that is the process that is demanding a new page and there are fewer than 64 pages remaining. : 3) Are there any guidelines for the actions a process should take : when SIGDANGER is delivered ? Get rid of any extra memory that you might have. This is not a practical suggestion in most cases, but it is the only thing that could possibly help. (It is not sufficient to free malloc'd memory. The disclaim() function can be used, but it must be done carefully.) G.N. ====================================================================== >92435. Address change for AIXSERV in the US ***************************************************************** * * * NOTE: CHANGE OF EMAIL ADDRESSES TO OCCUR DECEMBER 14TH 1992 * * * * On December 14th 1992 users of AIXServ will need to change * * the addresses used to send AIXServ transactions to the Austin * * support center. Use option 6) Edit defaults to change the * * BUGADDR and SERVADDR fields. The new entries should appear * * as: * * * * BUGADDR="aixbugs@austin.ibm.com" * * SERVADDR="services@austin.ibm.com" * * * * The old address will no longer work after December 14th, but * * must be used until that date. * * * * Any questions regarding this change should be sent to * * services@austin.ibm.com. * * * * These address changes will allow much better response times * * (minutes rather than hours or days). * * * ***************************************************************** ====================================================================== >92436. The real story about mixing SCSI-1 and SCSI-2 devices My apologies, I posted an error in the AIXTIPS NEWS item 92359 about SCSI compatibility. For mixing SCSI-2 and SCSI-1 devices on a SCSI-2 adapter the following is correct: The transmission rate between a SCSI I/O controller and a SCSI device is negotiated between the two; the synchronous transfer rate will be the fastest rate supported by both devices. If you have a SCSI-1 I/O controller the fastest rate you can get will be SCSI-1 rates regardless of what devices are attached. If you have a SCSI-2 I/O Controller, it will negotiate a SCSI-1 rate(4-5 MB/sec) with SCSI-1 devices and it will negotiate a SCSI-2 rate(10 MB/sec) with SCSI-2 devices. I hope you can now understand why on a SCSI-2 bus you will have different rates for SCSI-1 devices and SCSI-2 devices. SCSI-2 performance is also faster that just the rate difference(10 vs 4 MB/sec)as SCSI-2 includes a feature called "command tag queing" which can que up commands for a device and thus reduce bus latency and improve performance. Thanks to Ken for pointing this out. ====================================================================== >92440. How to get your keyboard back after unplugging it the from /6000? How to get the keyboard back to life after unplugging? When you unplug your keyboard from a running system, and plug it back in, the key mapping is wrong. For example, keys like Caps Lock and Ctrl don't work as designed. Now there is a solution : run the diagnostics on the keyboard. But watch out, if you run diag and try to go through the menus, you might be in trouble since the arrow keys don't work. The magic order is to type at the command line: /usr/lpp/diagnostics/da/dkbd Your screen goes black, you hear a few beep, and your keyboard is reset. It works with any environment, Xwindows, hft, NLS... Tips from Mickey Coggins and tested Anne Serre ====================================================================== >92444. RISC SYSTEM LED RECOVER INFORMATION PACKAGE Information: TITLE: LED Recovery Procedures DESCRIPTION: This file is a compilation of LED recovery procedures. DATE: 8/24/92 RECOVERY FROM AN LED 201 IN AIX 3.1 AND 3.2 CAUSES OF AN LED 201 An LED 201 during IPL is most often caused by a corrupted boot logical volume; however, it can also be caused by a hardware problem. If LED 299 appears before LED 201, a corrupted boot logical volume is probably the cause. If LED 299 does not appear, the cause may be hardware. The boot logical volume can become corrupted if the / (root) or /tmp filesystem is full when the bosboot command is run. This may occur during the installation of updates. SUMMARY OF THE RECOVERY PROCEDURE If the cause is a corrupted boot logical volume, erase files as necessary to free space on /dev/hd4 and /dev/hd3. If the cause seems to be hardware, follow the steps to check the boot logical volume, to make sure the boot logical volume is not corrupted. Then, check the error log for a hardware check stop, and contact your local branch office. (To check the error log, type "errpt | more".) STEPS 1. Turn the key to the Service position. 2. With bosboot diskettes or tape OF THE SAME VERSION AND LEVEL AS THE SYSTEM, boot the system, and go to the installation/maintenance menu. NOTES: a. The bosboot diskettes or tape must match the version and level on the system. If you mix AIX 3.1 and 3.2, you may damage the system. Also, many steps will not work if you mix levels of 3.1. 3. Choose the maintenance shell (option 5 for AIX 3.1, option 4 for AIX 3.2). Recovery from an LED 201 in AIX 3.1 and 3.2 1 4. If you have more than one fixed disk, determine which one contains the boot logical volume (hd5). To do this, see "Finding the Boot Logical Volume" at the end of this document. If you have only one fixed disk, that disk (hdisk0) contains the boot logical volume. 5. Now access the fixed disk that contains the boot logical volume by running /etc/continue (for AIX 3.1) or getrootfs (for AIX 3.2). ('#' is the number of the fixed disk, determined in step 4.) For AIX 3.1 only, run /etc/continue hdisk# For AIX 3.2 only, run getrootfs hdisk# 6. Use the df command to check for free space in /dev/hd3 and /dev/hd4. df /def/hd3 df /def/hd3 df /dev/hd4 7. If df showed that either filesystem is out of space, erase some files from that filesystem. Two files you may want to erase are /smit.log and /.sh_history. 8. Determine which disk is the boot disk with the lslv command. The boot disk will be shown in the PV1 column of the lslv output. lslv -m hd5 9. Recreate the boot image. (hdisk# is the boot disk determined in step 8.) bosboot -a -d /dev/hdisk# 10. With the key in Normal position, shutdown the system. shutdown -Fr 11. If LED 201 still occurs when you reboot your system, contact your local branch office. ---------------------------------------------------------------------- RECOVERY FROM LED 223/229, 225/229, 221/229, OR 221 CAUSES OF LED 223/229, 225/229, 221/229, OR 221 An alternating LED 223/229, alternating LED 225/229, alternating LED 221/229, or solid LED 221 occurs in AIX 3.1 or 3.2 on the RISC System/6000 when the system cannot locate the boot image. SUMMARY OF THE RECOVERY PROCEDURE To recover from this problem, rebuild the boot list. STEPS 1. Turn the key to the Service position. 2. While booting from the hard disk, watch for the light on the diskette drive. When you see the light, turn the key to Normal position. 3. When the machine has booted, log in as root. 4. Use the bootlist command to rebuild the boot list. bootlist -m normal scdisk 5. With the key in Normal position, shutdown and reboot. shutdown -Fr 6. If you still get LEDs 223/229, 225/229, 221/229, or 221, you may have a more serious problem, such as a missing boot logical volume. Contact your branch office SE (Systems Engineer). ---------------------------------------------------------------------- There are several reasons for an LED 551: You should be able to follow the procedures for LED 552 to correct the problems mentioned below. PROBLEM Solution _________________________________________________________________________ /dev missing, or corrupted - mkdir /dev /bin empty or missing - reinstall bad boot logical volume - bosboot -a /etc problems - restore selective files if possible, or reinstall corrupted filesystems - fsck /dev/hd4 as per LED552 a bad install of the system - install AIX properly ********************************************************************** LED 552 SYSTEM RECOVERY FOR AIX 3.1 AND 3.2 CAUSES OF AN LED 552 The known causes of an LED 552 during IPL on an RS/6000 are: o A corrupted file system. o A corrupted journaled-file-system (JFS) log device. o A bad IPL-device record or bad IPL-device magic number. (The magic number indicates the device type.) o A corrupted copy of the ODM (Object Data Manager) database on the boot logical volume. o A fixed disk (hard disk) in the state of inactive in the root volume group. SUMMARY OF THE RECOVERY PROCESS To diagnose and fix the problem, you will need to boot from the bosboot diskettes or tape and run fsck (file- system check) on each file system. If the file-system check fails, you may need to reformat the JFS log. STEPS 1. Turn the key to the Service position. 2. With bosboot diskettes or tape OF THE SAME VERSION AND LEVEL AS THE SYSTEM, boot the system, and go to the installation/maintenance menu. NOTES: a. The bosboot diskettes or tape must match the version and level on the system. If you mix AIX 3.1 and 3.2, you may damage the system. Also, many steps will not work if you mix levels of 3.1. b. If you get a 552 on this step, the diskette or tape is bad, and the machine is trying to boot off the fixed disk. Try it again with new bosboot diskettes or tape. 3. Choose the maintenance shell (option 5 for AIX 3.1, option 4 for AIX 3.2). 4. If you have more than one fixed disk, determine which one contains the boot logical volume (hd5). To do this, see "Finding the Boot Logical Volume" at the end of this document. If you have only one fixed disk, that disk (hdisk0) contains the boot logical volume. 5. Now access the fixed disk that contains the boot logical volume by running /etc/continue (for AIX 3.1) or getrootfs (for AIX 3.2). ('#' is the number of the fixed disk, determined in step 4.) For AIX 3.1 only, run /etc/continue hdisk# sh For AIX 3.2 only, run getrootfs hdisk# sh 6. Next, run the following commands to check and repair file systems. (The "-y" option gives fsck permission to repair file systems when necessary.) fsck -y /dev/hd1 fsck -y /dev/hd2 fsck -y /dev/hd3 fsck -y /dev/hd3 fsck -y /dev/hd4 For AIX 3.2 only, also run fsck -y /dev/hd9var If fsck indicates a file system with an unknown log record type or fails in the logredo process, then proceed to step 7. IF THE FILE SYSTEM CHECKS WERE SUCCESSFUL, SKIP TO STEP 9. 7. A corruption of the JFS log logical volume has been detected. Use the logform command to reformat it. On AIX 3.1 only, run /etc/aix/logform /dev/hd8 On AIX 3.2 only, run logform /dev/hd8 Answer YES when asked if you want to destroy the log. 8. Repeat step 6. If step 6 fails, the file system is almost always unrecoverable -- see "Dealing With Unrecoverable File Systems" after these steps. In most cases, step 6 will be successful. In that case, con- tinue to step 9. 9. With the key in Normal position, power down your machine Wait a couple seconds, then power it back up. The majority of LED 552s will be resolved at this point. If the LED 552 persists, contact your local branch office. DEALING WITH UNRECOVERABLE FILE SYSTEMS The easiest way to fix an unrecoverable file system is to recreate it. This involves deleting it from the system and restoring it from a backup. Note that hd2 and hd3 can be recreated but hd4 cannot be recreated. If hd4 is unrecoverable, you must reinstall AIX. For assistance with unrecoverable file systems, contact your local branch office. ---------------------------------------------------------------------- LED 553 The system will stop during IPL with 553 in the LEDs if init has a problem running or in reading the inittab file. This will often occur when the /tmp or the / filesystem is full. The following procedure can be used to correct this problem. - With the key in the 'SERVICE' position, boot from your installation media - Select option 5 from the installation menu - Type the following command to vary on the root volume group AIX 3.1 only: /etc/continue hdisk0 AIX 3.2 only: getrootfs hdisk0 - check for and correct an out of space condition Use 'df' to check for free space in /dev/hd4 and /dev/hd3. Erase files as necessary to correct the problem. Suspect /smit.log and /smit.script as being the problem. - Check the /etc/inittab for corruption: Usually it will be empty, or missing or have an entry in it that is not correct: - If inittab is corrupted then do the following: - Create the /etc/inittab file using your favorite editor. You must set your TERM environment variable using commands similar to the following prior to starting the editor. # export TERM=hft - if the inittab file was ok, then check the following files for any modification or permissions problem: /etc/environment /bin/sh /bin/bsh /etc/fsck missing or corrupted. This can be copied from the ram filesystem /etc/profile /.profile /etc/brc (3.1) or /sbin/rc.boot (3.2) - Also, if running 3.2, make sure the inittab is 3.2 (not 3.1). The line that starts out "brc" should read: brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 (version 3.2) brc::sysinit:/sbin/rc.boot 3 >/dev/console 2>&1 (version 3.2) NOT brc::sysinit:/etc/brc >/dev/console 2>&1 (version 3.1) - Place the key in 'NORMAL', execute the following command shutdown -Fr : @(#)inittab 1.22 com/cfg/etc,3.1,9021 4/6/90 17:18:07 init:2:initdefault: brc::sysinit:/etc/brc >/dev/console 2>&1 # Phase 2 of system boot rc:2:wait:/etc/rc > /dev/console 2>&1 # Multi-User checks srcmstr:2:respawn:/etc/srcmstr # System Resource Controller rctcpip:2:wait:/etc/rc.tcpip > /dev/console 2>&1 # Start TCP/IP daemons cons:0123456789:respawn:/etc/getty /dev/console piobe:2:once:/bin/rm -f /usr/lpd/pio/flags/* # Clean up printer flags files cron:2:respawn:/etc/cron qdaemon:2:once:/bin/startsrc -sqdaemon writesrv:2:once:/bin/startsrc -swritesrv LED C99 The LED C99 is usually caused by a bad /usr/bin/odmget command. /usr may be missing, or the /etc/filesystems file may be corrupted. 1) Boot from bosboot diskette or tape and get to install/maint menu - Key in service position 2) choose option 5 3) run: AIX 3.1 only: /etc/continue hdisk0 AIX 3.2 only: getrootfs hdisk0 - See the section on "Finding the Boot Logical Volume" at the end of this document. 4) Check to see if /etc/filesystems has the /usr filesystem in it. 5) use the mount command to check to see if /usr is mounted. 6) # cd /usr/bin If the command fails, then /usr/bin needs to be restored. 7) # ls -l /usr/bin/odmget If there is no odmget, then check to see if other files are missing from /usr/bin. from /usr/bin. LED C31 1) Boot from bosboot diskette or tape and get to install/maint menu - Key in service position 2) choose option 5 3) run: AIX 3.1 only: /etc/continue hdisk0 AIX 3.2 only: getrootfs hdisk0 - See the section on "Finding the Boot Logical Volume" at the end of this document. 4) chcons -a login=enable /dev/hft/0 5) reboot in normal mode. 6) If you still have LED C31, then repeat step 1-3, and goto step 7. 7) Next, # mkdir /etc/objrepos/bak # cp /etc/objrepos/Cu* /etc/objrepos/bak # cp /etc/objrepos/boot/Cu* /etc/objrepos # cp /etc/objrepos/boot/Cu* /etc/objrepos # savebase ---------------------------------------------------------------------- (from file /u/hsim/other/led518_3.2) RECOVERY FROM AN LED 518 IN AIX 3.2 CAUSES OF LED 518 When a preservation installation is followed by "BOS Installation Completion Tasks," some stanzas (sections) from the old /etc/filesystems file are copied over corre- sponding stanzas in the new file. Because of differences between AIX 3.1 and 3.2, some variables are not set cor- rectly, and /dev/hd1 may be mapped to /u instead of /home. This problem does not become apparent until o the user rebuilds the boot logical volume ("bosboot -a") and reboots or o the user creates a system image with mksysb and then tries to reinstall from that image. The first case results in an LED 518 during reboot. The second results in a failed reinstall. NOTES: 1. This /etc/filesystems problem occurs whether the system is installed from tape, over a network, or from a /usr server. 2. This problem does not occur with the "Upgrade Utili- ties" package. 3. APAR IX26523 addresses this problem. SUMMARY OF RECOVERY PROCEDURE In the file /etc/filesystems, append "type=bootfs" to the /, /usr, and /var stanzas. Make sure /dev/hd1 is mapped to /home in /etc/filesystems. Then recreate the boot device. STEPS 1. Turn the key to the Service position. 2. With bosboot diskettes or tape OF THE SAME VERSION AND LEVEL AS THE SYSTEM, boot the system, and go to the installation/maintenance menu. the installation/maintenance menu. NOTES: a. The bosboot diskettes or tape must match the version and level on the system. If you mix AIX 3.1 and 3.2, you may damage the system. 3. Choose the maintenance shell (option 4). 4. Run getrootfs without any parameters, and note which fixed disk (hdisk#) is listed as the boot disk. If getrootfs shows more than one boot disk, choose any boot disk listed. (In a later step we will determine which one is really the boot disk.) getrootfs 5. Now access the boot disk by running getrootfs with the hdisk name for the boot disk. getrootfs hdisk# 6. Change to the /etc directory. cd /etc 7. Set your terminal type in preparation for editing a file. (xxx is a terminal type, such as hft, ibm3151, or vt100.) TERM=xxx export TERM 8. Edit the file /etc/filesystems. In stanzas /, /usr, and /var, append "type = bootfs". Also, make sure /dev/hd1 is mapped to /home and not to /u; meaning that the first line of the stanza that has "dev = /dev/hd1" in it is written as "/home:" rather than "/u:" and that the "vol = " line is "vol = /home" rather than "vol = /u", in that same stanza. (For an example, see "EXAMPLE OF /etc/filesystems FOR AIX 3.2" after these steps.) 9. Determine which disk is the boot disk with the lslv command. The boot disk will be shown in the PV1 column of the lslv output. If getrootfs showed only one boot disk in step 4, then lslv should show the same boot disk. AT THIS POINT, IT IS VERY IMPORTANT TO DETERMINE THE CORRECT BOOT DISK. lslv -m hd5 10. Now, recreate the boot device. ('#' is the number of the fixed disk determined in step 9.) bosboot -a -d /dev/hdisk# -l /dev/hd5 -u 11. Shutdown the system. shutdown -F 12. With the key in Normal position, reboot the system. 13. We recommend that you create a new full-system backup because previous ones may be bad. To display the System Startup Menu, from which you can backup your system, type "smit startup". EXAMPLE OF /etc/filesystems FOR AIX 3.2 The following is an example of the /, /usr, /var, and /home stanzas of the /etc/filesystems file. /: dev = /dev/hd4 vfs = jfs log = /dev/hd8 log = /dev/hd8 mount = automatic check = false type = bootfs vol = root free = true /usr: dev = /dev/hd2 vfs = jfs log = /dev/hd8 mount = automatic check = false type = bootfs vol = /usr free = false /var: dev = /dev/hd9var vfs = jfs log = /dev/hd8 log = /dev/hd8 mount = automatic check = false type = bootfs vol = /var free = false /home: dev = /dev/hd1 vfs = jfs log = /dev/hd8 mount = true check = true vol = /home free = false ---------------------------------------------------------------------- FINDING THE BOOT LOGICAL VOLUME The Installation/Maintenance mode may assign a different hdisk name to a physical volume (fixed disk) than the multi-user mode assigns. To access the boot logical volume with /etc/continue or getrootfs, you will need to know the hdisk name of one of the disks in the same volume group as hd5 (the boot logical volume). NOTE: For the bosboot command, you will need to know the exact disk for hd5 (not just one of the disks in the group). THESE INSTRUCTIONS WILL NOT NECESSARILY PROVIDE THE CORRECT DISK FOR THE BOSBOOT COMMAND. If you have only one disk, then that disk (hdisk0) con- tains hd5. Use hdisk0 with the /etc/continue (for AIX 3.1) or getrootfs (for AIX 3.2) command. If you have more than one disk and you are running AIX 3.2, run getrootfs without any parameters to get a listing of disks. getrootfs Use one of the disks marked as a boot disk for the getrootfs command. If you have more than one disk and you are running AIX 3.1, run the following command for each hdisk# (hdisk0, hdisk1, etc.) until hd5 appears in column two. (This command lists all the all the physical and logical volumes in the volume group.) lqueryvg -p hdisk# -At The hdisk# for which hd5 appears is the hdisk# to use with /etc/continue. Source: IBM AIX Software Support Center, Austin, Texas ====================================================================== >92447. HOTW: What shared library funcs are loaded & running? Use GENLD Curious as to what shared library functions are loaded and running by each process on your system? GENLD is another one of those un(der)documented and unsupported commands shipped with the AIX BOS. It can be found in the directory, "/usr/lpp/bosperf/lib" Example: # genld (I've editted out many of the duller items) Proc_pid: 4919 Proc_name: inetd d00ae000 /usr/lib/libs.a/shr.o d0100000 /lib/libodm.a/shr.o d0230000 /lib/libsrc.a/shr.o d0227000 /lib/libbsd.a/shr.o d00cb000 /usr/lib/libc.a/meth.o d0002000 /usr/lib/libc.a/shr.o 10000000 inetd Proc_pid: 6746 Proc_name: X d02e4000 /usr/lpp/gai/adapter3.r4/load2d/ d02dd000 /usr/lpp/gai/adapter3.r4/loadrms/ d02db000 /usr/lib/libgair4.a/shr.o d02c0000 /usr/lpp/gai/loadddx/ d010d000 /lib/libcfg.a/shr.o d0100000 /lib/libodm.a/shr.o d029f000 /usr/lib/libdbm.a/shr.o d00cb000 /usr/lib/libc.a/meth.o -d ====================================================================== -- Andreas Siegert / Postmaster IBM Deutschland GmbH | Never grep a yacc AIX Field Support Center Pocci Strasse 11 | by the i-node! Internet: afx@ibm.de D-8000 Muenchen 2 | Opinions are my own, VNET: SIEGERT@MUNIVM4 Voice: (49)-(89)-7670-509 not IBM's.