Jump to content
Covecube Inc.

Sergey Klepov

Members
  • Content Count

    6
  • Joined

  • Last visited

  1. Well, the main idea was to use drive pool for such folder because it may be very big one... I just turned off "save space" feature for now in OneDrive. Tried to collect logs, but that doesn't provide anything, the error is not inside of pool, the error is raised in OneDrive app which "couldn't connect to Windows"... Which goes along with high disk activity in the pool. That is pretty strange behaviour, may be it will be better to try to reproduce by yourself. Shall I report bug? I couldn't find anything about such issue so may be there was no report on it before.
  2. Not sure what do you mean? I moved onedrive folder to the pool drive, so all files are in the pool. All is ok until I turn on "Save space and download files as you use them" in onedrive.
  3. I decided to move onedrive to drivepool since I have 1Tb one drive space and there is not much space on system drive. Everything works correctly even with balancing in action which is great, unless I don't turn on "download files on demand" option in one drive. I noticed that if I have that option turned on (which is natural, I don't need 1Tb data copy on my disk) OneDrive starts to behave strangely and raises errors "OneDrive couldn't connect to windows" and tries to sync files infinitely while OneDrive tries to write those fictive files to disks. I had to turn off that option but that is unfortunate - I'd like to keep that option on and I'd like to keep OneDrive inside of pool. Is it possible that it will be fixed in the future?
  4. Yes, that makes sense, but don't remember any big update from microsoft being installed after 10th and there was no update for drive pool also. Anyway issue was resolved, thanks
  5. Actually it did help, thanks. Not sure what, but I have a suspicion that I forgot to run installer with admin privileges
  6. Heard many good things about DrivePool, decided to test it. Have downloaded the latest stable build available on main downloads page for win10 x64 (2.2.2.934). Installed it, started drivepool - received an error "Background service failed to start, please restart". Restarted windows several times, restarted windows service of drivepool several times - didn't help. Checked logs of service - what I see there is DrivePool.Service.exe Information 0 [BitLocker] BitLocker monitoring started 2018-08-08 20:19:46Z 1169533024 DrivePool.Service.exe Information 0 [Main] StableBit DrivePool 2.2.2.934 2018-08-08 20:20:50Z 34181655 DrivePool.Service.exe Information 0 [Main] Microsoft Windows NT 10.0.17134.0 2018-08-08 20:20:50Z 34198889 DrivePool.Service.exe Error 0 [Main] Unable to start StableBit DrivePool service, CoveFS was not found. Exception of type 'DrivePoolService.Pool.CoveFsDriver.FsControl+#APh' was thrown. 2018-08-08 20:20:50Z 34246849 Emm, of course I don't have CoveFS on first clean install. How to make that thing work?
×
×
  • Create New...