Duplicate COVECUBECoveFsDisk______ drives

[marko]

My pool consists of four drives totalling 29Tb. This is correctly displayed in "This PC" and also in the Volume list inside Disk Management.

However, in the disk list below,  where it is Disk #15, it is shown as having a capacity of 2048 Gb, and, two Disk #15's are listed. Every time I open Disk Management, it prompts me to initialise this rogue disk, which always fails.

Hopefully, the attached images will help explain what I'm seeing.

How can I correct this?

Thanks for reading,

-Mark

 

[Shane]

Glad it fixed itself!

Each pool should be visible in Windows Disk Manager as a 2048.00 GB NTFS primary partition on a 2048.00 GB Basic disk. Opening the Properties of that partition should show the combined size (used, free, capacity) of the actual drives that form that pool.

The unallocated disk COVECUBECoveFsDisk____ that showed up is the virtual disk failing to be initialised for some reason during boot, though it's (even) weird(er) that it also showed as an initialised version too.

[marko]

This morning, I figured I would try and fix this by removing/re-installing Drivepool, but, did not need to.

When I opened the app to release the license, I noticed that the rogue drive was no longer visible in the non-pooled list. There was a notification in top left corner regarding duplication (I do not use duplication). I can't remember the exact text, but it read like a routine Drivepool pool maintenance task had completed.

Checked Disk Manager, and things are all good in there too.

It would appear that either Windows, or Drivepool has taken care of this for me. Long may it stay that way

 

The issue of Disk Manager showing a 29Tb volume on a 2Tb disk still persists though. Is that something I should be concerned about?

 

[marko]

4 hours ago, Shane said:

Glad it fixed itself!

Each pool should be visible in Windows Disk Manager as a 2048.00 GB NTFS primary partition on a 2048.00 GB Basic disk. Opening the Properties of that partition should show the combined size (used, free, capacity) of the actual drives that form that pool.

Thanks for the confirmation regarding that. What I see now is exactly as you describe.

 

4 hours ago, Shane said:

The unallocated disk COVECUBECoveFsDisk____ that showed up is the virtual disk failing to be initialised for some reason during boot, though it's (even) weird(er) that it also showed as an initialised version too.

It was weird. The fact I was showing 2 x Disk #15 was worrying too. All appears to be good now though.

Thank you for taking the time to reply. It is appreciated.

-Mark

[Christopher (Drashna)]

Yeah, sometimes .... Windows will double add the disk, if it's mounted too quickly.  It's ... weird.

ALso, if this happens again, you can uninstall the drives (all of them) in Device manager (but don't delete the driver), and reboot the system.  This should also correct the doubled drive.