Recompose Linked Clone Desktops - duplicate disks

[millski]

Hi,

I've got an issue when recomposing Linked Clone Desktops. On the ones that have errors next to them, it appears that they generate a second harddisk drive which is the same as the original disk. ie; My parent vm is 10gb. The linked clone is 10gb and then after a recompse is complete I have the original (10gb) and a new second disk that is 10gb. This causes the normal duplicate UUID error message, and the only way to power it on is to say yes to the message.

My environment is View 4.0, and the guest VM's are all WinXP SP3.

My question is really on the end of how to actually clean up the vm's that have this duplicate disks. Is there a known method to removing the old / incorrect disk and bringing it back to the original form.

Thanks

Alan

[mittim12]

So how many disk are present after this happens? Anyway to post a screen shot of it so that we have a better idea? Anything in the composer logs that would maybe indicate what is happening?

I haven't seen any known methods for cleaning up something like that. What happens if you recompose it again?

If you found this or any other post helpful please consider the use of the Helpful/Correct buttons to award points

Twitter: http://twitter.com/mittim12

[millski]

Normally we have 3 disks. Disk 0:0 (OS), Disk 1:0 (Internal Disk), Disk 1:1 (User Data Disk). After the recompose, I beleive the ones that have been gone into a error state for whatever reason, geneates a new duplicate disk. So I end up with 4 disks and the new disk sits on the SCSI Controller 0 under channel 0:1. It is exactly the same size as the OS Disk - in my case 10Gb.

I've tried a recompose / refresh, and the disk remains without getting cleaned up. If I remove one of the disks that have been duplicated, and then go back to a refresh or a recompose, the disk comes back again.

I had forgotten about looking at the view composer logs - off to trawl throught them now. Not exactly sure what to look for though.

Thanks for the help

Alan

[millski]

Never managed to get an answer to this, but we've upgraded to View 4.6 - so considering issue closed.