Kuno

I had serious issues with ACD corrupting my files as they were uploaded. At one point I was at over 300 tries to upload a single block. ACD is so not ready for the sheer amount of data the are getting. And also, they are starting to lock accounts of people who do not have encrypted data. So anyone who was dumb enough to use Plex Cloud without encrypting their data, will enjoy losing everything they've uploaded. Once your account is locked, all your data is gone. From a fresh post in /r/plex on reddit today.

Amazon has 100% access to your files, it even says so in the TOS. They can and WILL browse your media. They also use dedupe software to delete your stuff and replace it with links to one centralized version. Everything you upload to ACD should be 100% encrypted, unless you like other people having access to your data.

ACD has been such a clusterf@ck, and things are just going to get worse with Plex Cloud. I'm glad I got in on the 5 dollar for a year on cyber monday last year. Now if only I could get a cheap google work account or a school account, with unlimited storage. At this point I am seriously considering not renewing ACD as it's been horrible for any support outside of linux.

Emby supports quicksync and NVENC transcoding (2 stream limit on consumer cards, 4 on Quadros), and possibly soon VCE, where as Plex does not. Emby also allows you to control your playback on your clients so you can have direct play if your device supports it. It's what makes those $30 cheap chinese boxes so awesome. Heck it's what will make the Xaoimi Android box from Walmart so awesome. Install SPMC and use it as an external player and you have full DTS Passthrough, not DTS-HDMA or Tru-DTS though, and definitely not ATMOS. For those you need a shield. But again Plex does not offer this option. Plex users always seem to complain that their servers are not powerful enough because Plex sucks balls at direct playing content. The only clients I have that transcode are my 2 Roku users and 1 Apple TV 4. The rest use Android and direct play EVERYTHING. 10bit HEVC is wonderful for bandwidth saving.

I am just stating that ACD uses dedupe, and if you have encryption turned off, there is the possibility you will lose your stuff. That's all.

The reason it downloads is because it is verifying that what you upload, is actually what is on the drive. Amazon uses dedupe service and will delete files that are duplicates across multiple users to save space, and use a standard file to replace it. They don't do it by hashes sadly so you can end up with something completely different then what you uploaded. Read on reddit that some people have had mp3 files replaced with just standard ones, when they ones they uploaded were explicit versions. I have had to stop using ACD as the amount of CRC errors I was getting on their service was horrendous. See my post about checksum mismatch in the General forum.

Well I had to stop using ACD as it got stuck with checksum mismatch errors. I had 100 megs left to write and the stupid ACD kept giving me CRC errors. I had over 500 attempts to write my final blocks of data. I guess I'll just wait patiently until Amazon gets their head out of their asses and officially supports this awesome product.

Thank you so much for your responses. So dumb question. Does that mean because I have data verification on, I don't have to worry about this. The data verification will re-upload the files that did not match checksum and keep trying until it does match, correct? Or am I being over optimistic? Awesome product I am so glad I bought it.

it also doesn't help that apparently Luke Cage brought down the entire AWS for a while.

