Jump to content

triadcool

Members
  • Posts

    88
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by triadcool

  1. I have data in Stablebit cloud drives that I would like to add to my local storage Drivepool.  I don't wan't the cloud drive data modified/balanced other than initially seeding the PoolPart folder of each cloud drive.  What would be the best way of accomplishing this?  Would creating a separate Pool for the Cloud Drive and Local Drives then using Hierarchical Pooling work best?

    1. Local storage drivepool is constantly added to but no file duplication is needed.

    2. Cloud storage shouldn't be balanced or added to as its sole purpose will be to read data that already exists on it.

    3. Folder names will mostly be the same on both the local and cloud drives when creating the drivepool.

    Any help with figuring out how to set this up would be appreciated.  Thanks.

  2. Christopher,

     

    I am still having issues with CloudDrive re-indexing each of my 6 CloudDrives every time I restart my server and this process still takes over a day to complete for all of the drives.  Nothing is happening to the Chunk Database as I can browse to Google Drive and view the file for each drive in the data-ChunkIdStorage folder.  Does the file have to exist somewhere on the computer running CloudDrive for it to not trigger another scan at startup?

     

    I am currently running on version .929 but the same thing has happened on every version I have tried since the chunk database was implemented. 

  3. I use SyncBackPro to schedule files to be copied to my cloud drive nightly.  One thing I can't get to work correctly is if I want to setup a schedule to move files from one folder on my clouddrive to another folder in the same clouddrive, SyncBackPro wants to re-upload the files instead of just move them "in-place" like moving in windows explorer works.  What's the function called when you move files from one location to another on the same cloud drive and not trigger a re-upload?  I've searched for the answer to this problem but i'm not getting anywhere since i'm not sure what terminology to use.

  4. It does give you another prompt making sure that you want to proceed with destroying the drive once clicked.  I do agree that this button should be in a different location altogether as to prevent any accidental destroys.

  5. I lost about 48TB of data because of this issue. :/   The issue started happening to me when I was on a older version for over a month.  I didn't upgrade or change anything and started having this chunkid="" issue.  Stablebit is not finding chunks that do actually exist in Google Drive.

     

    Open the technical details windows, and click on the "service logs" button. 
     
    This will open up a new window that will show the service log output.  Click on the "Tracing levels" button, the "C" group and open the "Chunk ID helper" section.  Select "Verbose" and then reproduce the issue. 
     
    Once you do the above you will most likely see something like this:
     
    22:15:26.3: Information: 0 : [ChunkIdHelper:84] Chunk 366031 read (State=Found, ChunkId='')
    22:15:26.5: Information: 0 : [ChunkIdHelper:89] Chunk ID for chunk 366031 is '' (via cache)
    22:15:26.5: Information: 0 : [ChunkIdHelper:89] Chunk 366031 read (State=Found, ChunkId='')
     
    If you see the above with ChunkId=""  then you are affected by the same issue as me and a few others.  Again, the chunk exists on Google Drive (I have verified this many times) but stablebit doesn't find it which causes corruption.
  6. When you go into the technical details does it show a bunch of prefetch threads but with all of them downloading 0%?  This may be the same corruption problem that at least myself and another are having.

  7. This is the exact issue that I have with 3 of my drives totaling around 48TB of data.  I have two Google Drive accounts and this affected all of the drives on one of the Google Drive accounts.  The 3 drives on my other Google account are fine at the moment.

     

     

    This issue affected all 3 of the drives at the same time while on version .723.  I upgraded to the latest version 1.0.0.802 with no change in behavior.

     

     

    D5D97JK.png

    jPYVmdA.png

    it5nko2.png

  8. Just a heads up, when moving around the folders, you may need to "refresh" the drive list in StableBit CloudDrive. This queries the provider, and looks for the specific data.

     

    Also, you may need to create at least one drive so that you have the "StableBit CloudDrive" folder present already.

    I tried doing both of these without the drive showing up unfortunately.

  9. Interesting. Did you copy it exactly as a new folder (StableBit CloudDrive) or did you try to integrate it with already established disks?

    I copied it to a new folder in the root of the 2nd Google Drive account then moved the folder into the Stablebit Clouddrive folder retaining the original folder name.  Of course, so far there is no reason to do this since stablebit can't read the cloned folder from a different Google Account.

  10. It transfers the chunks pretty fast but I had to run the command about 10 times to get all of the files copied because of Google API limits.  It took about 20 minutes to copy 15,000 files from a 350GB drive.  All of this doesn't really matter right now since the copied drive won't mount in stablebit.

  11. Are any of you having problems with your Stablebit drives on Google Drive?  I have two Google Drive accounts that I use Stablebit on and all of my drives from one of my accounts aren't working correctly.  They are mounted but only random files will stream and some will play but quit after a minute or two as if they are corrupt.  When I try to download any of the files, the stablebit threads shoot to 40+ and the 5+ GB downloads finish in 5 seconds and the downloaded file is corrupt.  All of the drives on my other Google Drive account are working like normal.  This just started happening about an hour ago.

     

    EDIT: I just checked the service log and I am getting a bunch of these errors:

     

    20:49:57.4: Warning: 0 : [OAuth2TokenBase:29275794] HttpProtocolException refreshing token. HTTP Status BadRequest

    1. From the Primary account, share whatever files/folders you want with the Secondary account.

    Go to the Secondary account, and click "Shared with me".

    Right click on the files/folders from the Primary drive, and click "Add to my drive". ** Note ** This is not the end! Your files are currently still owned by the Primary drive and will be removed if the Primary drive no longer shares them with the Secondary drive!!

    Because rclone with Google Drive supports server side copying from the same remote (meaning you don't have to download/reupload the files), you can do something like "rclone copy secondaryGDrive:/primaryDriveFilesFolderPath/ secondaryGDrive:/newPathOnSecondaryDrive"

    Doing this will allow your Secondary drive to be the owner of the newly copied Primary drive's files and folders. The files will remain on your Secondary drive even if the Primary drive stops sharing with you.

     

  12. Christopher,

     

    I have copied the folder of one of my stablebit cloud drives from one Google Drive account to another using rclone.  I moved this copied "CloudPart" folder into the existing "Stablebit CloudDrive" folder on this 2nd Google Drive account. (I use stablebit on 2 separate Google Drive accounts)  I tried to get stablebit to see the folder and allow me to mount it but the software wouldn't recognize that there was a new drive.  

     

    I was hoping to be able to clone the folders between accounts to have a backup but it looks like Stablebit will only read the drives from the Google Drive account that they were originally created under.  I tried reauthorizing and restarting the server.

     

    EDIT:  I was trying to get this to work as there is a way using rclone to copy contents of a Google Drive to another all server-side with no local bandwidth usage.

×
×
  • Create New...