Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
13,726 questions
Disk collision occurs after backup/snapshot operations
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(32, 57.00000000000001%, 13%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKL%3C/text%3E%3C/svg%3E)
Kenneth Løken / Intility AS
0
Reputation points
Hello!
I'm having some issues with some of our servers where the second drive (data drive volume, D:) goes offline after backup/snapshot operations.
Happens across Windows Server 2016, 2019 and 2022. VMware hypervisor.
This error message is seen in Disk Management in Windows:
"The disk is offline because it has a signature collission With another disk that is online"
Happens unfrequently and randomly with different VM's with different roles and applications. We see no consistency in which virtual machines that experience this. They are across different storage, different hypervisors and different networks.
The "fix" is very simple, which is to right click and press "online". This forces windows to generate a new random disk signature and assign it to the disk by writing it to the MBR.
Referring to MS doc:
Has anyone seen this problem or could provide some insights as to why this may be happening?
Thank you in advance!
Windows Server
{count} votes
-
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(147.20000000000002, 71%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERH%3C/text%3E%3C/svg%3E)
Rick Hogan 0 Reputation points2024-08-02T19:57:32.8666667+00:00 I just found this post of yours. It sounds like your problem is a little different than mine. The problem we see is that Windows detects a disk signature collision between the actual disk and the shadow copy of the disk. This apparently is normal and always happens every time a full disk shadow copy is created. Where it goes wrong for us is that sometimes, Windows will force the real disk offline due to the collision.
Sign in to comment
Sign in to answer