dv310p3r

Oh, dang, I hadn't realized that, thank you. I'll note that for future issues. As a note, I solved it by switching to a different Nginx Proxy Manager. I have to redo the proxy hosts, etc. But at least the container works.

GPT is right. I created a sqlite file with the name expected from what was in the production.json file in the root of the NginxProxyManager directory and it tried to start but there was no migration table (of course since i created an empty db). So, for some reason no matter what I do it's not making the necessary sqlite table?

GPT seems to think that I'm supposed to have a sqlite database in a data folder within the NginxProxyManager folder inside of appdata, which I don't. So it's saying that since I'm missing that it's not working. But I can't recall if it's supposed to have one or not, and if not... why?

This seems to be the only error I can see in the logs. Just a SIGBUS. GPT seems to think it's some kind of faulty file or hardware, which doesn't make a lot of sense considering I've got a dozen other conatiners running on the same hardware no issues, all using the same pool for appdata, no issues. And I've moved the appdata folder, reinstalled container, etc... and still getting the same issue.

My Nginx Proxy Manager had been working fine for years, no issues. Recently it stopped and I can't start it back up again. Rather, I start it, and then it looks like it's started but then it stops. I can't figure out what's wrong. I've tried removing and readding the container, deleting the image, moving the appdata folder to see if it was configs of somekind. i'm at a loss. I'm on 7.1.4, but I only updated today thinking that that was causing it, I was on 7.0.0 when I noticed the issue and since updating, same thing.

OMFG TY sreknob! That did it. Man... what a mission.

I've copied the borg package found here https://github.com/shinji257/unraid_pkgs/tree/main/slackware64-current/borgbackup into my /boot/extra directory, and then run installpkg borgbackup-1.4.0-x86_64-2_s257.tgz It says that it installed the package Verifying package borgbackup-1.4.0-x86_64-2_s257.tgz. Installing package borgbackup-1.4.0-x86_64-2_s257.tgz: PACKAGE DESCRIPTION: # borgbackup (deduplicating backup program) # # BorgBackup (short: Borg) is a deduplicating backup program. # Optionally, it supports compression and authenticated encryption. # The main goal of Borg is to provide an efficient and secure way # to backup data. The data deduplication technique used makes Borg # suitable for daily backups since only changes are stored. The # authenticated encryption technique makes it suitable for backups # to not fully trusted targets. # Homepage: https://borgbackup.readthedocs.io/ # This package was built WITHOUT the HTML documentation. Package borgbackup-1.4.0-x86_64-2_s257.tgz installed. But when I run the borg command, I get -bash: /usr/bin/borg: cannot execute: required file not found

NGL I'm super confused and honestly upset. I've been an unraid user for almost a decade now. I love it. This is probably the first time I'm super upset at them for this. I have a simple use case for NerdTools, specifically borg. I have a share on my unraid that holds borg backups from several computers in my home. That's it. It worked great. I have commands on each computer to regularly check those backups, mount them, check files, and just generally be sure that it's working fine. All stuff that honestly took me some time to set up. Now I'm being told, redo all that and use a container for borg. I kind of tried, but it's a damn mess. I have everything already set up. My repo, my keys, everything. I just want borg to work as a local command on unraid. I'm trying to follow the thread to make this happen, but I can't. I'm advanced enough of a user that I'd like to use un-get to install borg, but the directions above, just don't work. Any assistance would be helpful. Thanks,

So, after a second reboot everything seems to be working fine. Not sure what it is. I think the only thing I've changed prior to the problem was the Netdata app / container. I had it running for a few days no issues, so I'm not sure that's it. But I did remove it between freezes, and it's been up sicne then. Thanks for the help.

Attached. syslog

Yep, i can get that. Should I upload it here, or should I parse / clean out any identifiable information first? I would guess that's what the diagnostics command does, but don't know for sure.

Should the diagnostics collection take long? It's been running for about 10 minutes, and nothing has been created yet. I can access the logs myself and share if needed, I'd just need to know which ones to share.

I'm not sure what's happening. And I can't say what may have triggered it. Yesterday morning everything was fine and then in the evening my server wasn't working. I could still SSH into and I could still see the shares, but the WebUI wasn't working any longer. Oddly, some containerrs still seem to eb running while others are not, like plex for example. I'm at a loss for what to do next? Please help.

Ok, yeah. So, somehow what's being shown in the frontend, and what the config file are for the shares are different. When I make a slight change, like the description and then apply with it's current setting, the config file for the share then accurately reflects what's on the UI. So, i guess my next question would be, if the UI is not reflecting what's in the config file, which is reflecting how unraid behaves. Is it whatever is in the UI or is it whatever is in the config file for the share. My gut says config, but what would be odd about that is that I have seen files move onto the array and not into the cache. So I'm not sure.

Could there be some kind of issue with configs after upgrading? Or, am I missing something? When I go into the Shares, they are not configured to use a pool, as far as I can tell, below are some screenshots of some of the shares. Also, where can I find the flash drive to remove those files you mentioned? I do most of my file management via ssh and using midnight commander. Edited: found the /boot/ folder... Thanks,