Jump to content
  • 0

Duplication Warnings


stalfos

Question

Hello,

Recently I began the task of switching out my 2TB drives for some 4TB drives. In the process, something went wrong, I am not sure what. Transfers to the pool would freeze, lock up my system, I unfortunately had to do some force shutdowns. Windows then seemed to have trouble fully accessing the drives - I could not do a dskchk as "another process had control of them" (or something of this nature).

 

I struggled with this for several days, eventually moved the 4TB drives to a spare system, formatted them, installed Drivepool trial to this sytem, got the pool fully set-up and all data migrated to the pool.

 

The I fully wiped my main system (reinstalled Windows), moved the 4TB drives back into it (Drivepool not setup yet). Everything working fine, can see the disks, can access the contents in the hidden Poolpart folders etc. Can run CHKDSK on them, no problems.

 

Now I reinstall Drivepool to this system and I am greeted with this:

(see attached)

I don't know how to safely resolve this warning message. Is it caused by moving disks from one system to another ?

I also am not sure which disk this pertains to. The Drivepool log would seem to indicate it pertains to HarddiskVolume9 with ID ending in 1c7925dd2569

DrivePool.Service.exe	Information	0	[CoveFs] Pool found on: \\?\GLOBALROOT\Device\HarddiskVolume9 (pool ID=6a84a3c4-b61d-4959-a7c3-1c7925dd2569)	2018-07-09 16:57:51Z	120647360

DrivePool.Service.exe	Warning	0	[FileDuplication] Duplication conflict detected for file '\\?\GLOBALROOT\Device\HarddiskVolume9\System Volume Information\IndexerVolumeGuid' (file part contents is different)	2018-07-09 16:59:15Z	363768255

However I cannot locate this disk on my system

\\?\Volume{2e061839-0000-0000-0000-100000000000}\
        *** NO MOUNT POINTS ***

    \\?\Volume{08f4e0e4-5b69-4403-84e6-26ba0114df68}\
        I:\

    \\?\Volume{c49d9602-adfb-472e-ac7e-f3aea119e096}\
        F:\

    \\?\Volume{9931b5bf-4af9-4e13-8d14-d747a49f0f59}\
        G:\

    \\?\Volume{9374b2b6-68d9-4c9c-8842-be6a7fe4c417}\
        H:\

    \\?\Volume{0b494ac8-41da-4fad-a5a3-b483e71ea4a2}\
        E:\

    \\?\Volume{89bb8c95-ad41-45b2-ba8f-081029facb20}\
        J:\

    \\?\Volume{2e061839-0000-0000-0000-602200000000}\
        C:\

    \\?\Volume{cd6a3a61-8385-11e8-88ff-806e6f6e6963}\
        D:\

Untitled.jpg

Link to comment
Share on other sites

3 answers to this question

Recommended Posts

  • 1

It means the pool drive.  And yeah... how Windows handles disk/partition/volume stuff is confusing... at best. 

For this ... take ownership of the folder, change it's permissions, and delete it (on the pool). 

Then resolve the issue.  It should fix the issue, and shouldn't come back. 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...