Checked my logs and it seems Amazon are being dicks ATM. 1:15:53.4: Warning: 0 : [WholeChunkIoImplementation] Error on read when performing master partial write. Checksum mismatch. Data read from the provider has been corrupted. 1:15:53.5: Warning: 0 : [ioManager:43] Error performing I/O operation on provider. Retrying. Checksum mismatch. Data read from the provider has been corrupted. 1:16:12.8: Warning: 0 : [ChecksumBlocksChunkIoImplementation:43] Checksum mismatch for chunk 2299, ChunkOffset=0x02000800, ReadChecksum=0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, ComputedChecksum=0x3a92ab3c91b0297e233a5b48d43e39c820f5409a8b9e4d86ecd8ddf6e825fd1342101fff88f77333926f946a74a2b63296df0cf9ed21b74b07f20f13e90dbe23. 1:16:13.9: Warning: 0 : [WholeChunkIoImplementation] Error on read when performing master partial write. Checksum mismatch. Data read from the provider has been corrupted. 1:16:13.9: Warning: 0 : [ioManager:43] Error performing I/O operation on provider. Retrying. Checksum mismatch. Data read from the provider has been corrupted. 1:16:33.1: Warning: 0 : [ChecksumBlocksChunkIoImplementation:43] Checksum mismatch for chunk 2299, ChunkOffset=0x02000800, ReadChecksum=0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, ComputedChecksum=0x3a92ab3c91b0297e233a5b48d43e39c820f5409a8b9e4d86ecd8ddf6e825fd1342101fff88f77333926f946a74a2b63296df0cf9ed21b74b07f20f13e90dbe23. 1:16:34.3: Warning: 0 : [WholeChunkIoImplementation] Error on read when performing master partial write. Checksum mismatch. Data read from the provider has been corrupted. 1:16:34.3: Warning: 0 : [ioManager:43] Error performing I/O operation on provider. Retrying. Checksum mismatch. Data read from the provider has been corrupted. 1:16:43.7: Warning: 0 : Unable to read MFT. File record invalid. 1:16:43.7: Warning: 0 : Unable to read MFTMirr. File record invalid. 1:16:43.7: Warning: 0 : [PinDiskMetadata] Error pinning NTFS data. Unable to read MFTMirr. File record invalid. 1:19:23.0: Warning: 0 : [ioManager:43] Thread abort performing I/O operation on provider. 1:19:23.0: Warning: 0 : [ioManager:43] Error writing range: Offset=241,070,112,768. Length=102,367,232. Thread was being aborted.. 1:19:54.3: Warning: 0 : [ChecksumBlocksChunkIoImplementation:43] Checksum mismatch for chunk 2299, ChunkOffset=0x02000800, ReadChecksum=0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, ComputedChecksum=0x3a92ab3c91b0297e233a5b48d43e39c820f5409a8b9e4d86ecd8ddf6e825fd1342101fff88f77333926f946a74a2b63296df0cf9ed21b74b07f20f13e90dbe23. 1:19:55.3: Warning: 0 : [WholeChunkIoImplementation] Error on read when performing master partial write. Checksum mismatch. Data read from the provider has been corrupted. 1:19:55.3: Warning: 0 : [ioManager:43] Error performing I/O operation on provider. Retrying. Checksum mismatch. Data read from the provider has been corrupted. 1:20:14.6: Warning: 0 : [ChecksumBlocksChunkIoImplementation:43] Checksum mismatch for chunk 2299, ChunkOffset=0x02000800, ReadChecksum=0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, ComputedChecksum=0x3a92ab3c91b0297e233a5b48d43e39c820f5409a8b9e4d86ecd8ddf6e825fd1342101fff88f77333926f946a74a2b63296df0cf9ed21b74b07f20f13e90dbe23. 1:20:15.7: Warning: 0 : [WholeChunkIoImplementation] Error on read when performing master partial write. Checksum mismatch. Data read from the provider has been corrupted. 1:20:15.8: Warning: 0 : [ioManager:43] Error performing I/O operation on provider. Retrying. Checksum mismatch. Data read from the provider has been corrupted. 1:20:40.5: Warning: 0 : [ChecksumBlocksChunkIoImplementation:43] Checksum mismatch for chunk 2299, ChunkOffset=0x02000800, ReadChecksum=0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, ComputedChecksum=0x3a92ab3c91b0297e233a5b48d43e39c820f5409a8b9e4d86ecd8ddf6e825fd1342101fff88f77333926f946a74a2b63296df0cf9ed21b74b07f20f13e90dbe23. 1:20:41.7: Warning: 0 : [WholeChunkIoImplementation] Error on read when performing master partial write. Checksum mismatch. Data read from the provider has been corrupted. 1:20:41.7: Warning: 0 : [ioManager:43] Error performing I/O operation on provider. Retrying. Checksum mismatch. Data read from the provider has been corrupted. 1:24:53.6: Warning: 0 : [ioManager:43] Thread abort performing I/O operation on provider. 1:24:53.6: Warning: 0 : [ioManager:43] Error writing range: Offset=241,070,112,768. Length=102,367,232. Thread was being aborted.. 1:30:24.3: Warning: 0 : [ioManager:43] Thread abort performing I/O operation on provider. 1:30:24.3: Warning: 0 : [ioManager:43] Error writing range: Offset=241,070,112,768. Length=102,367,232. Thread was being aborted.. 1:35:55.0: Warning: 0 : [ioManager:43] Thread abort performing I/O operation on provider. 1:35:55.0: Warning: 0 : [ioManager:43] Error writing range: Offset=241,070,112,768. Length=102,367,232. Thread was being aborted.. 1:36:35.2: Information: 0 : Comm server stopped on: tcp://127.0.0.1:26525/Comm1 1:36:35.2: Warning: 0 : [RemoteControlKeepAliveListener] Error receiving. A blocking operation was interrupted by a call to WSACancelBlockingCall 1:37:50.2: Warning: 0 : [ChecksumBlocksChunkIoImplementation:43] Checksum mismatch for chunk 2299, ChunkOffset=0x02000800, ReadChecksum=0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, ComputedChecksum=0x3a92ab3c91b0297e233a5b48d43e39c820f5409a8b9e4d86ecd8ddf6e825fd1342101fff88f77333926f946a74a2b63296df0cf9ed21b74b07f20f13e90dbe23. 1:37:51.3: Warning: 0 : [WholeChunkIoImplementation] Error on read when performing master partial write. Checksum mismatch. Data read from the provider has been corrupted. 1:37:51.3: Warning: 0 : [ioManager:43] Error performing I/O operation on provider. Retrying. Checksum mismatch. Data read from the provider has been corrupted. Thus far my uploads have been aborted by Amazon 108 times.

