LSM configuration won't stick

From: McCracken, Denise (Denise.McCracken_at_misyshealthcare.com)
Date: 05/17/04

  • Next message: Neil R. Smith: "SUMMARY: 5.1B SSH on 5.1?" 
    Date: Mon, 17 May 2004 14:47:16 -0700
To: "Tru64 managers' list (E-mail)" <TRU64-UNIX-MANAGERS@ornl.gov>

            I'm having a problem recovering my LSM after a 4.0f to 5.1a upgrade.
    This appears to happen only when we have mirrored root drives with another
    volume(s) in rootdg. I run the following procedure and then I can mount up
    my drives, but after I do a reboot, the LSM doesn't come back and I have to
    do it all over again. Any ideas?

    ____ # volinstall

    _____ # vold -k -r reset -m disable -x nohostid

    _____ # voldctl init

    _____ # voldctl enable

    (ignore these warnings. They're from the old root drives)
    lsm:vold: WARNING: Disk rz8d in group rootdg: Disk device not found
    lsm:vold: WARNING: Disk rz8b in group rootdg: Disk device not found
    lsm:vold: WARNING: Disk rz8g in group rootdg: Disk device not found
    lsm:vold: WARNING: Disk rz8a in group rootdg: Disk device not found
    lsm:vold: WARNING: Disk rz8h in group rootdg: Disk device not found
    lsm:vold: WARNING: Disk rz10a in group rootdg: Disk device not found
    lsm:vold: WARNING: Disk rz10b in group rootdg: Disk device not found
    lsm:vold: WARNING: Disk rz10g in group rootdg: Disk device not found

    _____ # volprint -A

    If any disk group that was there before (see your printout) is missing, it
    may need to be imported.

                    Example:

                    # voldg -o convert_old import sqdg

    ____ Start all volumes

            Example:
    # volume -g sqdg start sqvol
    # volprint -g sqdg

    This is where they mount up, but they're gone after the first reboot.

    thanks

    -d

    "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: Neil R. Smith: "SUMMARY: 5.1B SSH on 5.1?"

    Relevant Pages

    • LSM: It Burns!
      ... lsm:voldctl: ERROR: enable failed: Error in disk group configuration copies ... lsm:vold: WARNING: Disk rz0d in group rootdg: Disk device not found ...
      (Tru64-UNIX-Managers)
    • Re: [PATCH] make kernel ignore bogus partitions
      ... disk device. ... This patch makes the kernel ignore those partitions. ... while doing forensics on a disk one copies the start to some ... A loud warning may be more appropriate than an ignore. ...
      (Linux-Kernel)
    • DS10 missing devices in OS, but not SRM
      ... Here was the first clue upon boot that something wasn't quite right: ... lsm:vold: WARNING: Disk disk02 in group rootdg: Disk device not found ...
      (Tru64-UNIX-Managers)
    • k3B
      ... /usr/bin/cdrecord: WARNING: This causes a high risk for buffer underruns. ... Profile: 0x0009 ... /usr/bin/cdrecord: WARNING: Data may not fit on current disk. ... CUE sheet still not accepted. ...
      (alt.os.linux.suse)
    • Solaris RAID failover problems
      ... My intent is to mirror the drives completely, ... Can't read disk label. ... WARNING: md: d10: needs maintenance ... WARNING: forceload of misc/md_trans failed ...
      (comp.unix.solaris)