From: McCracken, Denise (Denise.McCracken@misyshealthcare.com)
Date: Tue May 06 2003 - 16:53:10 EDT
Yes, it's time once again for another stupid LSM problem with a 4.0f to
5.1a fresh start upgrade.
As I have been doing, I installed 5.1a on one side of the old mirror.
The install was set for UFS. The LSM configuration should be retained in
the d partition of the other side of the mirror and I should be able to
recover it when it comes back up on 5.1a, but...
# voldctl init
# voldctl enable
lsm:vold: ERROR: enable failed: Error in disk group configuration copies
No valid disk found containing disk group; transactions are
disabled.
lsm:voldctl: ERROR: enable failed: Error in disk group configuration copies
Argggh! Where did my configuration go? It seems that parts of it are
still here but the machine just refuses to see it...
# vold -k -r reset -m disable -x nohostid
#
# voldctl init
# voldctl enable
lsm:vold: WARNING: Disk rz0d in group rootdg: Disk device not found
lsm:vold: WARNING: Disk rz0b in group rootdg: Disk device not found
lsm:vold: WARNING: Disk rz0g in group rootdg: Disk device not found
lsm:vold: WARNING: Disk rz0h in group rootdg: Disk device not found
lsm:vold: WARNING: Disk rz0a in group rootdg: Disk device not found
lsm:vold: WARNING: Disk rz8a 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 rz8h in group rootdg: Disk device not found
OK, now I seem to have to configuration back for my root drives (these
warnings are normal), but where are all my other disk groups?
# volrecover -sb
# volprint -v
Disk group: rootdg
TY NAME ASSOC KSTATE LENGTH PLOFFS STATE TUTIL0
PUTIL0
v rootvol root DISABLED 262144 - ACTIVE - -
pl rootvol-01 rootvol DISABLED 262144 - NODEVICE - -
sd rz0a-01p rootvol-01 DISABLED 16 0 NODEVICE - -
sd rz0a-01 rootvol-01 DISABLED 262128 16 NODEVICE - -
pl rootvol-02 rootvol DISABLED 262144 - NODEVICE - -
sd rz8a-01p rootvol-02 DISABLED 16 0 NODEVICE - -
sd rz8a-01 rootvol-02 DISABLED 262128 16 NODEVICE - -
v swapvol swap DISABLED 261120 - ACTIVE - -
pl swapvol-01 swapvol DISABLED 261120 - NODEVICE - -
sd rz0b-01 swapvol-01 DISABLED 261120 0 NODEVICE - -
pl swapvol-02 swapvol DISABLED 261120 - NODEVICE - -
sd rz8b-01 swapvol-02 DISABLED 261120 0 NODEVICE - -
v swapvol2 fsgen DISABLED 15815636 - ACTIVE - -
pl swapvol2-02 swapvol2 DISABLED 15815636 - NODEVICE - -
sd rz8h-01 swapvol2-02 DISABLED 15815636 0 NODEVICE - -
pl swapvol2-01 swapvol2 DISABLED 15815636 - NODEVICE - -
sd rz0h-01 swapvol2-01 DISABLED 15815636 0 NODEVICE - -
v usrvol fsgen DISABLED 1433600 - ACTIVE - -
pl usrvol-02 usrvol DISABLED 1433600 - NODEVICE - -
sd rz8g-01 usrvol-02 DISABLED 1433600 0 NODEVICE - -
pl usrvol-01 usrvol DISABLED 1433600 - NODEVICE - -
sd rz0g-01 usrvol-01 DISABLED 1433600 0 NODEVICE - -
No other dg's showing up, just rootdg. I don't care about all of that
"rz" garbage...I remove those old plexes anyway. What I want is to have my
other dg's back! Why are the disks showing up "online" to voldisk but not
recognized anywhere else?
# voldisk list
DEVICE TYPE DISK GROUP STATUS
dsk0 sliced - - unknown
dsk1c simple - - online
dsk2c simple - - online
dsk3 sliced - - unknown
dsk4d simple rz8d rootdg online
dsk5c simple - - online
dsk6c simple - - online
dsk7 sliced - - unknown
For instance, dsk1c up there belonged to another disk group and it's
still under LSM control....but the disk group is gone!
I'm using the same method here that has worked before. What could have gone
wrong?
thanks
-Denise
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:49:18 EDT