cnbx8

Members
  • Posts

    3
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

cnbx8's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi, I hope everyone is doing well! I have two data disks that are formatted with "xfs encrypted" and contains data. My previous motherboard isn't working anymore so I have to build a new one. For some reason, the USB stick I used with the previous build is not working with the new build so I have to create a new unraid USB disk. I copied my /config from the old USB stick into the new USB stick and booted successfully. Now when I tried to add the two encrypted data disks, I am being asked to enter new a new key. I have used a passphrase key with the two data disks previously. Now here are my problems: Why am I being asked to enter a new key? If I enter a new key, would I still be able to access the files within the two data disks or data would be lost? What's the best way to add existing encrypted data disks into new unraid server without losing data? Thanks for the help!!!
  2. I have observed the same thing with my setup. Below is what I have observed: 1. Just right after starting the CrashPlan docker, cache is still pointing to /config/cache lrwxrwxrwx 1 root root 11 Sep 10 09:08 bin -> /config/bin lrwxrwxrwx 1 root root 13 Sep 10 09:08 cache -> /config/cache lrwxrwxrwx 1 root root 12 Sep 10 09:08 conf -> /config/conf drwxrwxrwx 1 nobody root 82 Apr 29 21:22 doc 2. After a few seconds, cache is not pointing to /config/cache anymore lrwxrwxrwx 1 root root 11 Sep 10 09:08 bin -> /config/bin drwxrwxrwx 1 root root 578 Sep 10 09:09 cache lrwxrwxrwx 1 root root 12 Sep 10 09:08 conf -> /config/conf drwxrwxr-x 1 root root 82 Sep 10 09:09 doc Because of this, everytime I restart my CrashPlan docker, it would scan files and synchronise. Has anyone resolved this? Thanks
  3. For me, these are two reasons why my docker.img size was growing rapidly: [*]For some reason in the gfjardim/crashplan docker the /usr/local/crashplan/cache is not linked (i.e. symbolic link) to /config/cache thus is using space within the docker.img. I restarted this docker and the issue was resolved [*]I have a local crashplan backup folder destination that I missed to map to my host folder. After I mapped this folder destination to a host folder, my docker image stopped growing. Thanks to hashi for providing the commands below which allowed me to pinpoint the culprit: [*]docker exec -it <container name> bash [*]find / -xdev -type f -size +100M