Page 1 of 1

Cloning and disk signature collisions

Posted: June 17th, 2019, 7:47
by snifferpro
I do both a clone of my C drive and an image backup.

On a couple of occasions I have had to boot the newly cloned drive and forgot to remove the original source drive.

This gives me Disk Signature collision which I think I understand.

What I'd like to do is change the disk signature of the original source drive which is a GPT SSD.

All the articles I've found on the net seem to suggest using diakpart which I have no problems using. Where I do have an issue is with determining how to provide a new disk signature.

What is the format of the GUID GPT disk signature?

How do I create a new disk signature? Is it just a string of random numbers?

If diskpart doesn't like the format or the actual id how do I create one that diskpart will accept.

Thanks

Re: Cloning and disk signature collisions

Posted: June 17th, 2019, 20:03
by fzabkar
snifferpro wrote:How do I create a new disk signature? Is it just a string of random numbers?

What is Disk Signature Collision? How to fix Disk Signature Collision problem on Windows?
https://www.thewindowsclub.com/disk-signature-collision-problem

The signature consists of 8 random hexadecimal digits (4 bytes) in sector 0.

An Examination of the Windows 7, 8/8.1 or 10 MBR ( Master Boot Record ):
https://thestarman.pcministry.com/asm/mbr/W7MBR.htm

An Examination of The Microsoft Windows 7 and 8 GPT 'Protective' MBR and EFI Partitions:
https://thestarman.pcministry.com/asm/mbr/GPT.htm

These four bytes from offsets 1B8h through 1BBh are called the Windows Disk Signature or NT Drive Serial Number.

You can examine sector 0 with a disc editor such as DMDE:

https://dmde.com/

Re: Cloning and disk signature collisions

Posted: June 18th, 2019, 6:12
by snifferpro
fzabkar - Thank you very much for your answer and links. It definitely helps clear things up for me.