LSM configuration won't stick

From: McCracken, Denise (Denise.McCracken@misyshealthcare.com)
Date: Mon May 17 2004 - 17:47:16 EDT


        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



This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:59 EDT