Thanks to Patrick van Gool, Johan Brusche, Robery Mulley for quick
responses.
For a non-root disk the volclonedg command can be used to save/restore the
LSM configuration and import it to the new disk WWID. For the root disk this
cannot be done, but starting vold without autoconfig and then manually
importing the disk group may work (vold -k -x noloadbalance -x noautoconfig
; voldg -f import rootdg)
However, I didn't try that because there was a much easier solution I had
totally overlooked... Rather than hack around with the WWID stored in LSM,
it is much easier not to use dd for cloning the disk but to create the clone
using LSM itself so that the new disk WWID is added into the LSM database
*before* transferring the disk to the new system.
In my case, the root disk was already encapsulated by LSM into rootdg using
volencap, hence adding the new blank disk to the root mirror set is trivial.
Using volrootmir to mirror from the rootdg to the new disk will then
transfer an exact LSM copy of the working system. Once the mirror / datasync
has completed shutdown the system then transfer the new disk to the clone
system and it's all set.
A side note: volrootmir is much faster on 5.1b than it used to be on 4.0f
because it actually copies only the blocks in use on the filessytems, not
the entire binary bitmap of the disk as dd does.
thanks.
-----Original Message-----
From: Iain Barker [mailto:ibarker_at_aastra.com]
Sent: Thursday, 04 September, 2003 21:04
To: tru64-unix-managers_at_ornl.gov
Subject: How to change the WWID of an LSM volume or SCSI drive
Hi.
I am trying to create an exact clone of a Tru64 5.1b system. It uses LSM
encapsulation and AdvFS on the root disk.
I tried disk labelling a spare drive, booting single user readonly and using
dd to copy the drive contents across to the new disk. But the WWID used by
LSM is causing problems for vold:
lsm:vold: WARNING: Disk dsk0b: Disk rejected as clone
lsm:vold: WARNING: Disk dsk0g: Disk rejected as clone
lsm:vold: WARNING: Disk dsk0h: Disk rejected as clone
lsm:vold: ERROR: enable failed: Error in disk group configuration copies
No valid disk found containing disk group; transactions are
disabled.
LSM: Vold is not enabled for transactions
No volumes started
I can boot the disk to single user OK, but vold won't start for LSM due to
the above.
How can I either:
1. Change the WWID of the SCSI disk so that it is identical to the one it
was cloned from
or
2. Change the WWID stored inside the LSM record to match that of the new
disk.
Failing that, is there any other way to make a working clone of the root
disk?
This is using the internal Adaptec SCSI of a DS20 system, no TruCluster.
thanks.
Received on Fri Sep 05 2003 - 14:39:04 NZST