DrivePool keeps saying drive is missing when it is not

[jaydee]

Hello,

I have a situation that is driving me nuts. DrivePool suddenly says that a drive is missing when it is not. The drive is visible in Windows Explorer. I can navigate to the drive, read and write files to it, etc. The drive even shows up in the list of Non-pooled drives in the DrivePool UI with an Add button beside it. When this happened yesterday, I removed the drive via the DrivePool UI. Then I re-added it, and it created a new PoolPart folder on the drive. I used robocopy to move all the files from the old poolpart folder to the new one, and then re-measured the pool, and everything seemed fine. Now, today it is the same situation. I noticed today that it happened right after I removed a different drive from the pool. I don't know if that had something to do with it? I'm assuming it's not an issue with the drive itself, as it is a brand new drive and functions fine otherwise.

I'm running DrivePool on Windows 10.

Am I resolving this issue correctly by removing and re-adding and then copying the data and re-measuring? Or am I doing something wrong? Is there any way I can troubleshoot this better?

Thank you!

[Shane]

8 hours ago, jaydee said:

I noticed today that it happened right after I removed a different drive from the pool

This is twitching my brain for some reason. Were both drives running off the same controller or USB device? Is it part of an older pool or a newer one?

8 hours ago, jaydee said:

Am I resolving this issue correctly by removing and re-adding and then copying the data and re-measuring?

Assuming you didn't make any other changes to the pool, you could directly move the user content (not sysvol, not recycle bin, not .covefs) of the disk's old poolpart folder into the disk's new poolpart folder instead of copying to the new folder then deleting from the old folder.

8 hours ago, jaydee said:

I'm assuming it's not an issue with the drive itself, as it is a brand new drive and functions fine otherwise.

That should be the ideal, yeah. But if you've the time and space to do so, you could evacuate the drive and then either quick-format and chkdsk /r (for a SSD) or long-format (for a HDD) it to be sure.

[GSMenace]

I have some of my drives dropping and windows does not see them again until a Hard reset.

[Shane]

Hard reset as in restarting Windows, reinstalling Windows or resetting Drivepool via the latter's Troubleshooting menu?

[TomN]

Was there any resolution to this other than take the drive out of the pool and then put it back as part of it, and manually move the files into the new pool directory?  I just did an in-place upgrad from Server 2019 to Server 2025 and am having this exact issue (with multiple drives in a 44 drive pool).  I can see the drives in Disk Management, I can even see them in Scanner as healthy.  But they don't show up in the pool (says missing).  Worked perfectly fine in Server2019.  Wondering if this is an in place upgrade issue or something else, thank you!

 

EDIT: I removed it from the pool, mapped the drive to a letter.  And got an error saying "This version of Windows doesn't support the ReFS format"  UGH!  Now to dig through posts to find a fix.  The other drives are ReFS and work just fine. I tested the drive on a Windows 11 machine and was able to map it no problem