It states right when you enable the ACD that it is an experimental provider and because of that it is severely limited. 20mbit up, 50mbit down. It won't change until Amazon gets their shit together.

Last night while continuing to upload my stuff to ACD, I apparently had just a few errors. Error: Checksum mismatch. Data read from the provider has been corrupted. I have data verification turned on, for obvious reasons. I also have 100/50 internet. I does appear as if Amazon is not playing nice as I am also dealing with a lot of aborted threads from them. I really enjoy your product and I can't wait until I learn how to use drive pool with all the drives I have. Oh and I only have it connected to one computer, nothing else. But I do have netdrive also installed and have ACD mapped to another drive. Could that be causing an issue? Even though Stablebit cloud drive creates its own directory on ACD.

They do analyze and will browse through your files. It's actually in the TOS for ACD. If they catch you having copyrighted material they can delete it, and other things. You will also receive this nice email. Dear customer, It has come to our attention that your account has shared content that violates the Cloud Drive Terms of Use. As a result, the sharing feature on your account has been disabled. Please refer to the Terms of Use for more information: https://www.amazon.com/gp/drive/tou If you feel this decision was made in error, you can appeal the decision by sending an email to clouddrive-content@amazon.com. We appreciate your cooperation. Sincerely, Amazon Cloud Drive Customer Service Plex and Amazon are partnering on this, but there is no encryption being done, and non being supported. You are honestly better off to have a beast of a machine and a fat pipe and use rclone for linux, or stablebit for windows, as pretty much every other option for windows sucks. I've tried them, and THIS is the only one that works properly. I just can't wait for Amazon to get their shit together and give you proper access. This 20mbit upload sucks when I got 30+TB to upload to my ACD for backup.

Wow that is fantastic news

Hrmm that's weird, it wasn't running at all. I have done a repair install, and it appears to have fixed the problem. My system recently updated to build 1607 of windows 10 Pro. It was right after that build KB3193494 and KB3176936 were installed that it stopped working. Thank you for your extremely quick response. I will definitely be buying, no matter what Amazon's stance is, your product is freaking awesome.