Installing 5.1a onto an LSM system

From: McCracken, Denise (Denise.McCracken_at_misyshealthcare.com)
Date: 03/16/05

  • Next message: jgz_at_thezimmermans.org: "rlogin/rsh" 
    Date: Wed, 16 Mar 2005 15:18:10 -0700
To: "Tru64 managers' list (E-mail)" <TRU64-UNIX-MANAGERS@ornl.gov>

            I have found that when I install 5.1a onto a 4.0f system that
    previously had LSM root drive(s), and I install onto a drive other than one
    of the 4.0f root drives, the installation does "checking for a previous LSM
    configuration" before it installs. It goes back and picks up all of the
    definitions from the old root drives, and I have garbage like this in my LSM
    configuration:

    >From volprint:

    TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0
    PUTIL0
    dg rootdg rootdg - - - - - -
     
    dm rz16a - - - - NODEVICE - -
    dm rz16b - - - - NODEVICE - -
    dm rz16d dsk0d - 0 - - - -
    dm rz16g - - - - NODEVICE - -
    dm rz16h - - - - NODEVICE - -
    dm rz18a - - - - NODEVICE - -
    dm rz18b - - - - NODEVICE - -
    dm rz18d dsk2d - 0 - - - -
    dm rz18g - - - - NODEVICE - -
    dm rz18h - - - - NODEVICE - -

    >From voldisk list:

    rz16a nopriv - - error
    rz16b nopriv - - error
    rz16d simple - - error
    rz16g nopriv - - error
    rz16h nopriv - - error
    rz17 sliced - - error
    rz18a nopriv - - error
    rz18b nopriv - - error
    rz18d simple - - error
    rz18g nopriv - - error
    rz18h nopriv - - error
    - - rz16b rootdg failed was:rz16b
    - - rz16g rootdg failed was:rz16g
    - - rz16h rootdg failed was:rz16h
    - - rz16a rootdg failed was:rz16a
    - - rz18a rootdg failed was:rz18a
    - - rz18b rootdg failed was:rz18b
    - - rz18g rootdg failed was:rz18g
    - - rz18h rootdg failed was:rz18h

            I can install the OS with a customized install.cdf. Is there any
    way that I can tell the installer not to go back and look for that previous
    LSM configuration? When I install onto one of the old root drives, I just
    remove the d parition from the mirror, but obviously I can't do that from
    both sides of the mirror before I shut down, nor can I deport rootdg. I'm
    doing this remotely, so removing a disk isn't an option. I've tried setting
    bootdef_dev to null and that doesn't help.

            Any ideas?

    thanks

    -denise

    "Customer service may be the only way that a
    company can distinguish itself from its
    competition these days." -H. Frank Gibbard

    Denise McCracken, Systems Software Specialist
    Misys Healthcare Systems, Tucson, AZ

    Certified Tru64 v5 Systems Administrator
    Comptia Network+ Certified Professional

  • Next message: jgz_at_thezimmermans.org: "rlogin/rsh"

    Relevant Pages

    • lsm has done its own thing when I tried to change boot disks.
      ... previously was running 5.1 from another lsm boot disk. ... the install, I partitioned my 9gb disk, and then did the install. ... As you can see the offending partition is dsk1h ...
      (Tru64-UNIX-Managers)
    • Re: Need help in Package Wizard
      ... Tony Toews [MVP] wrote: ... install into root drive like "C:" or any other root drives. ... Why not use the users My Documents folder? ...
      (microsoft.public.access.devtoolkits)
    • Need help in Package Wizard
      ... I was using the Package Wizard to distribute my application. ... install into root drive like "C:" or any other root drives. ... choice of Program Files, Common files, user's My Document. ...
      (microsoft.public.access.devtoolkits)