Jump to content
Covecube Inc.

Chase

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    2
  1. I went with a dedicated bare bones server and loaded windows 10 pro on it. It has 16gb ram, a 1TB HDD, and a 12 core AMD processor with plenty of transcode power. I've also got a 10gbps connection. $109/mo.
  2. This is what I did...after fooling with all the "seedboxes" and not knowing out how properly mess with linux codes. So it's a dedicated windows server for me.
  3. All of my drives are working and I have no errors...EXCEPT the last beta that changed the GoogleDrive_ConcurrentRequestCount to "2" appears to be causing issues. My drives tend to do a lot of reading and writing...it's for a plex server. And 2 concurrent causes CloudDrive to tell me I don't have enough bandwidth. I have tried to change the setting in the "settings.json" but it isn't accepting the change.
  4. Upgraded to the latest beta this morning. That drive I was having issues with and had deleted the cache was showing about 15% completed at the time of upgrade. The percent started over but it only took about 35 minutes to complete and mount my drive. (56TB with 20TB of data). Everything works on all drives except that annoying error when I try to change the I/O settings I talked about previously. Again...the changes take it just pops up with an error that the drive isn't mounted. I've got family in for the next several days. Be safe guys. I'm very happy with the latest beta fix. All of my drives are functional.
  5. To answer your question..I deleted the main Cache file which for me is stored on my C:/ Drive. It starts with Clouddrive and is followed by your drive UID. as SRCRIST said....it is very risky and my drive may be totally corrupt when it finishes. That was a risk I was okay with taking. You make your own decision. I did get a message back from Christopher on the Covecube team. They looked at my path of issues and whats happened plus troubleshooter data and his message was this... "We have found a bug in the migration code, that may be the problem here.We should have a fix out soon, that should be much faster (or even instantaneous) and handle failure better. "
  6. I may have fixed my drive that is stuck in "queued for recovery". But damn did it make me nervous and I'm far from out of the woods. In my understanding of the system the "cache" is just a local file of your pinned data and a COPY of the last #GB of data that was received or transferred between your machine and the cloud drives. It also seems that it holds the information for the CloudDrive program to say...yep this is a drive that we have mounted. So I shut down the windows service for CloudDrive and deleted the cache file for my problem drive. After restarting my computer when CloudDrive opened up it only showed the two working drives as mounted and the problem drive was available to mount. Sweet! Mount that sucker. Seems to be working. It now says that the drive is upgrading and I get a percentage actually shown. Albeit it is way slower compared to last time I went through this stage. Probably because this latest Beta has less I/O interactions. It did NOT give me the option to reauth so I assume this drive is still using the StableBit API. At this rate it should complete by Monday-ish?
  7. Uh. Yes. When this process first started I was on the default API. At that time I had two drives going through the update. In the middle of that process I added my own API but since you aren't able to reauthorize during the update it didn't actually switch to my API. When my first drive finished I was able to reauth. My second drive that is still having issues has never been able to reauth so my understanding is that it is still on the default API. The third drive that I mounted and said it was updating without showing a % was after I added my own API and therefore authorized on my API.
  8. Unintentional Guinea Pig Diaries. Day 8 - Entry 1 I spent the rest of yesterday licking my wounds and contemplating a future without my data. I could probably write a horror movie script on those thoughts but it would be too dark for the people in this world. I must learn from my transgressions. In an act of self punishment and an effort to see the world from a different angle I slept in the dogs bed last night. He never sleeps there anyways but he would never have done the things I did. For that I have decided he holds more wisdom than his human. This must have pleased the Data God's because this morning I awoke with back pain and two of my drives mounted and functioning. The original drive which had completed the upgrade, had been working, and then went into "drive initializing"...is now working again. The drive that I had tried to mount and said it was upgrading with no % given has mounted (FYI 15TB Drive with 500GB on it). However my largest drive is still sitting at "Drive queued to perform recovery". Maybe one more night in the dogs bed will complete the offering required to the Data God's End Diary entry. (P.S. Just in case you wondered...that spoiled dog has "The Big One" Lovesac as a dog bed.. In a pretty ironic fashion their website is down. #Offering)
  9. Unintentional Guinea Pig Diaries. Day 7 - Entry 1 OUR SUPREME LEADER HAS SPOKEN! I received a response to my support ticket though it did not provide the wisdom I seek. You may call it an "Aladeen" response. My second drive is still stuck in "Drive Queued to perform recovery". I'm told this is a local process and does not involve the cloud yet I don't know how to push it to do anything. The "Error saving data. Cloud drive not found" at this time appears to be a UI glitch and it not correct as any changes that I make do take regardless of the error window. This morning I discovered that playing with fire hurts. Our supreme leader has provided a new Beta (1.2.0.1306). Since I have the issues listed above I decided to go ahead and upgrade. The Supreme leaders change log says that it lowers the concurrent I/O requests in an effort to stop google from closing the connections. Upon restart of my computer the drive that was previously actually working now is stuck in "Drive Initializing - Stablebit CloudDrive is getting ready to mount your drive". My second drive is at the same "Queued" status as before. Also to note is that I had a third drive created from a different machine that I tried to mount yesterday and it refused to mount. Now it says "drive is upgrading" but there is no progress percentage shown. Seems that is progress but the drive that was working is now not working. Seeking burn treatment. I hope help comes soon. While my data is replaceable it will take a LONG TIME to do. Until then my Plex server is unusable and I have many angry entitled friends and family. End Diary entry.
  10. The software works great if you use the latest stable or beta 1.2.0.1301. I would suggest that you set it up and keep your drives relatively small for right now (<6tb data). Eventually you will have to upgrade and have the new file structure that the current beta is doing. These kinks will be worked out. I imagine that Stablebit is limited on engineers and they were blindsided with googles new rules. That is a lot of pressure on them to adapt while keeping a lot of data safe.
  11. Unintentional Guinea Pig Diaries. Day 5 - Entry 2 *The Sound of Crickets* So I'm in the same spot as I last posted. My second drive is still at "Queued to perform Recovery". If I knew how to force a reauth right now I would so I could get it on my API. Or at the very least get it out of "queued" Perhaps our leaders will come back to see us soon. Maybe this is a test of our ability to suffer more during COVID. We will soon find out. End Diary entry.
  12. I submitted a ticket. Let me preface all of this with I am tech savvy but by no means a programmer. Prefetch is working intermittently right now. The big problem is that it keeps telling me i'm throttled (double yellow arrows on download and upload sides) but it is not acting as if it is throttled consistently. For example, I have my prefetch set to grab 1Gb and it did so just now at 250 mbit/s without issue. I still have the error "Error saving data. Cloud drive not found" when trying to change performance I/O setting or when I press the pause button on upload. However it does take the new settings anyways and clearly the drive is found, mounted, and active. I added my own API and reauthorized on it for my one drive that has completed the update. Still have the issues listed above but I know that it has switched to my API. My second drive that was still in the middle of updating is now saying "Drive queued to perform recovery". It looks like my server shutdown unexpectedly at some point this morning so the recovery part is expected but I've never seen it say "queued" for recovery. I'm pissed that my server crashed. Its all brand new dedicated hardware and hosted in a data center...ugh Any ideas on how to push it out of "queued" to recover and actually start recovery? Thanks in advance.
  13. AFAIK you cannot have multiple people access the data from different devices if you are using cloud drive due to the reasons you state above. You can also only mount the drive to one computer. You may want to look into the "Google Drive Desktop App".
  14. on the drive that has completed the upgrade. I can see and access my data but when I try to change my I/O performance on that drive it tells me "Error saving data. Cloud drive not found" EDIT: Prefetch is not working
  15. I'll tell you my path on this...yours may differ I upgraded to the dreaded beta on Wednesday at about 5pm. I have two drives both 56TB in capacity. Drive "A" has 10TB of data and Drive "B" has 20TB in data. On Thursday I restarted my computer at around the 24 hour mark and the progress percentage started over. I can pretty confidently say that the whole process started over. About two hours later one of my drives stopped even showing the percentage complete and just had an error. This is when I went into the Json and added my own API key information...again restarting my computer and restarting the process. I don't know if adding my API to that file actually did anything because the logs still show i was being limited but the percentage started and was going up again so that was a sign of progress. Drive A with the 10TB of actual data took approximately 48 hours to complete from the last time I restarted my computer. Now that it is complete it appears that my data was unharmed and I can access it. On drive B with the 20TB of data is (as i write this is at the 60 hr mark) only at 55.33% . I'm refusing to be the first of us to restart my computer after it is "complete"....hell no
×
×
  • Create New...