Aceriz

SO to round this out so that future people will know how to solve if similar issue, 1. Install Borgmatic a. with the cache host path directed at "/nextcloud_aio_backup_cache/_data/" b. With the Repro drive host path pointed at the correct path Then docker exec -it borgmatic bash then borg break-lock /mnt/borg-repository sudo docker rm nextcloud-aio-borgbackup sudo docker volume rm nextcloud_aio_backup_cache Then reset the master docker and run the backup

from within Terminal when I inspect the folders either the original or the rsync files I do see the file "Lock.roster" and folder "lock.exclusive." when I navigate to the "/var/lib/docker/volumes/nextcloud_aio_backup_cache/_data" there is no files here... is there a way to manually delete the lock ? or replace the lock in the cache file ?

So I was able to install another instance of Borgmatic from within Unraid that stays active .... However I am having difficulty with executing the Borg Break-lock command from within Nextcloud the directory is located at " /mnt/user/Backups/nextcloudaio\ Backup/borg " when I navigate through terminal I see that it is located at "/mnt/user/Backups/nextcloudaio\\\ Backup/borg " When I attempt to run this command docker exec -it borgmatic borg break-lock /mnt/user/Backups/nextcloudaio\\\ Backup/borg I received an error stating " Repository /mnt/user/Backups/nextcloudaio\ Backup/borg does not exist. " In an attempt to help with problemsolving in case the "\\\" or " (space) before Backup" caused issues I did an rsync to a new directory "mnt/user/Backups/BORG-Nextcloudaio/borg " which was successful at copying all the files over on this new directory I still get the error "Repository /var/lib/docker/volumes/nextcloud_aio_backup_cache/_data does not exist"

Okay so I have made some progress where I am decided to just go with the above. This now has the nextcloudaio Mastercontainer starting up. But when I try to run the backup I am getting error ===> Failed to create/acquire the lock /root/.cache/borg/xxxxxxxxxx.lock.exclusive " Failed to create/acquire the lock" and point to a lock.exclusive file in my backup folder. Steps to replicate it: Manually start a backup Additional Info: This started after the above crash that occurred when trying to do the last update for the master container which failed. From within the Mastercontainer Interface I can run the check backup integrity command. Which comes back clean without reported errors. From what I can find it looks like I need to run the borg break-lock Command https://borgbackup.readthedocs.io/en/stable/usage/lock.html#borg-break-lock I can not seem to figure out how to run this in unraid.. as the "nextcloud-aio-borgbackup" docker closes immediately after about 2 second when I attempt to run the backup so not enough time to activate anything... Nor do I really know what the command would be.. is it borg -v break-lock /mnt/user/Backups/nextcloudaio\ Backup/borg ? thanks for help

Hello All, I am hoping to just get some help with my install of nextcloudAIO . Thought it would be best to start a new topic rather than hyjack the old topic that way I can get the collective wisdom to help rather than just rely on the generosity of @szaimen. Have been able to get fairly far I think in solving. everything in my NC -AIO was running until I attempted an update to the master container (through the UI ). Right now I can not load my AIO and am ideally not wanting to do a full re-install as original poster did If I can avoid this. After the update I got the error below showing up in the LOG file for the master container. Trying to fix docker.sock permissions internally... Creating docker group internally with id 281 It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? In a previous posting helping someone else @szaimen indicated that for a similar error ==>"Please change -v /mnt/user/appdata/nextcloud-aio:/mnt/docker-aio-config:rw to -v nextcloud_aio_mastercontainer:/mnt/docker-aio-config:rw " Runninng the command "sudo find /var/lib/docker/volumes -name configuration.json " generates the below /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data/configuration.json @szaimen Had indicated I apologize if it seems like a stupid question but as I am new to Linux I wanted to make sure I understand before I attempt and screw things up further. After much looking online I think for the rsync command suggested I would put in the below in terminal correct ?? rsync -av /mnt/user/appdata/nextcloudaio/ /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/ THEN would I have to go into the NC-Master Container template and change the configuration to read at HOST line to: "/var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/ " Would I keep the "_data" or should it be without it? If it is helpful to post the sudo docker inspect nextcloud-aio-mastercontainer please let me know I appreciate the collective wisdom in what is likely hopefully a simple fix and me just wanting to be cautious before I bork things further lol

