Disk Signature Collision under Windows 10?

[stockhausen]

I have been "scrapping some PCs and before doing so I extracted the 1TB HDDs from them.
When I try connecting them to a Windows 10 system, all at the same time one of them is not seen.

If I go into "Computer Management" => "Disk Management", one of them is seen but it is not available in File Explorer. If I click on the (i) I get the message "Disk Signature Collision". If I connect each HDD up individually - no problem. I have a vague feeling that at some time they (not recently) may have been part of a RAID-5 array.

Any idea how this situation has arisen and how I can correct it?

 

[stockhausen]

Thanks for that @Murphy

Hard disks on a Winows 10 system each have an allegedly unique signature / identifier; this is contained in the master Boot Record (MBR). Under earlier Windows systems (pre Windows 7), if duplicate signatures were spotted they would be automatically adjusted - seems sensible.
However, this is no longer the case - the 2nd "offending" disk will be placed offline and there is no very obvious way of mounting it - seems stupid but I am sure that Microsoft has a great justification.

In my case I ran the Command prompt with Administrator rights, went into Diskpart, checked the signature of all the HDDs, Selected the offending disk and altered the duplicate signature with a command along the lines "unique disk ID=ABCDEF01". I then rebooted the system and everything seemed as it should.

I found the means to do this by Googling "disk signature collision" and looking at the "Minitool" explanation.