Jump to content

Edrock200

Members
  • Posts

    36
  • Joined

  • Last visited

  • Days Won

    1

Community Answers

  1. Edrock200's post in V904 - Pinning data cycles every 30m was marked as the answer   
    Disregard, ran a chkdsk, it repaired some issues, and it stopped cycling. Sorry for raising the flag early.
  2. Edrock200's post in Google Drive Account Disabled was marked as the answer   
    Mystery solved. I had installed netdrive and mounted my Google drive, but didn't use it to copy anything to/from drive. My a/v scanner is configured to scan local and net drives, and it began attempting to scan repeatedly. Apparently Google didn't like this. I contacted them after they unlocked the account and figured it out. All is well. Sorry for the false flag.
     
    I like the idea of sharing the drive though to prevent getting locked out. I own my domain and gsuite account. I bought it and have 6 accounts paid for monthly (6 family members, we each pay $10/mo). I have about 20tb of system backups, system images, photos, multimedia and my iTunes library. On a side note, the latest version of cloudrive allows me to use prefetch now w/o causing disconnects or throttling.
  3. Edrock200's post in Google Drive + PreFetch = Throttle? was marked as the answer   
    In case anyone else comes across this thread who is also using Plex, don't let Plex scan your drive until your initial upload is done. I have mine set not to generate thumbnails or due deep media analysis, but it still makes a lot of calls to the drive on initial scan which will potentially cause throttling. Lessons learned on my end:
     
    Create drive
    Turn prefetch off
    Turn off excessive indexers and Google sync clients if your drive is using Google storage*
    Preload drive with content
    Turn on media scanners and let initial scan complete
    Turn on prefetch
     
    If you try to do it all in parallel you will most likely get throttled and it will probably take longer than doing it in the order above. Since Google drive client doesn't offer any detailed stats, I didn't realize it had essentially slowed to zero.
     
    *If you are using Google drive client to preload your clouddrive, throttle drive client up/down to 99/99mbs (max it will allow) and cloud drive to 250/250 up down with 5/5 io threads up/down and no prefetch.
     
    Should you find that you need to move your drive to another pc and still want drive client linked to cloudrive for syncing, do this:
     
    Old PC:
    Close Google drive client
    Backup folder %localappdata%\google\drive
    Detach cloud drive
     
    New pc:
    Install Google drive client and authenticate to account. Accept defaults but immediately close client after logon
    Mount clouddrive to SAME drive letter as old PC
    Restore %localappdata%\google\drive from backup to new pc
    Relaunch Google drive client
     
    This will restore the drive client file hashes and prevent your new pc from needing to download and hash every single file again. Alternatively you can open regedit and go to hkcu/software/Google/drive and point the appdata directory to your cloud drive and restore to that directory, so the hash stays with the drive. Since it's frequently used it should stay in cache when mounted.
    Ed
    *you can turn prefetch back on after initial load of files onto cloud drive
    *I did not mean to mark my own reply as best answer. I was just trying to mark the entire thread as solved.
×
×
  • Create New...