How to Rebuild Tru64 V5.1 Persistent Hardware Database

Owned by Robert Urban
Last updated: Nov 23, 2018
2 min read

Description

After migrating a Tru64 UNIX v5 system to a different platform, occasionally the kernel will panic during boot with an error message such as:

panic (cpu 0): titan-pci_confl1: cannot configure PCI subsystem -- get_bus failure

This is just one example. In such cases, the Tru64 Persistent Hardware Database (PHDB) has entries which are incompabile with the target platform and thus must be replaced with a clean version.

This procedure can also be used if there are invalid entries in the PHDB that the customer does not wish to see. As the PHDB does not forget entries (persistence), after a migration the old disk, tape, network, and possibly other devices will still be present in the PHDB, but invalid.

PLEASE NOTE: This procedure can only be used on a single (not clustered) sytem. A different, and more complex, procedure must be used for a TruCluster node.

Step-by-step guide

Prerequisites

  • The Tru64 UNIX installation CDROM image that corresponds to the version on the original system
  • An emulator (or an Alpha) with a vdisk (or disk) to which the OS has been migrated ("target system disk") and CDROM to boot the above

Procedure

  1. Make sure the SRM environment variable "bootdef_dev" is NOT set. If the "bootdef_dev" variable points to your target system disk, the CDROM boot procedure will attempt to use the existing PHDB.
    P00>>>set bootdef_dev ""
  2. Boot from the Tru64 installation CDROM
    P00>>>boot dkaXXX
  3. Mount the target system disk root partition
    (assumption: AdvFS)
    # cd /etc/fdmns
    #     mkdir root
    # hwmgr show scsi
    (identify target system disk. example: "/dev/disk/dsk0")
    # ln -s /dev/disk/dsk0a root/
    # mkdir /tmp/root
    # mount root#root /tmp/root
  4. Clean up old PHDB files
    # cd /tmp/root/etc
    # rm -f dec* df* dc* cfginfo
    # rm -f /tmp/root/cluster/members/member/etc/df*
    # rm -f /tmp/root/cluster/members/member/.Booted
  5. Unmount target root fileset
    # cd /
    # umount /tmp/root
  6. Halt in-memory (CDROM-based) system
    # halt
  7. Boot from target disk in single-user mode
    (This is the point at which the new PHDB is created)
    P00>>>boot -fl s -fi genvmunix dkaX
  8. Mount root fileset read/write (you will see messages indicating a new PHDB is being created)
    # mountroot
  9. Fix Advfs symbolic links
    # hwmgr show scsi
    (identify target system disk. Example: "/dev/disk/dsk0")
    # cd /etc/fdmns
    # rm root_domain/* usr_domain/*
    # ln -s /dev/disk/dsk0a root_domain/
    # ln -s /dev/disk/dsk0g usr_domain/
  10. Mount all filesystems
    # bcheckrc
  11. Fix swap in /etc/sysconfigtab
    vm:
      swapdevice = /dev/disk/dsk0b
  12. Build new kernel
    # doconfig -a

Related articles


<Go to Top>


© Stromasys, 1999-2024  - All the information is provided on the best effort basis, and might be changed anytime without notice. Information provided does not mean Stromasys commitment to any features described.