HPUX11.11 installation Problem

[Jim Adamson]

Hi,
Can anyone help with a probelm cold installing HPUX11.11 on a B132L Workststation.

When the installation process completes and reboots there is always a system crash at the 'copy processor logs to /var/tombstones' stage. This occurs on all the 32 bit TCOE, MTOE and basic installations.

I logged on in single user mode and found /opt, /usr and /var were not mounted. When I tried mount /opt I got 'vxfs mount /dev/vg00/lvol6 is corrupted. After I ran 'fsck /dev/vg00/lvol6' the partition was declared clean and could be mounted. The same occured with /usr (dev/vg00/lvol7) and /var (dev/vg00/lvol8). Afetr this I tried 'init 3' but the system crashed at the 'tombstones' stage as usual.

I should add I put a Seagate 8GB disk (from another machine) in this workstation prior to the cold install, so maybe this disk has a fault. But the installation process finds the disk and appears to install the depots without any problems. The B132L had a 2GB disk in it originally.

I installed hpux11.11 on a similar workstation yesterday with no problems so I am at bit of a loss what to do next. Any help appreciated.

Jim

[hpuxrox]

There is a known issue with the PDC on that verion of box. Take a look at /usr/sbin/diag/contib/Readme.

Hopefully this is of some help.

-Yates

[Helen French]

Hi Jim:

You either have to anlyse the file ts99 under /var/tombstones or check the PIM information from the boot console menu. Check for any type of hardware errors from these places.

HTH,
Shiju

[Jim Adamson]

Hi,
thanks for the replys.

The file under /var/tombstones is 'tc100' and is 0 length. There is no README at /usr/sbin/diag/contrib.

How do I check the PIM info at the boot console?

thanks,
Jim

[S.K. Chan]

Not sure if you can do this on a B-class, but give it a try..

Interrupt the boot up.

At Main Menu prompt asking you to enter a
command, enter "SER" (service).

At the Service Menu enter "PIM 0" or "PIM"

[Jim Adamson]

Hi,
If this helps anyone - I upgraded the firmware to 6.1 and machine now boots without any problem.

regards,
Jim Adamson