Jump to content
Covecube Inc.
  • 0
suodrazah

Yet another 'performing recovery' thread. Requesting info on on time frame and key points of the process.

Question

Unfortunately Windows decided that it would force restart my system when installing latest updates. And now I am experiencing the dreaded "This drive is performing recovery" process.

I've since modified my own reboot script to include safe shutdown of the StableBit CloudDrive Service to ensure safe shutdown/restart, and will execute this when installing updates manually.

From the threads I have found and read I'm relatively confident I'll get most of my data back, my question is about time frame and at what point in the process I will regain access to my data.

The drive in question is 256TB and configured on GSuite, at the time of reboot I had 5TB uploaded, 9TB queued for upload and had recently cleared the cache (hours prior).

During recovery, I assume that CloudDrive is re-indexing the local data. I can see it reading the dedicated cache drive consistently, between 80 and 200MB/s. Assuming that it has to read all of the local data this process will take up to 24 hours to complete. After this, I again assume, uploading will resume. Uploading is restricted to 50Mb/s, so this could take up to 3 weeks to complete.

Will I regain access to my data at the 24 hour or 3 week point? If 3 weeks, my upload speed is getting bumped up to a gb for the month!

Any input greatly appreciated.

Recovery.png

Share this post


Link to post
Share on other sites

4 answers to this question

Recommended Posts

  • 0
1 hour ago, suodrazah said:

I've since modified my own reboot script to include safe shutdown of the StableBit CloudDrive Service to ensure safe shutdown/restart, and will execute this when installing updates manually.

That may actually cause more problems than it solves.  The "StableBit CloudDrive Native Service" is there to prevent Windows from shutting down before the StableBit CloudDrive Service has had a chance to safely exit.  

As for how long this may take, that's hard to answer, but depends heavily on the size of the drive and the size of the cache. 
https://stablebit.com/Support/CloudDrive/Manual?Section=Recovering from Errors#Power Loss / System Crashes

 

Share this post


Link to post
Share on other sites
  • 0
Posted (edited)

Thanks for the reply, if I wanted to absolutely guarantee safe shutdown what should I do? Couldn't care less if it takes hours to shutdown, just needs to be safe.

The drive just came back online. It's mounted and I'm just waiting to see if I have access to the files in question without having wait for the uploads to complete. Progress makes me smile.

Edited by suodrazah
Got a bit ahead of myself

Share this post


Link to post
Share on other sites
  • 0

I've regained file access.

EDIT: I initially thought that this was due to a drive failure, but realised that I had moved the cache off of the stuffed drive anyway. Minimal loss, makes me happy.

Share this post


Link to post
Share on other sites
  • 0
On 5/4/2020 at 6:47 PM, suodrazah said:

Thanks for the reply, if I wanted to absolutely guarantee safe shutdown what should I do? Couldn't care less if it takes hours to shutdown, just needs to be safe.

Honestly?   There isn't really anything that you should need to do.  The "native" service should prevent the system from shutting down before the service has a chance to cleanly shut down.  That was it's only intended purpose. 

However, power loss, BSOD, and the like can happen. And in this case, these events can happen.  A battery backup will help prevent issues with power loss, but that depends on the VA rating of the battery backup (UPS), and how long it takes for CloudDrive to gracefully shutdown. 

As for BSOD's... that's a lot harder to prevent.  Running a semi-regular memory test, checking the system disk, and being careful what you install/download, and hoping no weird issues pop up, those are about the only options. 

 

On 5/4/2020 at 6:55 PM, suodrazah said:

EDIT: I initially thought that this was due to a drive failure, but realised that I had moved the cache off of the stuffed drive anyway. Minimal loss, makes me happy.

I'm glad to hear that you have access back.  

If you haven't, it may be a good idea to run a simple CHKDSK pass on the drive, to make sure there is no file system corruption, and to fix any if there is. 

 

Share this post


Link to post
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...