chrissi5120

Hi, where shall we find the "new one"? for me, it is only showing the "old one"

Thank you for your reply, I could have been more specific with my description, of course i already tried to restart that service: root@storageserver:~# /etc/rc.d/rc.flash_backup start root@storageserver:~# /etc/rc.d/rc.flash_backup status flash backup monitor is running. system is signed in to Unraid.net. sadly, this does not change anything, pressing update also does nothing.

Hello Team! report: <-----UNRAID-API-REPORT-----> SERVER_NAME: storageserver ENVIRONMENT: production UNRAID_VERSION: 6.10.3 UNRAID_API_VERSION: 2.49.2 (running) NODE_VERSION: v14.15.3 API_KEY: valid MY_SERVERS: authenticated MY_SERVERS_USERNAME: chrissi5120 CLOUD: ok [IP=52.40.54.163] RELAY: connected MINI-GRAPH: connected ONLINE_SERVERS: storageserver[owner="chrissi5120"] OFFLINE_SERVERS: ALLOWED_ORIGINS: http://localhost:8008, http://IPV4ADDRESS:8008, https://IPV4ADDRESS:8543, http://storageserver:8008, https://storageserver:8543, http://storageserver.local:8008, https://storageserver.local:8543 HAS_CRASH_LOGS: no </----UNRAID-API-REPORT-----> flash_backup script: root@storageserver:~# /etc/rc.d/rc.flash_backup status flash backup is enabled but the monitor is not running. system is signed in to Unraid.net. restarting unraid-api does nothing: Aug 27 19:59:14 storageserver unraid-api[19764]: 👋 Farewell. UNRAID API shutting down! Aug 27 19:59:17 storageserver unraid-api[3265]: ✔️ UNRAID API started successfully! ping: root@storageserver:~# ping backup.unraid.net PING backup.unraid.net (54.213.198.207) 56(84) bytes of data. ^C --- backup.unraid.net ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2041ms Status Page:

Thank you for sharing your reasoning behind that build. I totally get your point, running the newer chipset and keeping sas slots available is also a nice upside in my eyes.. Your case is pretty hard to come by in Germany, I would really love to see a comparable offer with an integrated sas expander, all the cases i can find require at least two connections to even run the backplanes.. they are also not exactly cheap.. ah man.. hard choices..

This is an incredible build. I will propably copy-cat a lot of things from you One question: this case you are using has an SAS Expander with the 8643 expander.. couldnt you go for a mainboard like this: THIS and save some money on the HBA card? Maybe i am missing something and this board controllers are horrible?

This is a little offtopic but still relevant to the issues with 12th gen CPU's: What would be a solid alternative to the performance level of an 12600k in your eyes right now? As this thread suggests, it is still highly problematic to run this generation CPU's with unraid.. Where would you go instead? Lets just pretend someone really needs to upgrade this Month, no way around relevant factors: - power consumption (Germany, energy is getting unaffordable) - price / performance I am coming from a 10 year old quad core xeon setup with ECC Memory, but it would not be necessary to go for ECC at that point for me tbh. Setup could be Intel or AMD, as long as it is stable, i do not care either. I also do not care for Hardware Transcoding, as long as the CPU can handle one 4k HDR Transcode just fine. IGPU optional, onboard graphics would also be okay.. maybe this is the solution? just disable the IGPU entirely for now? Is it stable without the IGPU usage?

Thank you for your feedback! i opted for midnight commander (command is "mc", its preinstalled), INSIDE a screen session. after thoroughly reading into fuse between containers, i realized, that there is absolutely no "plug and play" way to achive this. This would all need scary permissions and people seem to have actual problems with it even if it is running. midnight commander seems to be the solution for quick copy and paste operations as it is easier on the eye when dealing with spaces in file-/foldernames when i would need to restore a complete volume, i would certainly opt for something like a rsync with recursive search etc. activated. tl;dr: FUSE sucks if you want to move stuff between containers and the host-OS, better use something on the host-shell.

Hi Guys, my Backup just finished for the first Time Next, I wanted to restore some files with the help of the /mnt/borg:/mnt/fuse mountpoint. To have a GUI which I can “fire and forget” a copy command, i tried to use double commander. Sadly, “double commander” is unable to even see the mount point while it is mounted due to not matching permissions.. Both, double commander and borg are started to UID/GID 99/100, but the borg mount command results in file permissions being root:root. I could probably circumvent this by running double commander in privileged mode with root UID/GID but i would rather not like to. Do you guys have this issue at all and/or how do you circumvent it? best regards Christoph

Also,the availability of this things seem to be fairly limited.. I can only find weird ebay listings

https://borgbackup.readthedocs.io/en/stable/usage/general.html#logging

a really generalistic question to your containers design and borg in general.. if i would add the appdata path to the config and restart, would he pick the new added path just like that or might i need to do someting else before?

are you sure, you deleted the old image? try docker image ls and then manually delete it to be sure.. if you get no success, make sure to stick as closely to the original example configuration without your comments, yaml is very picky regarding spaces and other invisible stuff. as soon as you get a different error, i would mark this as an success

thank you for your on-point suggestion i get stressed out by thinking about a solution to control the docker states from inside the borg container (hen-egg problem) for now, i will try to use the advanced option from CA-Backup: "Select which applications to NOT stop during a backup" i just selected borg there, in the files i also exclude the borg-cache folders contents. lets see how i will roll with that..

The error comes from inside the application itself, see line 5089 As this is a dockerized app, i would try to delete the image and pull it again from repository before investigating any deeper

Hi Guys, CA-Backup just killed the container before doing backups, this results in the following error after restart: summary: /etc/borgmatic.d/config.yaml: Error running configuration file ssh://<$SERVERNAME>/./backup/unraid: Error running actions for repository Failed to create/acquire the lock /root/.cache/borg/c78474a458bfb7cf00e996ef92a3db312fc845792a33306672041ae578876656/lock.exclusive (timeout). I could resolve it manually with running the following command inside the container: borg break-lock ssh://<$SERVERNAME>/./backup/unraid My problem is that this will occur everytime CA-Backup stops the docker containers. Is there are a proper way to AUTOMATICALLY mitigate this from inside borg? best regards Christoph