-
blingbling1384 started following CrashPlan & CrashPlan GUI Merger Plugin , [Support] Djoss - CrashPlan , Powerdown package for unRAID v5 and v6 (DEPRECATED) and 1 other
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
FYI, updating unRAID to the latest version fixed this issue for me.
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
I'm having a problem where the clicking on the CrashPlan Docker and selecting WebUI still takes me to http://www.code42.com/crashplan/. I've edited the Advanced Settings as suggested, but I can't seem to get the new WebUI address to take effect. Any suggestions?
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
That’s because the CrashPlan Docker has auto updated itself to 4.4.1 and the CrashPlan Docker Desktop doesn’t. ok... so.... is there a fix? I, too, had this problem. Now, ever since I attempted to launch the Desktop Docker, the CrashPlan Docker itself isn't working either. It appears my backups are stalled. Have you figured out a way to get the backups working again, even though the Desktop Docker no longer works?
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
If the CrashPlan Desktop Docker is unable to connect something must have happened with the CrashPlan Docker. I assume it is running, can something changed your config folder, where is the config folder stored, if it is on the cache drive can it have been moved/changed? You might have a look on the Guide in my signature to see if that can help. The CrashPlan Docker was running. I didn't change anything in my config folder. The config is stored on the cache drive. Nothing was moved/changed. Is it recommended to stop the Dockers before stopping the array? That is the only thing I can think of that may have corrupted something. I just removed both CrashPlan dockers, disabled Docker in my settings, deleted the docker.img file from my cache disk, re-enabled Docker in settings, Re-added both CrashPlan Docker containers. Now the CrashPlan GUI is working again through Remote Desktop. Thanks!
-
[CONTAINER] CrashPlan & CrashPlan-Desktop
Just upgraded my unRAID to v6 today. I then installed the CrashPlan & CrashPlan - Desktop containers. After initial install of both containers, I was able to use Remote Desktop to connect to the Desktop container on port 3389. The Desktop app launched without issue, and I was able to change backup settings. Since then, I unmounted my array to do some testing, then re-mounted the array. Now when using Remote Desktop to connect to the Desktop container, CrashPlan will not launch. It gives an error on the splash screen "Unable to connect to the backup engine, retry?" I've removed both containers and images and re-added them fresh. I also tried rebooting unRAID. Not sure what changed that caused the Desktop app to stop working. Any advice? I'm very much an unRAID novice, so there's nothing fancy in my config. With v5 I just set it and forget it. Haven't done much with v6 since the upgrade besides adding CrashPlan Dockers. Thanks!
-
cache_dirs - an attempt to keep directory entries in RAM to prevent disk spin-up
My understanding was that cache_dirs was supposed to cache the directory information so that the disks did not need to spin up while simply traversing the directory structure. Is this not the case? I can see in the syslog that cache_dirs runs without errors upon startup, but the disks still spin up when I'm browsing through directories (not accessing files).
blingbling1384
Members
-
Joined
-
Last visited