From: McCracken, Denise (Denise.McCracken@misyshealthcare.com)
Date: Thu Jan 16 2003 - 21:21:30 EST
This is weird. I did a 5.1a fresh start upgrade and recovered my
LSM stuff OK, but when I reboot the system, LSM does not start. I ran the
following commands to restore LSM, and I still have to run them every time
the system boots:
vold -k -r reset -m disable -x nohostid
voldctl init
voldctl enable
Then I can do a volume start on each volume and they come back to
life.
I tried an encapsulation of the root disk (before I knew I had this
problem) and all that came back encap'd was the rootvol. swap2
encapsulated, but couldn't be activated because LSM wasn't going. The root
filesystem is now /dev/vol/rootdg/rootvol, but the disklabel on the root
disk doesn't show any LSM on it, and I can't run a voldisk list or anything
until I repeat the above commands.
My inittab has:
lsmr:s:sysinit:/sbin/lsmbstartup -b </dev/console >/dev/console 2>&1 ##LSM
lsm:23:wait:/sbin/lsmbstartup </dev/console >/dev/console 2>&1 ##LSM
vol:23:wait:/sbin/volreconfig -n </dev/console >/dev/console 2>&1 ##LSM
But running these commands after reboot manually does not start LSM.
Any ideas? I have a machine down while I work this out, so anything would
be appreciated.
-D
Denise McCracken
MiSys Healthcare Systems
Denise.McCracken@misyshealthcare.com
(520) 570-2521
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:04 EDT