Jump to content
Covecube Inc.
  • 0

Drive mount Error


Question

9 answers to this question

Recommended Posts

  • 0

open a ticket at https://stablebit.com/Contact

 

And if you could, do this: 

http://wiki.covecube.com/StableBit_CloudDrive_Web_Logs

 

 

 

That said, the "Internal Server Error" is an HTTP 500 error.  This means that there is a server side issue here.  As in, Google Drive is coming back with errors.   In this case, there isn't much that the software can do, other than wait and retry.

Link to post
Share on other sites
  • 0

open a ticket at https://stablebit.com/Contact

 

And if you could, do this: 

http://wiki.covecube.com/StableBit_CloudDrive_Web_Logs

 

 

 

That said, the "Internal Server Error" is an HTTP 500 error.  This means that there is a server side issue here.  As in, Google Drive is coming back with errors.   In this case, there isn't much that the software can do, other than wait and retry.

 

To be clear, Christopher--and I mentioned this in the other thread--the problem here is that, during the reindexing process, it simply *doesn't* retry. Retry would mean that it puts in a request for chunk 2,345,234, gets a server error, waits, and puts in that request again. Instead, it puts in a request for chunk 2,345,234, gets a server error, and restarts at chunk 4,234,122--slowly working its way back down. It needs to retry, rather than abort and start over.

 

In some cases, it doesn't even start over. It just fails, the UI gives a mounting error, and it sits there until you press the "retry" button. This behavior, of course, adds even MORE time to the process. 

 

The good news, for the other folks in this thread, is that the data on my drive was, ultimately, completely fine when this was happening to me. It will EVENTUALLY remount, and all of your data will be there. It can just take an entirely unreasonable amount of time. 

Link to post
Share on other sites
  • 0

Okay.

 

I do believe that I've bugged this behavior already, so Alex will take a look into it. 

 

Also, Alex has reworked some of the download code, so it may help with this. 

 

 

As for the retry, it does.  however, after too many errors in a short period (120 seconds), the drive unmounts.  The reason for this is that Windows is very sensitive to IO problems.  So the choice here is wait and let Windows hang (this was happening a lot, when issues were occurring, causing system instability), or to disconnect the drive.   Neither is great, ut  we choose system stability over functionality. 

 

 

As for auto-retrying, it would not fix this issue.  Addressing the root cause would be better in the long term, though. Even if that's adding special handling for indexing. 

 

 

Either way, we do appreciate the feedback.  

Link to post
Share on other sites
  • 0

Christopher,

 

To be clear: Are you saying that it is retrying multiple times even though the service log only records one error? Because I can see where it retries when the drive is actually mounted, but only a *single* server error needs to show up in the logs during the indexing process in order for it to completely restart the process. I'll paste you an example:

