ITEM: N1273L

/usr client will not reboot c29, c31 and c34

ENV:    RISC/6000 model 355 (User Client WorkStation)
        Running AIX version 3.2.5

DESC:   After doing a shutdown -Fr, the system went to led c29, c31 &
        c34.  The customer booted into Service mode, and did an lsdev -Cc
        hft, and it returned the console as "defined".  Customer needs
        to know what is wrong with his system.  The c29 indicates that
        the ethernet is not configuring, it eventually goes away and 
        the system does boot, but to the local /usr.  The problem
        occurred after running "bosboot -d hdisk0 -a" which he did
        in an attempt to fix a ipcs problem.  He is only able to boot
        to the local /usr with an ascii terminal, the hft is not
        configuring.  Customer has made a backup using Sysback/6000.
        The error log also shows errors relating to the battery.

ACTION: The customer can create a continual ping with his 355, after
        he gets the c34.  An lsdev -C | grep ent0 showd his Ethernet
        High-Performance LAN Adapter as "available".   Customer has
        placed service call and installed a new battery.  The NVRAM
        should still point to the local hdisk0 as the boot device.

Note that the InfoExplorer article "Backing Up Your System" states:
 Note:  If you used the procedures in "BOS Installation for Use with a
/usr Server" to install your system, you cannot reinstall your system
from a backup image.

He can mount /usr from the server, after a normal boot, but still
having problems.  TCP/IP and NFS weren't running (per lssrc -a).  So
we started startsrc -s inetd and startsrc -g nfs.  (how are the remote
nfs mounts other than /usr occuring?)  We unmounted and remounted some
other filesystems (but not /usr).

Got NFS write error 30 on host (serveraddress).  This error is due
to mounting /usr with read-write instead of read-only.

We believe the problem is associated with the boot LV not including
configuration methods for the ethernet.  He had run the bosboot
without the -p flag, i.e., "-p /usr/lib/boot/netdisk.proto"   The
default proto file does not have support for configuring the ethernet
adapter while the netdisk.proto file does.  He will rerun the bosboot
command for his /usr client (after he fixes his /usr filesystem mount
which he is mounting read/write instead of read/only - thus getting
lots of errors).  I also showed him the /usr/lpp/bosinst/bosmain
script which is used to install the system (including for a /usr
client).

I explained that his backups (made from sysback would not be
installable) and that the only way to reinstall a /usr client is by
choosing the "Install this system for use with a /usr server." option
from the installation program.  This is because it will only install
the root portions of the operating system (except for a small piece of
a local /usr in case of problems).  Sysback does not have an option to
install a /usr client from a backup.

The customer got the system running by running the bosboot with the -p
option.  



Support Line: /usr client will not reboot c29, c31 and c34 ITEM: N1273L

Dated: October 1994 Category: N/A

This HTML file was generated 99/06/24~13:30:39

Comments or suggestions?
Contact us