Jump to content

steffenmand

Members
  • Posts

    418
  • Joined

  • Last visited

  • Days Won

    20

Posts posted by steffenmand

  1. Okay, thank you for the information. 

     

    Another question, are you using any non-standard settings, like the "Minimum download size", etc. 

     

    Also, please do this:

    http://wiki.covecube.com/StableBit_CloudDrive_Drive_Tracing

     

    That may catch the issue as it happens, and may help us to identify what exactly is happening here. 

     

     

     

    Also, could you run this: 

     

    http://dl.covecube.com/Troubleshooter/StableBit.Troubleshooter.exe

     

    Make sure that the "include system information" option is checked, when you submit it. 

     

    My guess is that Windows is trying to make thumbnails for video and image files, thus gets stuck in a state where it has to retrieve x data first.

     

    I look forward to the option of having extended data pinned, such as file headers etc. Maybe they might come in soon, as we are getting a release out soon :)

  2. I suspect that we manage this globally and per drive. 

     

    I'll have to ask, as I'm not 100% certain and this is one of the more advanced areas of the software. 

     

    Seems only to run on a global setting - would be nice to have it per account instead!

     

    Btw hope all is well after the surgery! Get well! 

  3.  

    Hello

     

    I had an 2TB encrypted drive on my server with alot of files, mounted to Amazon Cloud Drive with the StabeBit software. My server crashed and I can not access the mounted drive anymore because the server is gone for good. I saved the encryption key. How can I mount the drive to another PC so I can see my files again?
     
    Thank you for the help

     

     

    Just connect the account on the new server and you should be able to force an attach

  4. Hi,

     

    I've noticed that the thread count seems to have been defined globally to be shared between all your drives.

     

    As i have several google accounts hooked up, with individual drives, shouldn't it be more logical to have the thread count be defined pr. unique google account ? - They should all have their individual API call caps, which was the main reason for the limit.

     

    Would be nice to access files from another account, while also download from the first - right now it would just slow down the progress from both.

     

  5. go to technical overview and look at the service log.

     

    you will get a warning about multiple chunks with the same id and the number it has: search for this on the drive and you should find two chunks. Download the newest (for backup) and then delete it afterwards. do this for all the chunks which have duplicates.

     

    after you finish go to troubleshooting - > reset settings and include the databases.

     

    reboot and start :-) should mount fine now! if not then reupæoad all the chunks you dowbloaded and make a ticket with stablebit

  6. As long as you backup chunks it should be possible to revert back by uploading then again and reindexing :-)

     

    I chose to go for the older ones, as i knew ihad not done any changes since the updates where they were made. so i trusted the old data more than the new, as the new potentially could have faulty data - this was also why my drive went RAW as i had multiple chunks on the chunk which contained the MFT data - the new one was corrupt, the old just fine

  7. Fixed it for all drives which had not gone RAW.

     

    The one the went RAW seemed to have multiple chunks on the main chunks. So i just tried deleting the new versions (took a backup) and started reindexing all over to see if that would fix the issues and let it mount properly. I guess one of those chunks hold the MFT data and if it uploaded a new empty file, it would ofc. not be able to mount, because the fix loads the newest version == empty file.

     

    Will report back if that fixes the issue with the RAW drive :)

     

    Deleting all the newest chunks when we had multiple chunks with the same key worked. drive now mounts properly! Before trying this make sure to backup the chunks so you can fix it again!

     

    if you already indexed just restart the indexing procedure by resetting the settings and the database under troubleshooting -> reset settings as your index currently will be pointing to the wrong chunk where we had multiple

  8. Fixed it for all drives which had not gone RAW.

     

    The one the went RAW seemed to have multiple chunks on the main chunks. So i just tried deleting the new versions (took a backup) and started reindexing all over to see if that would fix the issues and let it mount properly. I guess one of those chunks hold the MFT data and if it uploaded a new empty file, it would ofc. not be able to mount, because the fix loads the newest version == empty file.

     

    Will report back if that fixes the issue with the RAW drive :)

  9. Do you get chkdsk errors? I am just gonna wait for a bit and see what happens. I am in the midst of running chkdsk. After it runs i will check to see everything works hopefully. But seems to be the newer versions have something messed up. .802 had an upload issue and the newer ones seem to have corrupted everything else that was on the drive

    I got no chkdsk errors after testing - the error is simply that the chunks dont have a reference to the right chunk on the provider.

  10. I think our data is lost due to the way MFT works if it is MFT it should be fairly hard to restore. 

     

    Well as far as i can see, then the system knows what chunks to use. They are simply just not linked to the proper id on the provider. Thats why we were seeing tons of chunks completing successfully with 0%.

    I think the big problem with data would arise if the problem was that it lost reference to what chunk numbers refers to which file

  11. Haven't created new drives since the double folder issue, but got 4 other drives which still works.

     

    Chunks exists on the provider and I am able to download them through the Web interface!

     

    First drive I got this issue on was on the 8th and the second was the 19th so days before and after the outage!

     

    It just seems like it skips the download and fills in empty data

×
×
  • Create New...