Jump to content
  • 0

Multiple warnings result in unable to complete pushes to ACD


kirkyg

Question

So i've been struggling to get off the ground with pushing files to Amazon Cloud Drive using Stablebit Cloud drive.  I'm actually testing this product along with some other individuals i know for similar purposes and I'm the only one of us that has had this many problems.

 

Here is the behavior that I'm seeing...

 

Typically i'll copy a not so large set of files (say 5-15GB), then most of the time during this file copy (usually towards the end if not the last few chunks) it will just continuing retry and fail.  Here are some of the errors I'm seeing (these are in no particular order and have happened many times in the past couple of weeks).  Also, to resolve this issue re-authentication does not typically work and the only way i can bypass is it will usually work with i disabled the download verification.  I note that I have a low upload bandwidth with my poor internet (1.4mbps) - is it required to have a certain upload speed to be able to push to stablebit?  Please let me know if you have any suggestions or thoughts on what may be happening here.

 

CloudDrive.Service.exe Warning 0 [ioManager:31] HTTP error (ServiceUnavailable) performing I/O operation on provider. 2016-11-08 00:20:12Z 836855831764
CloudDrive.Service.exe Warning 0 [ioManager:31] Error performing I/O operation on provider. Retrying. HTTP Status ServiceUnavailable 2016-11-08 00:20:12Z 836855834047
CloudDrive.Service.exe Warning 0 [WholeChunkIoImplementation] Error on read when performing master partial write. HTTP Status ServiceUnavailable 2016-11-08 00:20:13Z 836859436241

 

CloudDrive.Service.exe Warning 0 [ioManager:5] Error performing I/O operation on provider. Retrying. The write operation failed, see inner exception. 2016-11-08 02:25:12Z 862519557055
CloudDrive.Service.exe Warning 0 [ioManager:5] Error writing range: Offset=37,518,049,280. Length=10,485,760. Thread was being aborted.. 2016-11-08 02:25:12Z 862519936352
 
CloudDrive.Service.exe Warning 0 [ioManager:5] [W]   Verification FAILED: Offset=0x00000008C0000000, Length=4,222,976. 2016-11-08 02:32:16Z 863970953478
CloudDrive.Service.exe Warning 0 [ioManager:5] Error performing I/O operation on provider. Retrying. Write verification has detected a data inconsistency when uploading data to the cloud. 2016-11-08 02:32:16Z 863971039780
 
CloudDrive.Service.exe Warning 0 Unable to read MFT. File record invalid. 2016-11-08 02:37:35Z 865061934422
CloudDrive.Service.exe Warning 0 Unable to read MFTMirr. File record invalid. 2016-11-08 02:37:35Z 865061935345
CloudDrive.Service.exe Warning 0 [PinDiskMetadata] Error pinning NTFS data. Unable to read MFTMirr. File record invalid. 2016-11-08 02:37:35Z 865061936061
 
CloudDrive.Service.exe Warning 0 [WholeChunkIoImplementation] Error on write when performing master partial write. The write operation failed, see inner exception. 2016-11-07 21:26:06Z 801109042587
CloudDrive.Service.exe Warning 0 [ioManager:31] Error performing I/O operation on provider. Retrying. The write operation failed, see inner exception. 2016-11-07 21:26:06Z 801109111427
CloudDrive.Service.exe Warning 0 [ioManager:31] Error writing range: Offset=40,454,062,080. Length=5,406,720. Thread was being aborted.. 2016-11-07 21:26:06Z 801109830502

 

post-2839-0-68439100-1478575604_thumb.jpg

post-2839-0-10538900-1478575701_thumb.jpg

 

Thanks in advance for any help with these issues!

Link to comment
Share on other sites

10 answers to this question

Recommended Posts

  • 0

To be blunt, it looks like you're having a communication issue here. 

 

Either it may be a local network issue, or it may be with communication with Amazon's servers (eg, server side). 

 

The small snippets of longs that you've posted indicate this, and that it's handling these errors "gracefully" for the most part. 

 

However, I'd recommend upgrading to the 1.0.0.631 build, as this may significnatly improve reliability. 

http://dl.covecube.com/CloudDriveWindows/beta/download/StableBit.CloudDrive_1.0.0.631_x64_BETA.exe

Link to comment
Share on other sites

  • 0

