Jump to content

  • Log in with Twitter Log in with Windows Live Log In with Google      Sign In   
  • Create Account

Photo

*WARNING* Detaching drive in .783 DETROYS your CD


  • Please log in to reply
3 replies to this topic

#1 raidz

raidz

    Member

  • Members
  • PipPip
  • 12 posts

Posted 28 December 2016 - 06:16 AM

So I thought when I detached a drive last week I accidentally hit destroy instead of detach and wrote it off as my own stupidity.

 

I just detached another drive today and CD destroyed it. I lost 40 TBs of data. DO NOT detach your cloud drive until they figure this out.

 

I am extremely pissed to say the least. I have lost two drives now in the past 7 days, some with data I did not have backed up in another place.

 

This is extremely unacceptable and I warn all of you of putting anything worth your time on these drives until they make this software more reliable.

 

I guess the software is listed as beta, so my own fault for thinking it wouldn't ruin a drive in one fell swoop.

 

Data actually isn't gone but the files they wrote to have no previous versions so it looks like I cannot recover. 


  • Ginoliggime, KiaraEvirm and Antoineki like this

#2 Christopher (Drashna)

Christopher (Drashna)

    Customer and Technical Support

  • Administrators
  • 8,203 posts
  • LocationSan Diego, CA, USA

Posted 31 December 2016 - 12:27 AM

To be blunt, this shouldn't happen.
 
The only reason that the drive would show up as "Destroyed" in the UI, is if the metadata file for it was deleted, but the rest of the contents remained. 
 

In the UI, drives show up as destroyed if their cloudpart folder exists, but the metadata file doesn't (or can't be retrieved for any reason).
when you destroy a drive, the first thing that gets wiped out is the metadata (to "mark" the drive destroyed beyond this point), then the actual chunks of data get deleted


If this is happening consistently then please do let us know.

 

And in this case, please enable logging, and fiddlercap, and reproduce this issue.

 

 

http://wiki.covecube...e_Drive_Tracing

http://wiki.covecube...dDrive_Web_Logs

 

And once you've done that, run this:

http://dl.covecube.c...ubleshooter.exe

 

 

I've also spent the last hour trying to reproduce this (on 1.0.0.784 though) without any success. Detaching and re-attaching the drive repeatedly.

 

So if something is going on here, it may be localized to your hardware, connection or account. 

 

And could you check "\StableBit CloudDrive\CloudPart-xxxxx\xxxxx-METADATA" for contents, and post it here or in a ticket, if it exists? 


Christopher Courtney

aka "Drashna"

Microsoft MVP for Windows Home Server 2009-2012

Lead Moderator for We Got Served

Moderator for Home Server Show

 

This is my server

 

Lots of "Other" data on your pool? Read about what it is here.


#3 Christopher (Drashna)

Christopher (Drashna)

    Customer and Technical Support

  • Administrators
  • 8,203 posts
  • LocationSan Diego, CA, USA

Posted 31 December 2016 - 07:34 PM

By chance, do you have two "StableBit CloudDrive" folders on your provider (especially if this is Google Drive)?


Christopher Courtney

aka "Drashna"

Microsoft MVP for Windows Home Server 2009-2012

Lead Moderator for We Got Served

Moderator for Home Server Show

 

This is my server

 

Lots of "Other" data on your pool? Read about what it is here.


#4 steffenmand

steffenmand

    Advanced Member

  • Members
  • PipPipPip
  • 296 posts

Posted 08 January 2017 - 08:33 PM

This happened to me and it turned out it was due to me having used .769 or .770 which caused two "Stablebit CloudDrive" folders to exist. It would load the wrong folder and show as deleted.

 

Make a ticket and they will help fix it! - A lot of files ended up corrupted though, but unsure if this was the cause






0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users