Jump to content
  • 3

Win10 build broke DrivePool how to fix?

XtremeMaC

Asked by XtremeMaC,

 Share

Question

XtremeMaC Newbie

XtremeMaC

Posted
Posted

Hello,

I'm on Fast Ring in Win10. Yesterday's update broke Drive Pool that's super crucial for me and few others that are not crucial.

I went the normal way, uninstalled, cleared appdata, cleared bunch of registry entries, uninstalled drivers as much as I can find along with Scanner. also uninstalled the Covecube drive under Hardware...

Yet still, I see the covecube as a drive and it won't let me add any drives to a new pool. How can I delete the so called existing pool that is no longer shown...

 

Surely not DrivePool's fault, but how can I fix this? Any ideas?

image.png.fc0e08174c5a3e8d9f6be2d11ee09159.png

image.png.d8e5fdea4e46ea3f7190b1ca5799a987.png

 

Yes, I know I can return to previous build, that's more headache, I'd rather try to fix the current one. Should have been as easy as re-install drivepool... looking for help

24 answers to this question

Recommended Posts

  • 0
XtremeMaC Newbie

XtremeMaC

Posted
  • Author
Posted

  

On 7/5/2020 at 9:43 AM, PalmPilot said:

It looks like DrivePool beta .1152 addressed the issue. Did anyone try it already? 


.1152
* Included balancing plugins with the main installer.
* [D] Rebuilt the virtual disk driver.
    - Using the latest tooling.
    - Certified for Windows Server 2019.
    - Fixed GPT emulation (was causing issues on Windows 10 Insider Preview).

From:

http://dl.covecube.com/DrivePoolWindows/beta/download/changes.txt

http://dl.covecube.com/DrivePoolWindows/beta/download/

Thanks for the links!

Just installed "StableBit.DrivePool_2.3.0.1152_x64_BETA.exe" on both below

1) Win 10 Pro Insider | v2004 | Build 20161.1000 | Full Build Number: 20161.1000.Rs_prerelease.200627-1754.

2) Win 10 Pro Insider | v2004 | Build 19645.1

After a restart of course, DrivePool is working properly on both! 

Thanks CoveCube team! 

 

  • 1
PalmPilot Newbie

PalmPilot

Posted
Posted

It looks like DrivePool beta .1152 addressed the issue. Did anyone try it already? 

.1152
* Included balancing plugins with the main installer.
* [D] Rebuilt the virtual disk driver.
    - Using the latest tooling.
    - Certified for Windows Server 2019.
    - Fixed GPT emulation (was causing issues on Windows 10 Insider Preview).

From:

http://dl.covecube.com/DrivePoolWindows/beta/download/changes.txt

http://dl.covecube.com/DrivePoolWindows/beta/download/

  • 1
Jimpc Newbie

Jimpc

Posted
Posted

Just tested the latest Drivepool beta. It does not fix the issue. 

 

Edit: Uninstall an reinstall did the trick. Thanks Christopher.

  • 0
afaroutdude Newbie

afaroutdude

Posted
Posted

I had the same problem.  Support pointed me to these instructions, which I followed to no avail: https://wiki.covecube.com/StableBit_DrivePool_Q3017479

I reverted from 20150.rs_prerelease.200612-1734 to 19645.mn_release.200605-1502 via Windows Update Settings -> Recovery -> Go back to the previous version of Windows 10 and the symptoms are gone, my old pool showed up immediately with no issues.  

Super interested to hear of a real solution!

  • 0
RED-404 Newbie

RED-404

Posted
Posted

Yeah I figured rolling back would work but testing is testing. Lol I even did that wiki thing without even knowing about it. I've open a ticket and sent more logs including inf logs showing the driver having trouble with a 0x0D error. Interestingly its not exclusively a DrivePool error I also gave DriveBender a shot and it just stalls on assigning a drive letter.

  • 0
jfreiman Newbie

jfreiman

Posted
Posted
2 hours ago, afaroutdude said:

I had the same problem.  Support pointed me to these instructions, which I followed to no avail: https://wiki.covecube.com/StableBit_DrivePool_Q3017479

I reverted from 20150.rs_prerelease.200612-1734 to 19645.mn_release.200605-1502 via Windows Update Settings -> Recovery -> Go back to the previous version of Windows 10 and the symptoms are gone, my old pool showed up immediately with no issues.  

Super interested to hear of a real solution!

I tried rolling back as well but that didn't solve my problem.  I now have multiple COVECUBECoveFs____ "drives" and/or partitions.  Then I really screwed up and followed an older thread which had me move my files from the hidden folders and rebuild the drivepools - now I have a whole bunch of mixed up and folders and files spread across 8 10/12TB hard drives.  :(

  • 0
XtremeMaC Newbie

XtremeMaC

Posted
  • Author
Posted

I rolled back to previous build and currently have no problem. I had to pause the updates for a week. 

This build also weirdly messed up Adobe Reader for some reason.. Re-install fixed that. 

For sure this thread will not get many hits as it's clearly an MS problem, however it'd be nice to know a way to completely remove every aspect of CoveCube/StableBit/DrivePool/etc... 

I must have missed a few registry entries, and a few I saw but needed system privileges, didn't bother with fiddling around with that..
I'm happy that reverting fixed the issues and everything else is still working.. 

  • 0
PalmPilot Newbie

PalmPilot

Posted
Posted