My upload speed is very limited, but my latency and reliability of the connection is usually pretty good.  That's what I'm trying to understand here.  Is there flaky behavior when below a certain threshold of available bandwidth (meeting timeouts for larger chunk size etc?).  The one thing i dont understand is the loop activity occurring at certain points.  If its connectivity quality i can assure you that im not receiving any packet loss that would cause degradation hours of period of time that it continues to fail.

 

In any case, i will install the beta version and test more.  I will also be switching internet providers in the next few days to a much higher offering upload and download.  I will respond again with findings.

 

Thanks!

Link to comment
Share on other sites

  • 0

That really depends. 

 

On the providers that support it, we use partial uploads.  That means that the chunk sizes may be larger, the chunks of data we're uploading may not be. 

 

And no, there shouldn't be flaky behavior from StableBit CloudDrive.  if there are errors, they get reported and retried. There shouldn't be any issues software side. 

Link to comment
Share on other sites

  • 0

I upgraded my internet to a faster speed and verified i was getting solid connection with no packet loss.  I then sent a 50gb block to start copying.  Everything went well until the last 64mb in which it failed with this error below and kept trying for 6 hours while i was working.  Up until this point the logs showed server throttle normal activity and a sporatic http I/O error and Unable to read MFT.

 

CloudDrive.Service.exe Warning 0 [ioManager:34] [W]   Verification FAILED: Offset=0x0000001142C00000, Length=6,836,224. 2016-11-11 01:58:21Z 1743951062874
CloudDrive.Service.exe Warning 0 [ioManager:34] Error performing I/O operation on provider. Retrying. Write verification has detected a data inconsistency when uploading data to the cloud. 2016-11-11 01:58:21Z 1743951068895
 
This behavior is not indicative of a poor internet connection since as soon as i uncheck the upload verification box it starts finishing the last chunks.  I also had run checkdisk with option to repair anything sectors overnight with no change - however i'm just now remember the drive i ran it on may not have been same hard disk that the stablebit cache is on.  I will run scandisk on the other drive tonight and upgrade to this new version and test again - but i need to resolve these issues before i can really commit alot of data up to the cloud and buy the product to use long term.
Link to comment
Share on other sites

  • 0

I ran checkdisk on correct hard drive and installed the new beta version.  I'm not unable to mount the drive getting the following error:

 
post-2839-0-01660100-1478873305_thumb.jpg
 
Should i have completely removed stablebit and then re-installed?  I tried the 'Retry' and when the drive shows I also tried manually re-authorizing with no success as it continues to fail to mount after a minute or so.  Suggestions?
Link to comment
Share on other sites

  • 0

The error that you posted above is an upload verification.  

These are normal and are handled without issue usually.  Unless they happen too often.  Amazon frequently fails uploads, so we use upload verification to ensure that everything happened properly. 

 

 

These are separate from the "parameter is incorrect" error that you're seeing here.  

Too many of these will cause the drive to unmount (to prevent the system from potentially locking up due to IO errors). 

 

If you could, enable file system logging, click on "Retry" in the notifications, and see if it corrects the issue.

http://wiki.covecube.com/StableBit_CloudDrive_Drive_Tracing

 

If not, grab the logs and upload them to us. 

Link to comment
Share on other sites

  • 0

I turned on trace logging, attempted to retry drive mount.  In the process i got a UI exception that i submitted to report to your server:

 

post-2839-0-06048700-1478915970_thumb.jpg

post-2839-0-46192800-1478915974_thumb.jpg

 

Then after submitting the exception i received a red error from top left as follows:

 

post-2839-0-94363100-1478916040_thumb.jpg

 

In terms of the actual log files I'm assuming you want some files stored in the log folders.  I have attached the current days Service\Logs file.  Did you also want any of the encrypted error files that were generated at 7:51 CST when it errored?

 

CloudDrive.Service-2016-11-11.log

Link to comment
Share on other sites

  • 0

Kirk,

 

Did you upload the logs via the DropBox link in the wiki link above? 

http://wiki.covecube.com/StableBit_CloudDrive_Drive_Tracing

 

If so, I'm not finding reference of it. 

 

 

Additionally, the {SA} reports are blindly sent, so we'd have no idea what they're in reference to. 

 

The log submission guide grabs these error reports, and a bunch of other information, so it's best to grab them and upload them to us directly. 

Link to comment
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...