Drive cannot be mounted on new Machine (googledrive)

[cryx]

Hey Guys,

 

I have this problem 2 days now, my specs from the CloudDrive 100TB, 2mio chunks (10mb) on Google Drive. Now i will claim this drive on a new machine and i have all time a Provider Internal Error like this (and the error come from random chunks maybe 22000 stopped or 133000 stopped idk why and its all time a another cloud part):

 

18:42:27.5: Information: 0 : [ChunkIdSQLiteStorage:24]   chunks IDs: 1336435,1336436,1336441,1336442,1336443,1336444,1336445,1336446,1336447,1336448,1336449,1336450,1336451,1336452,1336453,1336454,1336455,1336456,1336457,1336458,1336459,1336460,1336461,1336462,1336463,1336464,1336465,1336466,1336467,1336468,1336469,1336470,1336471,1336472,1336473,1336474,1336475,1336476,1336477,1336478,1336479,1336480,1336481,1336482,1336483,1336484,1336485,1336486,1336487,1336488,1336489,1336490,1336491,1336492,1336493,1336494,1336495,1336496,1336497,1336498,1336499,1336500,1336501,1336502,1336503,1336504,1336505,1336506,1336507,1336508,1336509,1336510,1336511,1336512,1336513,1336514,1336515,1336516,1336517,1336518,1336519,1336520,1336521,1336522,1336523,1336524,1336525,1336526,1336527,1336528,1336529,1336530,1336531,1336532,1336533,1336534,1336535,1336536,1336538,1336539

18:42:57.2: Warning: 0 : [ApiGoogleDrive:24] Google Drive returned error (internalError): Internal Error

18:42:57.2: Warning: 0 : [ApiHttp:24] HTTP protocol exception (Code=InternalServerError).

18:42:57.2: Warning: 0 : [CloudDrives] Cannot start I/O manager for cloud part 13648a9f-4c1e-43d9-a7c2-c61442158252. Internal Error

 

u need more informations please ask for it idk what u need :/ and sorry for my bad english thanks

 

EDIT: can i change the read time to 5 seconds for the chunks? or the max read chunks to 50? maybe its the Rate limit from the google drive provider?

[cryx]

please close it is working now on the 4 run...

[Christopher (Drashna)]

First, your english is fine!  

 

 

That said, the "ChunkIdSQLiteStorage" stuff is normal if you haven't mounted the drive in a while. We implemented this to fix a number of issues and reduce API usage. 

 

As for the "internal error", this is a server side issue.  Specifically, the "InternalServerError" is most likely a "HTTP 500" error.  There isn't anything we can really do other than "retry".  But if this fails too much in a short period of time, there isn't much we can do, other than "gracefully fail". 

 

 

 

On the plus side, the software shouldn't need to reindex the software, so this should be a one time "event".