I had the same issue. Contacted support and was told that they (Covecube) need to update the DrivePool virtual driver and have it re-sign by Microsoft before it can be used with the latest Insider Build. I have no idea how long it would take them. Hopefully soon.

  • 0
geebee Newbie

geebee

Posted
Posted
On 6/21/2020 at 4:58 PM, XtremeMaC said:

as it's clearly an MS problem,

It's not an MS problem, it's a user problem. Fast ring, or the new dev, beta and release preview channels are there for developers to iron out compatibility and bugs before it hits mainstream. You are on a developer release channel, on the same channel that Covecube is probably tracking, expecting zero-day stability, that's not going to happen.

 

Quote

Yesterday's update broke Drive Pool that's super crucial for me

Then move Drivepool out of the developer channel windows installation.

  • 0
XtremeMaC Newbie

XtremeMaC

Posted
  • Author
Posted

Thanks for the 0 value added comment.

As with any beta release, you go on forums, go to feedback hubs and report the unexpected bug. That's how companies know there is an issue and eventually fix it. So, here we are reporting it. Whole point of MS feedback hub and point rating system is to gather how many people have the problem. 

At the same time Covecube, by our reporting, if they were really motivated, could also try to find workaround or permanent/robust method to circumvent any future issues that could arise from similar bug. 

Ps. I already know the suspected problem as MS's build updates revealed in their known issues section. But the definition is for MS storage spaces, didn't know it could affect Drivepool.

In addition, I couldn't have found this issue on a dedicated machine as I, along with many users, probably wouldn't install DrivePool... The whole point of rollback is this....

  • 0
Umfriend Advanced Member

Umfriend

Posted
Posted

I didn't want to react at first but snapdragon is right. No one in their right mind combines crucial functionality and beta testing. It is crucial to separate the two.

The demand that they work to circumvent "any future issues" is simply ridiculous.

  • 0
XtremeMaC Newbie

XtremeMaC

Posted
  • Author
Posted

ok, so most often for any beta software, if it fails, is most likely to corrupt things on your primary drive unless special circumstances, at the very worst case, could corrupt drive permissions on other drives. Also, do you think that all "released" software is bug-free???

So what people do is, put valuable data into separate drives to mitigate risks. 

With this "bug", what happened is I did not lose any crucial data (I worded that incorrectly, it's just data that I'd rather not lose, not crucial in anyway. Crucial stuff is on cloud and external hdds.)
The files are already in the disks, what happened was just loss of the pool.. 

A risk I am willing to take. I came here to report it and look for any possible ways to fix. End of story. 

  • 0
LewJones77 Newbie

LewJones77

Posted
Posted

Seems to be a known issue with Win10 insider builds of 2004.... Since MSFT moved to the Iron Branch, away from the Manganese Branch.

Looks like we are stuck until MSFT fixes whatever is breaking software raid! I am trialling DrivePool, because i had the same issue with Drive Bender, which stopped working when i updated my plex server... I had to roll back to an earlier release which worked fine (19635 - still the Manganese branch... now MSFT has moved to the Iron branch, things are broken again)

Another post on even Storage Spaces broken : https://mspoweruser.com/the-windows-10-may-2020-update-may-be-causing-major-hard-drive-management-issues/

  • 0
Christopher (Drashna) Advanced Member

Christopher (Drashna)

Posted
Posted
1 hour ago, Jimpc said:

Just tested the latest Drivepool beta. It does not fix the issue. 

Have you rebooted the system twice?  If not, try doing that. 

If that doesn't help, then could you open a ticket at https://stablebit.com/Contact

After doing so, run the StableBit Troubleshooter on the system:
https://wiki.covecube.com/StableBit_Troubleshooter

Then try resetting the settings:
https://wiki.covecube.com/StableBit_DrivePool_Q2299585B

If that doesn't work, completely remove the software using this guide:
https://wiki.covecube.com/StableBit_DrivePool_Q3017479

This should remove the driver, as well.  Then reboot the system, and reinstall with the newest version, again. 

  • 0
Jimpc Newbie

Jimpc

Posted
Posted
On 7/5/2020 at 4:07 PM, Christopher (Drashna) said:

Have you rebooted the system twice?  If not, try doing that. 

If that doesn't help, then could you open a ticket at https://stablebit.com/Contact

After doing so, run the StableBit Troubleshooter on the system:
https://wiki.covecube.com/StableBit_Troubleshooter

Then try resetting the settings:
https://wiki.covecube.com/StableBit_DrivePool_Q2299585B

If that doesn't work, completely remove the software using this guide:
https://wiki.covecube.com/StableBit_DrivePool_Q3017479

This should remove the driver, as well.  Then reboot the system, and reinstall with the newest version, again. 

Uninstall and reinstall did it. Thanks. 

  • 0
Christopher (Drashna) Advanced Member

Christopher (Drashna)

Posted
Posted

Actually, we don't really track the Insider stuff, since things are known to break and be fixed before general release.  

However, if we have a bunch of reports of issues, we'll take a look, as in this case.   And because it was a change rather than a bug, we decided to fix it (as the cause of this is very likely to make it to GA).  

 

But ... in no uncertain terms, if stability is critical, you should NOT be using an Insider build. Period.  Expect things to break on the Insider channel, because they will. 

 

Either way, we do have a fix for this issue.  And if you run into issues, the "reinstall" guide I link above should fix any issues.

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...
×
 Share
Go to question listing
×
×
  • Create New...