Jump to content

Mikey160984

Members
  • Content Count

    20
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Mikey160984

  • Rank
    Member

Converted

  • Gender
    Male

Recent Profile Visitors

159 profile views
  1. found the problem... its due to the "new lack" of smb. I had it configured via smb to sync the files to the backup server. Had to change it to the local thing now. Had some issues at first, but now it seems to work fine again
  2. Since the last update, DirSync is filling up my Docker Image File to the maximum. Anyone got the same issue? Re-installed it several times, but as soon as it starts to sync, it fills up the Docker File. Didn't change anything before, just updatet...
  3. Another question for 2 GPUs If I type in the the docker only the GPU ID I want to use, the sytem still uses the two GPUs (like the "all" argument). Testet with a reinstall (yes, deletet the folder in appdata). Is this normal?
  4. Another short question or little problem... after a WU got folded it will be sent to the f@h servers, and then it displays "cleanup". But it sticks there. Didn't have the problem with the docker from mobiousnine. After restarting the container, the "cleanup" WU is away from the list. The log says: ... 21:06:38:WU02:FS00:Cleaning up 21:06:38:ERROR:WU02:FS00:Exception: Failed to remove directory './work/02': boost::filesystem::remove: Directory not empty: "./work/02" 21:06:38:WU02:FS00:Cleaning up 21:06:38:ERROR:WU02:FS00:Exception: Failed to remove directory './work/02': boost::filesystem::remove: Directory not empty: "./work/02" 21:07:38:WU02:FS00:Cleaning up 21:07:38:ERROR:WU02:FS00:Exception: Failed to remove directory './work/02': boost::filesystem::remove: Directory not empty: "./work/02" 21:09:15:WU02:FS00:Cleaning up 21:09:15:ERROR:WU02:FS00:Exception: Failed to remove directory './work/02': boost::filesystem::remove: Directory not empty: "./work/02" 21:11:52:WU02:FS00:Cleaning up 21:11:52:ERROR:WU02:FS00:Exception: Failed to remove directory './work/02': boost::filesystem::remove: Directory not empty: "./work/02" 21:16:07:WU02:FS00:Cleaning up 21:16:07:ERROR:WU02:FS00:Exception: Failed to remove directory './work/02': boost::filesystem::remove: Directory not empty: "./work/02" 21:22:58:WU02:FS00:Cleaning up 21:22:58:ERROR:WU02:FS00:Exception: Failed to remove directory './work/02': boost::filesystem::remove: Directory not empty: "./work/02" And I'm not sure, if the points were added to my account as it got not fully finish... Folding too with two other WinPCs and there I do not have this problem. Anyone got same problems?
  5. haha... got the same GT710 lying around and so i thought i put it in the server too... so I only have to add another variable with the GPU ID or should I type all two IDs in the same field? maybe you could assist me in this case. could be interesting for more people Edit: Got it, had to reinstall the Container and typed "all" under Nvidia_Visible_Devices now both GPUs are listed, one is folding, second one waits for WU... should work fine I think
  6. Did anyone try to use more then one nvidia gpu with this container? editing the config for a second gpu slot is no problem, but do both gpus work as they should?
  7. I think, theres another update for Crashplan available.... maybe you can look into that...
  8. Here you Can login https://www.crashplanpro.com/login/#/login?to=%2Fconsole%2F You can set up everything there, including the folders to backup, witch time etc... It is a bit slower but it works fine and is maintained by Code42. I’m using it and it works perfectly, so I can leave the blank white docker behind Gesendet von iPhone mit Tapatalk Pro
  9. I would say... every resolution... from the basic one with wich the docker comes to better ones like 1920x1080 It's like the one before me postet... Dropdown Menu and everything is white... had this problems with the version before the last update also Edit: Just found out... if I log in on the Code42 web page and visit the admin console I can adjust all the same settings easily withouth having the troubles of the white site behaviour of the docker container... so I just can leave the container web ui as it is and I can live with this solution and every thing is fine... for me
  10. Hi Guys! Thanks for making this Docker available to us, love it so far, and works quiet well. Tried out Duplicati before, but it has too much problems I think. Starts Backup, but stops after 1 TB, keeps showing errors in database (no rep is helping) etc But, there is a thing, that doesn't work very well for me... When I change the resolution of the Crashplan Docker, I get more often a blank white screen if I would like to change something in the settings, especially if there is a drop down menu. If I set the resolution back to 1280 x 768 it gets better, but still this happens sometimes. If this is the case, I have to restart the container otherwise I can't use it because its all blank. Is there a solution for this? Also found out, if I let crashplan detect and set the language it is getting worse... So I changed it from auto to english, I can deal with that point...
  11. Saw some of his videos already. This was very helpful at the beginning. Test box was only to learn so I can start a Real server
  12. Supermicro X11SPL-f xeon Silver 4110 32 GB ECC Ram 5x4 TB Ironwolf and 2 TB Ironwolf for Time Machine 2x240 GB SSD for Cache Test Box was an old HP DC7800 and was limited by 3 SATA Connectors. The new pinning function seems to be great. On the test box I had 6.5.3 until it broke
  13. Thanks this was a really useful explanation. Now I see this stuff much clearer starting my unraid server tomorrow. Can’t wait for it. Only had a test box so far, but it broke a few weeks ago