1444 posts in this topic Last Reply December 16, 2017

Recommended Posts

I have tried everything others have done after trawling through this thread to get rid of the black screen issue and have completely started again (full re-install of unRAID) also on 6.2.2 hope he can fix it as I have not backed up for weeks!

Regarding the black screen problem... I personally don't have a black screen, but when I view the CP interface via the web it does freeze. I just use a different VNC client on port 4239 and it works great.

Regarding the black screen problem... I personally don't have a black screen, but when I view the CP interface via the web it does freeze. I just use a different VNC client on port 4239 and it works great.

Awesome! This worked. I never made the initial change to the conf file, so my assumption is that the timing with the unRAID upgrade was purely coincidental, and I just needed more RAM allocated in the first place.

Share this post

Link to post

After migrating from running CrashPlan on my Windows machine to running it on unRAID (thanks for the great docker!), I've got my server fully backed up to the cloud.

I'm now attempting to get other people's backups to me running, and I have 2 questions:

1) I want to confirm that I'm not backing up to my docker.img file again. I had issues with this before, even though I though everything was good.

Attachment 1 shows how I've got the docker configured

Attachment 2 shows the default backup location

Attachment 3 shows where that location is

Attachment 4 shows what's already on disk at that location. (The previous CP backup folders. Don't know if the numbers are globally meaningful, so I obfuscated).

Based on the 4th image, it appears to me that the mapping is correct, but, then, I'm pretty sure this is what it looked like previously...

Do these settings look correct to get the backup onto my protected array instead of into the docker.img?

2) I've run into some difficulty getting difficulty getting the incoming connections to work

I installed the CP docker with all the default port usage - it's listening on 4242.

I've got 4242 being forwarded for both TCP & UDP to my server.

I was on Skype with my daughter, and her setup looks to me to be correct, she's got my backup code entered, but it says it cannot connect.

We ran through these steps from Code42 for debugging the issue, and everything seems to be working. The only issue that I can't 100% confirm is AV software on her machine - she's running a Mac and I just don't know much about them.

She had a backup running to my machine previously when the backup engine was running on my Win7 machine (with it following hard links to the server. Yay!), so I know the software was working previously.

She did just update the CP client to the latest on her laptop, but I would presume that wouldn't break anything...

Any suggestions on what else to check to figure out why she can't get connected?

I will be working with my son (on Win7) tomorrow night, so I'll have another data point to see what's going on.

I'm pretty sure that I had incoming connections working previously, but had the docker configured incorrectly - it was filling my docker.img file almost instantly. I don't know if it was her machine or one of the several other family members who backup to my server who was making the connection, though.

Share this post

Link to post

I have stopped the Crashplan docker until this get fixed. It's generating a lot of stress and heat on the HDDs and CPU because it's constantly restarting a scan over the same files again and again . Does it has something to do with the Crashplan 4.8.0 release maybe?

My Crashplan docker's log is plagued with the same error repeating constantly:

Share this post

Link to post

Just in case anyone is interested, although I would prefer to use a docker, due to so many problems with Black Screens & random failures I now run Crashplan on my Windows 7 VM and it works perfectly backing up all my shares.

Please note this is not meant to be derogatory in any way but just to let people know of an alternative that works well.

Thanks for the idea! Yes, it seems it was that! After adding more RAM to Crashplan it seems to work fine again! Thank you!!

My pleasure, I've got 10+ years of DSLR photos covering several TB and I hit the Java memory thing long ago (actually before migrating over to docker).

I gave mine 4gb of ram and nothing I still get the same error as I did before.

Not wanting to be THAT guy but have you tried removing the container and the appdata files and just starting the config from scratch? you can adopt the old PC from the cloud and it will pick up from where it left off so it not a total loss (again you probably knew but I was just covering bases)

Share this post

Link to post

I do not BELIEVE so Squid. By default, CP is optimized for 1TB or 1 Million files. A user needs to manual up this amount at essentially 1 MB / 1TB OR 1M Files to be backed up. if the container is 32 GB (not certain if it is or not)... 1.5-2 is about the max.