Jump to content

paulml

Members
  • Posts

    5
  • Joined

  • Last visited

Everything posted by paulml

  1. I believe your 2nd example is exactly what I'm looking for! Just to confirm, if I want to (theoretically) split folder names alphabetically with each letter going to its own separate HDD, I should set up rules as so: \TV-Shows\A*\* ---> HDD-01 \TV-Shows\B*\* ---> HDD-02 \TV-Shows\C*\* ---> HDD-03 and so on until.... \TV-Shows\Z*\* ---> HDD-26 Sorry, just wanted to make sure before I make a significant change Thank you very much for the help!
  2. Hi, I have been micromanaging the placement of folders thru the Folders tab under File Placement. I then came across this post from years ago which suggests that I can use the Rules tab under File Placement to organize the folders alphabetically like so: \TV-Shows\A* ---> HDD-1 \TV-Shows\B* ---> HDD-2 \TV-Shows\C* ---> HDD-3 This should place all subfolders under "TV-Shows" that starts with "A" to HDD-1 and so on. I've always thought the Rules tab was for files and not folders. I would just like to confirm if it indeed works for folders as well and if the above example would work? I couldn't find an activity log to test out the rule and check to see for myself. Thanks!
  3. Hi, it was on and off at the time I made the post so I didn't proceed to make a ticket at all. Everything would suddenly just work perfectly then it would error out again. This happened less and less though and it rarely happens to me now.
  4. Same thing happened to me about a week ago (wanted to change download & upload speed limits) and a reinstall of CloudDrive fixed it for me. Drive data was safe. Upon re-install, program quickly found my drive but I had to go thru the initial setup/preparation. Haven't happened again ever since.
  5. Hi, I currently have 2 drives configured in Stablebit CloudDrive (using 2 different Google Accounts). The other is automatically mounted but the other gives the following error: "This drive cannot be mounted. The drive was forced to unmount because it couldn't read data from the provider." I first thought that it might be a problem on Google's side and it might resolve by itself with time but I then realized my other drive is working perfectly fine so it must not be a problem with Google. I have tried manually logging in to G Drive on the web and it works. I tried the usual PC reboot and internet reconnect but those didn't help. I've tried re-mounting and re-authorizing multiple times but still no go. Running Windows 10 Pro btw. A copy of the recent log file is as follows: 0:00:29.2: Information: 0 : [CloudDrives] Drive 27f5b609-fae8-487e-a8b7-f1c63b40b411 was previously unmountable. User is not retrying mount. Skipping. 0:00:31.9: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:00:31.9: Information: 0 : [CloudDrives] Drive 27f5b609-fae8-487e-a8b7-f1c63b40b411 was previously unmountable. User is not retrying mount. Skipping. 0:00:35.2: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:00:35.2: Information: 0 : [CloudDrives] Drive 27f5b609-fae8-487e-a8b7-f1c63b40b411 was previously unmountable. User is not retrying mount. Skipping. 0:00:37.4: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:00:37.4: Information: 0 : [CloudDrives] Drive 27f5b609-fae8-487e-a8b7-f1c63b40b411 was previously unmountable. User is not retrying mount. Skipping. 0:00:40.1: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:00:40.1: Information: 0 : [CloudDrives] Drive 27f5b609-fae8-487e-a8b7-f1c63b40b411 was previously unmountable. User is not retrying mount. Skipping. 0:00:43.4: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:00:43.4: Information: 0 : [CloudDrives] Drive 27f5b609-fae8-487e-a8b7-f1c63b40b411 was previously unmountable. User is not retrying mount. Skipping. 0:00:43.4: Information: 0 : [CloudDrives] Started 1 cloud drives. 0:00:43.4: Information: 0 : [Main] Enumerating disks... 0:00:43.4: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:00:43.4: Information: 0 : [CloudDrives] Drive 27f5b609-fae8-487e-a8b7-f1c63b40b411 was previously unmountable. User is not retrying mount. Skipping. 0:00:44.8: Information: 0 : [Disks] Updating disks / volumes... 0:00:44.9: Information: 0 : [Main] Starting disk metadata... 0:00:44.9: Information: 0 : [Main] Updating free space... 0:00:44.9: Information: 0 : [Main] Service started. 0:00:44.9: Information: 0 : [Main] Waiting for cloud drives... 0:01:09.7: Information: 0 : [Main] Cleaning up cloud drives... 0:01:09.7: Information: 0 : [ChunkIdSQLiteStorage:5] Cleaning up drives... 0:01:09.7: Information: 0 : [Main] All cloud drives ready. 0:01:17.3: Information: 0 : [Disks] Got Volume_Arrive (volume ID: 4f61b8b4-c7c2-4656-a5cb-981622420b95, plex ID: 00000000-0000-0000-0000-000000000000, %: 0)... 0:01:17.3: Information: 0 : [Disks] Got drive letter assign (volume ID: 4f61b8b4-c7c2-4656-a5cb-981622420b95)... 0:01:18.3: Information: 0 : [Disks] Updating disks / volumes... 0:04:59.0: Information: 0 : [IoManager:33] All writes complete. 0:18:44.1: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:18:44.1: Information: 0 : [CloudDrives] Using public key to unlock cloud part 27f5b609-fae8-487e-a8b7-f1c63b40b411. 0:18:44.1: Information: 0 : [CloudDrives] Valid encryption key specified for cloud part 27f5b609-fae8-487e-a8b7-f1c63b40b411. 0:18:50.0: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:18:52.1: Warning: 0 : [CloudDrives] Cannot mount cloud part 27f5b609-fae8-487e-a8b7-f1c63b40b411. It was force unmounted. 0:18:52.1: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:18:52.1: Information: 0 : [CloudDrives] Drive 27f5b609-fae8-487e-a8b7-f1c63b40b411 was previously unmountable. User is not retrying mount. Skipping. 0:19:09.0: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:19:11.2: Information: 0 : [CloudDrives] Synchronizing cloud drives... 0:19:13.1: Warning: 0 : [CloudDrives] Cannot mount cloud part 27f5b609-fae8-487e-a8b7-f1c63b40b411. It was force unmounted.
×
×
  • Create New...