How to change the WWID of an LSM volume or SCSI drive

From: Iain Barker (ibarker@aastra.com)
Date: Thu Sep 04 2003 - 21:03:39 EDT

• Next message: Himanshu Khona: "Performance analysis of tru 64 unix system alpha 2000 with tru64 O.S. 4.0D ..update"
• Previous message: Tom Webster: "HSZ70 Trans Failover Config Q's"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

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.

• Next message: Himanshu Khona: "Performance analysis of tru 64 unix system alpha 2000 with tru64 O.S. 4.0D ..update"
• Previous message: Tom Webster: "HSZ70 Trans Failover Config Q's"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]

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