Hi all,
I'm trying to get together a procedure allowing us to clone system disks
from a read only SAN attached disk and alter them for use with different
machines. The OS alterations are almost complete but I've struck a
problem with LSM rejecting the disk as a clone when I boot it up from
the new hardware. The device database has been rebuilt for the new
machine and the disk device special files are the same as they were in
the original LSM configuration so the rest of the LSM config should
match up.
I can see from a previous summary that the question has been asked
before but not really answered - how can I change the LSM config to
recognise the wwid of this disk and not reject it as a clone? In the
example shown below I've unencapsulated root, user and var to get the
machine to boot but I'd prefer not to have to do that either. Building
the mirror online using LSM is not what this customer was wanting so I'm
hopeful that with the help of the list I'll be able to get this working.
Thanks in advance,
Danielle.
13:16:53 starting LSM in boot mode
13:16:53 lsm:vold: WARNING: Disk dsk2f: Disk rejected as clone
13:16:53 lsm:vold: WARNING: Disk dsk2g: Disk rejected as clone
13:16:53 lsm:vold: WARNING: Disk dsk2h: Disk rejected as clone
13:16:53 lsm:vold: ERROR: enable failed: Error in disk group
configuration copi
13:16:53 No valid disk found containing disk group; transactions are
disabled.
13:16:53 lsm:vold: FATAL ERROR: Rootdg cannot be imported during boot
13:16:54
**********************************************************************
This message is intended for the addressee named and may contain
privileged information or confidential information or both. If you
are not the intended recipient please delete it and notify the sender.
**********************************************************************
Received on Tue Jun 15 2004 - 23:14:51 NZST