pocomo Posted September 20, 2016 Posted September 20, 2016 New user here, trialing build 722 on Windows 10. I have created my drive using Google Drive, but it keeps disconnecting with repeated instances of this error (see attached screenshots): [ioManager:72] Error performing I/O operation on provider. Failed. The parameter is incorrect Any clue what this is? I ran a check on my network connection which is pretty solid, results here: http://netalyzr.icsi.berkeley.edu/restore/id=369839a0-12857-24e54d82-c64f-41fc-b12d Right now Cloud Drive is promising but unusable for me. Thanks for any input. Antoineki, Ginoliggime and KiaraEvirm 3 Quote
0 triadcool Posted September 20, 2016 Posted September 20, 2016 I get the same thing on my newly created REFS drive on build 1.0.0.719. Quote
0 pocomo Posted September 21, 2016 Author Posted September 21, 2016 I'm using NTFS with 20MB blocks, if that might have any impact. Quote
0 Christopher (Drashna) Posted September 25, 2016 Posted September 25, 2016 Could you do this: http://wiki.covecube.com/StableBit_CloudDrive_Drive_Tracing I get the same thing on my newly created REFS drive on build 1.0.0.719. Could you upgrade to 1.0.0.722 and see if it continues? Quote
0 pocomo Posted September 26, 2016 Author Posted September 26, 2016 Hi Chris - I'm already running build 722 (see first post). Working on the drive tracing, thanks. Quote
0 pocomo Posted September 27, 2016 Author Posted September 27, 2016 Hi Chris - Drive tracing log attached. Error occur essentially immediately upon re-attaching the drive. Thanks. Service.MH.20160927.zip Quote
0 Christopher (Drashna) Posted September 27, 2016 Posted September 27, 2016 Okay, the errors I'm seeing are "user rate limit exceeded", and that is probably causing the other issues as well. This is a "server side" setting that we need to change, I beleive. Alex is already aware of this, and may have already changed it. I've messaged him directly about it, so if he hasn't yet, he should shortly. Quote
0 pocomo Posted September 28, 2016 Author Posted September 28, 2016 Cool, thanks Chris. I'll keep an eye on this thread for any updates or further info required. Quote
0 Christopher (Drashna) Posted September 28, 2016 Posted September 28, 2016 Alex did look into it (at least a bit) last night. I'm not sure if he changed anything, though. If you're still seeing the issue, let me know. Quote
0 pocomo Posted September 29, 2016 Author Posted September 29, 2016 I did a 'reset all settings to default' just to try and see if this would stabilize things, but to no avail. Upon reboot I unlocked the drive and it errored out and unmounted within 1 minute with the same message as above. I enabled drive tracing again and it took longer to fail this time (maybe 4 minutes?). Same error. Destroyed that drive and created a new one with all default values except for 10 TB size. Got the message dialog 'there was an error while trying to format your drive, try from Disk Management'. Tried from disk management, failed while initializing drive with new partition table. I'm going to try reinstalling, or perhaps wait for a new build to be released to try. Quote
0 pocomo Posted September 30, 2016 Author Posted September 30, 2016 Upgraded to 723 and started over with a fresh install and a new drive. Creation completes but I still get an error during formatting and Disk management is unable to initialize the drive. The service log contains an entry I hadn't seen before "7:40:49.5: Warning: 0 : Error getting info on pack. Sequence contains no elements" but not much else, here's the full contents of the log. 7:37:42.9: Information: 0 : [CloudDrives] Synchronizing cloud drives... 7:37:42.9: Information: 0 : [Disks] Got Disk_Depart (disk ID: 97bac974-efd0-4609-b907-79fc8e20fe68)... 7:37:43.9: Information: 0 : [Disks] Updating disks / volumes... 7:39:53.2: Information: 0 : [CloudDrives] Synchronizing cloud drives... 7:39:53.2: Information: 0 : [CloudDrives] Valid encryption key specified for cloud part 8f206b7d-7318-440f-85bc-39ffc5f61219. 7:39:53.2: Information: 0 : [CloudDrives] Removing cloud drive uid: 876e196f-9e55-4838-bd22-52b4211569e6 (LastSeenUTC=09/30/2016 12:44:47, IsDestroyed=True) 7:39:55.4: Information: 0 : [CloudDrives] Synchronizing cloud drives... 7:39:56.1: Information: 0 : [CloudDrives] Synchronizing cloud drives... 7:39:57.3: Information: 0 : [Disks] Got Disk_Arrive (disk ID: a1727d86-cc27-42ed-85ff-371c84abeca3)... 7:39:57.8: Information: 0 : [Disks] Got Disk_Modify (Disk ID: e972c9b8-d5e4-465f-a74a-5cb90732b756, Name: Samsung SSD 850 PRO 1TB, Adaptor: Intel® 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller - 1C03, Device path: \\?\scsi#disk&ven_samsung&prod_ssd_850_pro_1tb#4&3b66f9aa&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})... 7:39:58.3: Information: 0 : [Disks] Got Disk_Modify (Disk ID: e972c9b8-d5e4-465f-a74a-5cb90732b756, Name: Samsung SSD 850 PRO 1TB, Adaptor: Intel® 6 Series/C200 Series Chipset Family 6 Port SATA AHCI Controller - 1C03, Device path: \\?\scsi#disk&ven_samsung&prod_ssd_850_pro_1tb#4&3b66f9aa&0&000000#{53f56307-b6bf-11d0-94f2-00a0c91efb8b})... 7:39:59.3: Information: 0 : [Disks] Updating disks / volumes... 7:40:00.5: Information: 0 : [Disks] Got Pack_Arrive (pack ID: fa297584-b2a8-499f-944c-e599c9cc0463)... 7:40:01.5: Information: 0 : [Disks] Updating disks / volumes... 7:40:01.5: Warning: 0 : Error getting info on pack. Sequence contains no elements 7:40:03.5: Information: 0 : [Disks] Got Pack_Depart (pack ID: fa297584-b2a8-499f-944c-e599c9cc0463)... 7:40:03.9: Information: 0 : [ioManager:38] All writes complete. 7:40:04.5: Information: 0 : [Disks] Updating disks / volumes... 7:40:48.5: Information: 0 : [Disks] Got Pack_Arrive (pack ID: c3a45202-6dab-44c2-9fca-43335084b87d)... 7:40:49.5: Information: 0 : [Disks] Updating disks / volumes... 7:40:49.5: Warning: 0 : Error getting info on pack. Sequence contains no elements 7:40:50.1: Information: 0 : [Disks] Got Pack_Depart (pack ID: c3a45202-6dab-44c2-9fca-43335084b87d)... 7:40:51.1: Information: 0 : [Disks] Updating disks / volumes... 7:40:51.8: Information: 0 : [ioManager:38] All writes complete. 7:42:33.0: Information: 0 : [Disks] Got Pack_Arrive (pack ID: 072025da-f843-4fa1-b902-3750d1c9a910)... 7:42:34.0: Information: 0 : [Disks] Updating disks / volumes... 7:42:34.0: Warning: 0 : Error getting info on pack. Sequence contains no elements 7:42:36.1: Information: 0 : [Disks] Got Pack_Depart (pack ID: 072025da-f843-4fa1-b902-3750d1c9a910)... 7:42:36.3: Information: 0 : [ioManager:38] All writes complete. 7:42:37.1: Information: 0 : [Disks] Updating disks / volumes... If there isn't much else to try I'll put this aside for a while, thanks. Quote
0 pocomo Posted October 3, 2016 Author Posted October 3, 2016 I created a new drive on Google Drive using v723 and it's kinda working but I am unable to initialize the drive through Win10's disk management interface or cmdline diskpart. I recorded two initialization attempts with drive tracing enabled and uploaded the resulting logs to dropbox. If these turn up anything I would love to hear about it; other folks seem to be having a pretty high success rate. Thanks! Quote
0 everyonce Posted October 4, 2016 Posted October 4, 2016 I'm having the same issues -- let me know if there's any extra data I can help provide... Quote
0 pocomo Posted October 4, 2016 Author Posted October 4, 2016 @everyonce - are you by any chance running VirtualBox on your physical Windows host in your setup? That's the only thing that I think separates my setup from a bog-standard Win10 install. Quote
0 everyonce Posted October 5, 2016 Posted October 5, 2016 I am running on a physical win10 box. I worked around whatever this is... by removing the "drives" from the Google account using clouddrive on a different computer. Then I was able to create a working disk by being sure to check the format and mount checkbox under advanced on the create drive. I also did not use the full disk encryption (though I really do no know what that means since it encrypts stuff anyway) Quote
0 pocomo Posted October 5, 2016 Author Posted October 5, 2016 Cool, thanks for the input. I'll give this recipe a shot when I have some time. Quote
0 steffenmand Posted October 7, 2016 Posted October 7, 2016 I am running on a physical win10 box. I worked around whatever this is... by removing the "drives" from the Google account using clouddrive on a different computer. Then I was able to create a working disk by being sure to check the format and mount checkbox under advanced on the create drive. I also did not use the full disk encryption (though I really do no know what that means since it encrypts stuff anyway) It does really basic default encryption per default to ensure Google and Amazon don't index the files as video/pictures whatever. This encryption is easily cracked. The Full Disc Encryption is proper encryption with a good key involved. Quote
0 pocomo Posted October 9, 2016 Author Posted October 9, 2016 (edited) Update: I decided to start over with a completely generic Win10 Pro install, running inside VmWare ESXi 6 on Intel NUC6 hardware. Got that up and running, installed CloudDrive build 723, set up a new Google Drive disk, no problems. So far it seems to be working fine, no idea what was wrong with my other machine and will probably never know. Edit: forgot to mention that I have seen a few "rate limit exceeded" messages but they have not impeded successful operation. I'm also leaving the chunk integrity checking turned on, as I would really hate to have the drive get corrupted once it starts filling up. Edited October 9, 2016 by pocomo Quote
0 Christopher (Drashna) Posted October 9, 2016 Posted October 9, 2016 Install 1.0.0.725 to fix (or at least reduce) the "Rate Limit Exceeded" warnings. Quote
0 thatvalis Posted October 28, 2016 Posted October 28, 2016 I have been getting "parameter is incorrect" all day as well. Tried 725, 730 and 748. Didn't encounter this error and unmounting of disk before, when I was running the latest stable build. KiaraEvirm, Antoineki and Ginoliggime 3 Quote
0 Christopher (Drashna) Posted October 31, 2016 Posted October 31, 2016 Are you still seeing this? And do you have an open ticket? Quote
0 thatvalis Posted November 1, 2016 Posted November 1, 2016 Yes, I've been seeing this as soon as I increase the download and upload threads. But it has been occuring even when I have something like 3-4 threads (upload and download combined). Currently is seems stable enough at the latest 749 build. No errors in the last 8 hours, but I was also taking it very slow: 1 download thread, 1 upload thread (throttled at 10 mbps). Prefetcher disabled. Currently trying 2 upload threads throttled at 20 mbps, hopefully it will remain stable. I have only been using the service for little over a week (using the latest link from the main download page, 463?), but in the beginning when I was uploading close to 1 TB I didn't run into any problems at all as I recall. Maybe the occasional "rate limit exceeded" but it all went pretty smoothly. I ran much more threads back then too. Quote
0 thatvalis Posted November 2, 2016 Posted November 2, 2016 Just thought I would check in to say that I have been running 4 upload/4 download threads at capped upload speed for me (50 mbit/s) without issues for a long time now. Seems like it's working well again! Version 749. Christopher (Drashna) 1 Quote
0 pocomo Posted November 4, 2016 Author Posted November 4, 2016 I'll chime in as well. CloudDrive has been very stable for me since upgrading to 725 (now at 753). I have not seen the error that started this thread for several weeks at this point. Stability first, then speed - still working on that one Thanks CoveCube, you have the making of a great product here. Christopher (Drashna) 1 Quote
0 Christopher (Drashna) Posted November 4, 2016 Posted November 4, 2016 Just thought I would check in to say that I have been running 4 upload/4 download threads at capped upload speed for me (50 mbit/s) without issues for a long time now. Seems like it's working well again! Version 749. I'm glad to hear that it seems like the performance and issues have improved! If I'm misreading, then please do let me know. Quote
Question
pocomo
New user here, trialing build 722 on Windows 10.
I have created my drive using Google Drive, but it keeps disconnecting with repeated instances of this error (see attached screenshots):
[ioManager:72] Error performing I/O operation on provider. Failed. The parameter is incorrect
Any clue what this is? I ran a check on my network connection which is pretty solid, results here: http://netalyzr.icsi.berkeley.edu/restore/id=369839a0-12857-24e54d82-c64f-41fc-b12d
Right now Cloud Drive is promising but unusable for me.
Thanks for any input.
32 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.