ITEM: AI1265L

System hangs at led 551.

Question:

Informed customer that his business hours is between 8-5 CST.
Customer accepted offhour charge.
.ENV: AIX 3.2.5, 530H
,DESC:   Customer system hang at led 551 during reboot.
.He then tried to run getrootfs but got error message.
.ACT:  I had customer run "lsdev -Cc disk" but it was not found.
lqueryvg command does not work either.  I suggested customer reboot
the system and run fsck.  I also refered him to recovery procedure
led551 fax.  Customer will do this and will callback if he has
any problems.
;Next:  Closing pending callback. 

Response:

DESC:  Customer is receiving errors after running getrootfs.
.ACT:  
He has gone through the procedures in his guide.  He
has run fsck which did not return any error messages.  Customer
is unable to run logform in service mode.  We ran lqueryvg on
each of his drives.  lsvg -l rootvg gave error message that rootvg
was locked.  When we tried to look at the error report, it complained
about not having a template.  Customer may have file corruption or
boot image corruption.
.Customer does have a mksysb of his system.  
.Customer will run diagnostics on his system to verify that he does
not have any hardware problems.
.Customer should also try booting using an installation tape if 
diagnostics returns ok to rule out that his mksysb has a bad boot
image.
.NEXT:  Closing pending callback.

Response:

Desc:   The led551 recovery is failing at step9 when trying to
        exit.  The fsck commands completed fine earlier, but on
        exit to try and mount the aix filesystems, the following
        messages are displayed:

AFopen failed : no such file or directory
mount: could  not table filesystem data
mount: there is  no plausible log device for /dev/hd2 ("/usr")
AFopen failed: no such file or directory tabling filesystem
data: no such file or derectory
AFopen failed: no such file or directory
mount : could not table filesystem data
mount : there is no plausible log device for /dev/hd3 ("/tmp")
AFopen failed : no such file or directory tableing filesystem data;
no such file or directory
mount; could not table filesystem data
mount; there is no plausible log device for /dev/hd9var ("/var")
File systems mounted for maintenace work

Act:    Austext shows this problem could be caused by missing files
        from /etc or /bin

        'mount' reports the same errors, but shows /(root)-hd4 and
        /usr-hd2 are mounted.

        Daniel checked and /bin was missing entirely and in /etc
        there were only 2 files.

        Using the mksysb tape he booted off of, we proceeded to
        restore the missing directories using:

                cd /
                tctl rewind
                tctl -f /dev/rmt0.1 fsf 3
                tar -xvf /dev/rmt0 ./bin ./etc

Next:   Daniel will call back if the restore has problems
        He also wanted to know how to get the latest sendmail
        and I explained FixDist and recommended downloading ptf
        U435247.

        closing call pending callback

Response:



Support Line: System hangs at led 551. ITEM: AI1265L

Dated: November 1995 Category: N/A

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

Comments or suggestions?
Contact us