CloudDrive.Service.exe	Information	0	[ChunkIdSQLiteStorage:26]   chunks IDs: 2067212,2067217,2067218,2067219,2067220,2067221,2067222,2067223,2067224,2067225,2067226,2067227,2067228,2067229,2067230,2067231,2067232,2067233,2067234,2067235,2067236,2067237,2067238,2067239,2067240,2067241,2067242,2067243,2067244,2067245,2067246,2067247,2067248,2067249,2067250,2067251,2067252,2067253,2067254,2067255,2067256,2067257,2067258,2067259,2067260,2067261,2067262,2067263,2067264,2067265,2067266,2067267,2067268,2067269,2067270,2067271,2067272,2067273,2067274,2067275,2067276,2067277,2067278,2067279,2067280,2067281,2067282,2067283,2067284,2067285,2067286,2067287,2067288,2067289,2067290,2067291,2067292,2067293,2067294,2067295,2067296,2067297,2067298,2067299,2067300,2067301,2067302,2067303,2067304,2067305,2067306,2067307,2067308,2067309,2067310,2067311,2067312,2067313,2067314,2067315	2017-07-04 07:50:02Z	209022985613
CloudDrive.Service.exe	Warning	0	[ApiGoogleDrive:26] Google Drive returned error (internalError): Internal Error	2017-07-04 07:50:07Z	209039853973
CloudDrive.Service.exe	Warning	0	[ApiHttp:26] HTTP protocol exception (Code=InternalServerError).	2017-07-04 07:50:07Z	209039867036
CloudDrive.Service.exe	Warning	0	[CloudDrives] Cannot start I/O manager for cloud part 62179051-cb2c-46b8-818d-4ee2a186e3ec. Internal Error	2017-07-04 07:50:07Z	209039897780
CloudDrive.Service.exe	Information	0	[CloudDrives] Synchronizing cloud drives...	2017-07-04 07:50:10Z	209048101740
CloudDrive.Service.exe	Information	0	[Disks] Got Disk_Modify (Disk ID: a439b0c4-9e85-42a7-bccc-01ed3ff606dd, Name: INTEL SSDSC2BB160G4, Adaptor: Standard SATA AHCI Controller, Device path: \\?\scsi#disk&ven_intel&prod_ssdsc2bb160g4#4&15828421&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})...	2017-07-04 07:50:13Z	209058284693
CloudDrive.Service.exe	Information	0	[Disks] Got Disk_Modify (Disk ID: c5c2798c-a82e-420b-97c2-0bd1f6740b75, Name: INTEL SSDSC2BB160G4, Adaptor: Standard SATA AHCI Controller, Device path: \\?\scsi#disk&ven_intel&prod_ssdsc2bb160g4#4&15828421&0&030000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})...	2017-07-04 07:50:13Z	209058286325
CloudDrive.Service.exe	Information	0	[Disks] Got Disk_Modify (Disk ID: be624dce-5691-42a7-b43a-0ebc2693e4c7, Name: INTEL SSDSC2BB160G4, Adaptor: Standard SATA AHCI Controller, Device path: \\?\scsi#disk&ven_intel&prod_ssdsc2bb160g4#4&15828421&0&040000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})...	2017-07-04 07:50:13Z	209058286790
CloudDrive.Service.exe	Information	0	[Disks] Got Disk_Modify (Disk ID: 57d7cdea-d18a-47e2-a3d1-40012094e450, Name: Covecube Virtual Disk, Adaptor: Covecube Cloud Disk Enumerator, Device path: \\?\SCSI#DiskCOVECUBECloudFs_________0001#1&2afd7d61&0&{53883972-f0d3-45bf-897d-8d8cb951cbb2}#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})...	2017-07-04 07:50:13Z	209058287247
CloudDrive.Service.exe	Warning	0	[ChunkIdHelper:26] Chunk ID storage engine does not have all the chunk IDs. Enumerating chunks...	2017-07-04 07:50:13Z	209059088095
CloudDrive.Service.exe	Information	0	[ChunkIdSQLiteStorage:26] Clear all chunk IDs...	2017-07-04 07:50:13Z	209059088767
CloudDrive.Service.exe	Information	0	[Disks] Got Disk_Modify (Disk ID: a439b0c4-9e85-42a7-bccc-01ed3ff606dd, Name: INTEL SSDSC2BB160G4, Adaptor: Standard SATA AHCI Controller, Device path: \\?\scsi#disk&ven_intel&prod_ssdsc2bb160g4#4&15828421&0&020000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})...	2017-07-04 07:50:14Z	209059949614
CloudDrive.Service.exe	Information	0	[Disks] Got Disk_Modify (Disk ID: c5c2798c-a82e-420b-97c2-0bd1f6740b75, Name: INTEL SSDSC2BB160G4, Adaptor: Standard SATA AHCI Controller, Device path: \\?\scsi#disk&ven_intel&prod_ssdsc2bb160g4#4&15828421&0&030000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})...	2017-07-04 07:50:14Z	209059951785
CloudDrive.Service.exe	Information	0	[Disks] Got Disk_Modify (Disk ID: be624dce-5691-42a7-b43a-0ebc2693e4c7, Name: INTEL SSDSC2BB160G4, Adaptor: Standard SATA AHCI Controller, Device path: \\?\scsi#disk&ven_intel&prod_ssdsc2bb160g4#4&15828421&0&040000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})...	2017-07-04 07:50:14Z	209059953983
CloudDrive.Service.exe	Information	0	[Disks] Got Disk_Modify (Disk ID: 57d7cdea-d18a-47e2-a3d1-40012094e450, Name: Covecube Virtual Disk, Adaptor: Covecube Cloud Disk Enumerator, Device path: \\?\SCSI#DiskCOVECUBECloudFs_________0001#1&2afd7d61&0&{53883972-f0d3-45bf-897d-8d8cb951cbb2}#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})...	2017-07-04 07:50:14Z	209059955406
CloudDrive.Service.exe	Information	0	[Disks] Updating disks / volumes...	2017-07-04 07:50:15Z	209063279396
CloudDrive.Service.exe	Information	0	[ChunkIdSQLiteStorage:26] Set chunks IDs...	2017-07-04 07:50:19Z	209076555738
CloudDrive.Service.exe	Information	0	[ChunkIdSQLiteStorage:26]   chunks IDs: 11,139,142,1856284,2797743,2797744,2797745,2797746,4210125,4210126,4210127,4210128,4210129,4210130,4210131,4210132,4210133,4210134,4210135,4210136,4210137,4210138,4210139,4210140,4210141,4210142,4210143,4210144,4210145,4210146,4210147,4210148,4210149,4210150,4210151,4210152,4210153,4210154,4210155,4210156,4210157,4210158,4210159,4210160,4210161,4210162,4210163,4210164,4210165,4210166,4210167,4210168,4210169,4210170,4210171,4210172,4210173,4210174,4210175,4210176,4210177,4210178,4210179,4210180,4210181,4210182,4210183,4210184,4210185,4210186,4210187,4210188,4210189,4210190,4210191,4210192,4210193,4210194,4210195,4210196,4210197,4210198,4210199,4210200,4210201,4210202,4210203,4210204,4210205,4210206,4210207,4210208,4210209,4210210,4210211,4210212,4210213,4210214,4210215,4210216	2017-07-04 07:50:19Z	209078418489
CloudDrive.Service.exe	Warning	0	[ApiGoogleDrive:106] Google Drive returned error (userRateLimitExceeded): User Rate Limit Exceeded	2017-07-04 07:50:19Z	209078588436
CloudDrive.Service.exe	Warning	0	[ApiHttp:106] HTTP protocol exception (Code=ServiceUnavailable).	2017-07-04 07:50:19Z	209078598915
CloudDrive.Service.exe	Warning	0	[ApiHttp] Server is throttling us, waiting 1,236ms and retrying.	2017-07-04 07:50:19Z	209078599786

You can see, here, that it only got a single server error before deciding to enumerate the chunks again. It was at roughly chunk number 2067212, it gets the error, and then it starts over again at chunk number 4210125. As far as I can tell, there are no successive server errors in this log. Just one. One was all it took to restart the process.

 

Here is another, even simpler, log snippet from a different occasion of the same situation:

CloudDrive.Service.exe	Information	0	[ChunkIdSQLiteStorage:26]   chunks IDs: 1008805,1008806,1008807,1008808,1008809,1008810,1008811,1008812,1008813,1008814,1008815,1008816,1008817,1008818,1008819,1008820,1008821,1008822,1008823,1008824,1008825,1008826,1008827,1008828,1008829,1008830,1008831,1008832,1008833,1008834,1008835,1008836,1008837,1008838,1008839,1008840,1008841,1008842,1008843,1008844,1008845,1008846,1008847,1008848,1008849,1008850,1008851,1008852,1008853,1008854,1008855,1008856,1008857,1008858,1008859,1008860,1008861,1008862,1008863,1008864,1008865,1008866,1008867,1008868,1008869,1008870,1008871,1008872,1008873,1008874,1008875,1008876,1008877,1008878,1008879,1008880,1008881,1008882,1008883,1008884,1008885,1008886,1008887,1008888,1008889,1008890,1008891,1008892,1008893,1008894,1008895,1008896,1008897,1008898,1008899,1008901,1008902,1008903,1008905,1008906	2017-07-05 05:37:37Z	179431003884
CloudDrive.Service.exe	Warning	0	[ApiGoogleDrive:26] Google Drive returned error (internalError): Internal Error	2017-07-05 05:38:06Z	179525435228
CloudDrive.Service.exe	Warning	0	[ApiHttp:26] HTTP protocol exception (Code=InternalServerError).	2017-07-05 05:38:06Z	179525436540
CloudDrive.Service.exe	Warning	0	[CloudDrives] Cannot start I/O manager for cloud part 62179051-cb2c-46b8-818d-4ee2a186e3ec. Internal Error	2017-07-05 05:38:06Z	179525503627
CloudDrive.Service.exe	Information	0	[CloudDrives] Synchronizing cloud drives...	2017-07-05 05:39:57Z	179895055905
CloudDrive.Service.exe	Warning	0	[ChunkIdHelper:26] Chunk ID storage engine does not have all the chunk IDs. Enumerating chunks...	2017-07-05 05:39:58Z	179898074584
CloudDrive.Service.exe	Information	0	[ChunkIdSQLiteStorage:26] Clear all chunk IDs...	2017-07-05 05:39:58Z	179898075210
CloudDrive.Service.exe	Information	0	[ChunkIdSQLiteStorage:26] Set chunks IDs...	2017-07-05 05:40:06Z	179923605343
CloudDrive.Service.exe	Information	0	[ChunkIdSQLiteStorage:26]   chunks IDs: 11,139,142,1856284,2797743,2797744,2797745,2797746,4210125,4210126,4210127,4210128,4210129,4210130,4210131,4210132,4210133,4210134,4210135,4210136,4210137,4210138,4210139,4210140,4210141,4210142,4210143,4210144,4210145,4210146,4210147,4210148,4210149,4210150,4210151,4210152,4210153,4210154,4210155,4210156,4210157,4210158,4210159,4210160,4210161,4210162,4210163,4210164,4210165,4210166,4210167,4210168,4210169,4210170,4210171,4210172,4210173,4210174,4210175,4210176,4210177,4210178,4210179,4210180,4210181,4210182,4210183,4210184,4210185,4210186,4210187,4210188,4210189,4210190,4210191,4210192,4210193,4210194,4210195,4210196,4210197,4210198,4210199,4210200,4210201,4210202,4210203,4210204,4210205,4210206,4210207,4210208,4210209,4210210,4210211,4210212,4210213,4210214,4210215,4210216	2017-07-05 05:40:06Z	179925052680

Again, it was at chunk number 1008805 and after a SINGLE server error it's back at 4210125. It does not seem to be retrying chunk 1008805 at all. It does not, in fact, even wait for a second server error. It just starts over at the beginning.

 

So, again, are there additional attempts to retry these reads that are not being recorded in the logs? Or are we still just failing to understand each other about the problem?

 

Additionally, the drive is not unmounting at all--well, not most of the time. It's just restarting the indexing process. So the expected behavior if it was getting multiple errors within a 120 second window is also not obtaining. I can also tell you that I've literally been sitting here and watching the service tracing logs when this happens, and it certainly isn't waiting 120 seconds between getting that error and starting over. It's a matter of seconds. Maybe one or two.

 

I appreciate that Alex is already looking at it, but I also want to make sure that we're clear about this particular problem--and I'm not sure that we are. 

 

Again: this is a separate, less tolerant behavior during the reindexing process than the 120 sec threshold timeouts that you are describing. At least as far as I can tell. If there is something I'm missing, though, please let me know. 

Link to post
Share on other sites
  • 0

I'll have to double check, but the general logic for any sort of API call here (be it enumeration like this, uploading, downloaded, etc) is that when it's failed, it will be retried.   

 

That said, you are seeing the "internal error" code, which is a server side HTTP error (specifically HTTP 500, usually).  It means something "bad" happened on the server side. Retrying shoudl happen, but may cause issues.

 

 

Also, for reference, notice the ":26" for in each of the requests?  This is the thread number, so you can see that this thread is working on the same stuff (indexing and storing to SQLite)

 

 

 

I have flagged the issue for review, including some of that you're seeing.  And I've asked a couple of questions about handling/retrying/special handling for this.  

 

Hopefully, we're able to get to this issue soon, and fix it quickly. 

Link to post
Share on other sites
  • 0

Sadly, I'm back with more problems.

 

I've updated to the latest beta and I need to reauthorize the drive everytime it starts. Logs show a "Cannot start I/O manager for cloud part xxx (security exception). Security error." problem.

 

When I reauthorize (and if I'm lucky), CD gets back online without re-indexing. If I'm not then it re-indexes everything all over.

 

Any idea?

0:00:30.3: Information: 0 : [CloudDrives] Synchronizing cloud drives...
0:00:30.4: Information: 0 : [Main] Cleaning up cloud drives...
0:00:30.5: Information: 0 : [CloudDrives] Valid encryption key specified for cloud part xxx.
0:00:30.6: Warning: 0 : [CloudDrives] Cannot start I/O manager for cloud part xxx (security exception). Security error.
0:00:30.9: Information: 0 : [CloudDrives] Synchronizing cloud drives...
0:00:30.9: Warning: 0 : [CloudDrives] Cannot start I/O manager for cloud part xxx (security exception). Security error.
0:00:31.6: Information: 0 : [ChunkIdSQLiteStorage:4] Cleaning up drives...
0:00:31.6: Information: 0 : [Main] Enumerating disks...
0:00:31.6: Information: 0 : [Disks] Updating disks / volumes...
0:00:33.1: Information: 0 : [Main] Starting disk metadata...
0:00:33.1: Information: 0 : [Main] Updating free space...
0:00:33.1: Information: 0 : [Main] Service started.
0:12:44.2: Information: 0 : [CloudDrives] Synchronizing cloud drives...
0:12:44.2: Warning: 0 : [CloudDrives] Cannot start I/O manager for cloud part xxx (security exception). Security error.
0:12:46.0: Information: 0 : [CloudDrives] Synchronizing cloud drives...
0:12:46.0: Warning: 0 : [CloudDrives] Cannot start I/O manager for cloud part xxxx (security exception). Security error.
0:13:14.4: Information: 0 : [CloudDrives] Synchronizing cloud drives...
0:13:18.9: Information: 0 : [CloudDrives] Synchronizing cloud drives...
0:13:18.9: Information: 0 : [Disks] Got Pack_Arrive (pack ID: yyy)...
0:13:18.9: Information: 0 : [Disks] Got Disk_Arrive (disk ID: yyy)...
0:13:19.9: Information: 0 : [Disks] Updating disks / volumes...
0:13:20.4: Information: 0 : [CloudDrives] Synchronizing cloud drives...
0:13:20.9: Information: 0 : [Disks] Got Volume_Arrive (volume ID: xxxx, plex ID: 00000000-0000-0000-0000-000000000000, %: 0)...
0:13:20.9: Information: 0 : [Disks] Got drive letter assign (volume ID: xxx)...
0:13:22.5: Information: 0 : [Disks] Updating disks / volumes...
0:13:24.9: Information: 0 : [Disks] Got Disk_Modify (Disk ID: xxx
0:13:24.9: Information: 0 : [Disks] Got Disk_Modify (Disk ID: xxx
 and more...
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...