sorry if this is a very stupid question but when you say "rsync" the data how would I go about doing that? and when you say with the correct command are you talking about changing the line in the edit configuration at "host path " so that that would read "/var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data" Sorry again in stupid questions...

Runninng the command "sudo find /var/lib/docker/volumes -name configuration.json " generates the below /var/lib/docker/volumes/nextcloud_aio_mastercontainer/_data/data/configuration.json

how did you go about the change . ..

It is something that I would change here ?

Hello Sorry for also hyjacking, everything in my NC -AIO was running until I attempted an update then I also got the error below ==> Trying to fix docker.sock permissions internally... Creating docker group internally with id 281 It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? This is not supported since the built-in backup solution will not work in that case! It seems like you did not attach the 'nextcloud_aio_mastercontainer' volume to the mastercontainer? When you indicate the "Please change -v /mnt/user/appdata/nextcloud-aio:/mnt/docker-aio-config:rw to -v nextcloud_aio_mastercontainer:/mnt/docker-aio-config:rw " how would I go about doing this change ?? Right now I can not load my AIO and am ideally not wanting to do a full re-install as original poster did If I can avoid this. Do I have to change something in the Master Docker Container edit space (below)? or in terminal window. ? If you want me to post my sudo docker inspect nextcloud-aio-mastercontainer am happy to just let me know

I am wondering So if I run in just the regular Unraid boot option that is without the GUI I do land with a command line that appears to allow me to enter username and password in a regular command line. is there a way to initiate a clean shutdown from this. I ask because essentially if I am able to do this without much issue then I might just forgo the UnraidGUI boot. As I do not do much within the built-in GUI on the tower apart from initiating a shutdown once I turn off the VM.

Sorry if there has been confusion when I am talking about he UnraidGUI. I am mentioning the GUI that can be accessed directly from the server when you have a monitor connected to the server directly and the flash is selected to the "unRAID OS GUI Mode" it gives the firefox browser etc.. I have it setup that my system autoboots a VM directly from the PC using my graphics card, then with the onboard from the motherboard I have access to the GUI. I have it setup this way so that when I turn off the VM i have a means to turn off the server etc without leaving the computer or needing to access from other computer

To provide a bit of clarity yes I am using VMs, and have been throughout both on 6.9.2 and even when I log into safemode6.11.1 GUI and the unraidGUI screen works even with using VMs in safe mode Interns of wiring I have my motherboard set to assign my onboard graphics to unraid. then my monitor has two inputs (D-Sub for the GUI from the onboard, and Displayport from my graphics card) Hopefully this makes sense

Hey, So thought I would provide an update see if you have any thoughts about how to problem solve what is now my last issue. As I have now solved the NPM issue, as well as the NextcloudAIO issue. So currently my last issue is : when I restart Unraid 6.11.1 in GUI mode. I am not able to see the Unraid GUI login screen or anything. All that I see is a flashing line in the top Left corner. I am not able to type anything. When I have reset in 6.11.1 Safemode-GUI the GUI does appear to work. In troubleshooting this I attached the diagnostics from Safemode and non safemode 6.11.1 above. What would be the best way to identify why this is occurring? is it to delete progressively each plugin one at a time ?

So as I continue to trouble shoot. What I have done so far. For the Unraid GUI -- I have tried to delete a number of plugins that I thought perhaps might be causing problem. (nvidia, nvidia info, and i dynamix active streams (since its version listed was not recent). this did not appear to fix the unraid GUI issue for the NextcloudAIO issue I think I might have honed in a bit on what might be causing issue. was able to find the following error in a separate log file Configuring Redis as session handler... Setting php max children... The www-data user doesn't seem to have access rights in the datadir. Did you maybe change the datadir and did forget to apply the correct permissions? See https://github.com/nextcloud/all-in-one#how-to-change-the-default-location-of-nextclouds-datadir The found permissions are: 99:100 770 (userID:groupID permissions) but they should be: 33:0 750 (userID:groupID permissions) for the "datadir" I had in the unraid Docker Edit directed this to a share on unraid called "NextcloudAIO" How would I go about changing this in unraid