boomam

When the memory was installed - the system was running perfectly fine, no issues, for well over 300 days without reboot. RAM is running within spec of the motherboard/CPU documented limits, 2933Mhz, with a slight overvolt (0.01v) to cater to the 4x DIMM voltage drop - standard stuff. I am 100% certain it is not the memory - I'm well versed in Ryzen memory requirements/limitations....especially when it comes to the older Zen Architectures (its a 3200g). Anyway - reading around on what BTRFS errors mean, the "corruption" stat doesn't mean hardware problems (99% the time), it means corruption of data. IO errors are hardware issues 100% of the time, by comparison. With that in mind, the evidence would point to data issues, instead of hardware ones, despite the docker image data being hours old being a bit strange. Regardless, as extra steps/notes since last night - The second cache pool had racked up a extra errors every second (getting up to 8,700), however these stopped once the docker service was shutdown - a little strange. Following this, I shut the system down, re-seated all the SATA and power connections on the drive and motherboard, blew out the accumulated dust (not much in all fairness), then booted to UEFI, did a long awaited update, and booted into Unraid. Everything came up fine - no errors anywhere (btrfs status, sys log, btrfs scrub, etc.) other than on the main cache pool, where a few corrupted errors appeared whenever a specific VM did anything, with the scrub confirming just the same 2 errors each time. Checking dmesg's output, i was able to confirm that the specific VMs vhd had become corrupted. I deleted the affected vhd, restored the VM from an earlier backup, re-scrubbed the file system and got no further errors. Completing boot/reconfig of all my containers/VMs and leaving it overnight, no further errors anywhere that I can see. If it behaves itself between now and the end of the week, I'll likely shutdown completely and run another memtest and offline stress test since i updated the UEFI. Next step following this will be to work out the syntax to send notifications to the notification agents from CLI - i want to have a scheduled script that runs, checks if it can write to the cache drives or not (with not indicating its in 'read only' mode again - the original source of all this), and if so, pinging an alert. I'll report back any further findings regardless, for anyone elses future diagnosis.

Further testing, killing docker has stopped the errors accumulating. Created a dummy 40Gb file on the second cache, then copied it to the main cache - no new errors. This is very weird - the docker image files were freshly downloaded, hours ago!😶

Oh, thats wierd, my second cache (just docker images on it) has shot up from 0 to 1600+ in the last few mins!?

ok, now upto '8', following a backup of my VMs...not looking good...

Hi, I just finished restoring my apps/containers after my main cache drive decided to go read only - keeping an eye on BTRFS errors, with "btrfs dev stats /mnt/cache", i'm seeing that mere hours after restoration, the corruption errors on both disks in the pool is at '1' already. The two disks in the pool has no 'bad' smart results, showing % life remaining around 47-49%, nor any other errors. Is an error count of '1' anything to be worried about at this point? Or should I start looking at replacing the drives already? Thanks!

Hi, Is there a way to have Unraid recognize multi-network containers? Right now, if i add a second network to a container either through CLI or Portainer, it works, everything behaves, but if i ever change anything to do with the container in the GUI, it removes said network. Any way to avoid this? Equally, as a second question, is there a way to force dockerMan to rebuild a template it has? The "original" in there isn't storing my extra variables for some reason (on this one container). Thanks in advance!

Not sure if we report it here, but this is an incorrect alert: (cloudflare/cloudflared:latest) has the following comments: latest tag does not exist on dockerHub Additionally, this application has been blacklisted from Community Applications for that reason. There is now a latest tag available on ducker hub: https://hub.docker.com/r/cloudflare/cloudflared/tags

Is it possible to get the repo/image updated to the latest release please?

This is great. Nice and simple way to visualise the nginx logs.

Hi, Is there something wrong with the latest release of this container? Trying a new setup and it wont connect to the database whatsoever - equally, wiping out configs for databases from the config.yml still see's it trying to connect to a postgres database (which is very weird as nothing is specified). Is there some wierd gotcha with this container perhaps? Thanks.

Completely forgot about that advanced button. 😛 Thanks! that appears to have resolved it.

There are no extra parameters by default? Can you expand on your fix, in detail, please?

Hi, Happy new year everyone! I've been thinking the last few days about the amount of apps/containers/VM's/etc. that can put excess writes on a given cache drive in Unraid, and what the real solution to it is, beyond accepting a loss of a drive. To be clear, I am aware that this isn't an Unraid problem per-say (although the loop2 bug contributes, with its own workarounds), so I'm using Unraid here as an example as that's what I'm running at home. Lets use stats and analysis through Grafana as an example - Standard config, influx and Prometheus/similar pulling stats from fairly standard home-lab systems, like UniFi, Unraid, HomeAssistant, etc. All useful data that can help draw some pretty graphs - but not without adding more undue wear on a given SSD. How are people actually handling this long term? Accepting the loss of a SSD? Shipping the log writing off of Unraid to something else (and moving the problem there?)? HDD usage? Logging the databases to RAM where possible, flushing every hour or so? Something else? How are we all handling this problem? Thanks!

Anyone getting this error when trying to get Pydio-Cells running? Error response from daemon: pull access denied for pydio-cells, repository does not exist or may require 'docker login': denied: requested access to the resource is denied. See 'docker run --help'. Image seems to download, just the 'docker run' doesn't seem to want to finish.

32Gb. 4x 8Gb sticks. Originally had 2x 8Gb sticks, but then i upgraded my main system to PC3600/32Gb (2x16Gb), then my old 32Gb kit went to my other half, then her 16Gb (2x8Gb) of memory that was identical to the ones already in Unraid, went in, making 4x matching 8Gb sticks. 😛 Had to underclock them a little (2933 vs 3200) and give a little more voltage (+0.05v) to get stability, but touch wood its been running sweet as a nut. Hoping that a future upgrade to a 5700G will allow me to run them back at 3200 again.

As a quick & dirty fix: cd /mnt/user/XXXX (where XXXX is a share of yours) wget https://slackware.uk/slackware/slackware64-14.2/slackware64/l/ncurses-5.9-x86_64-4.txz upgradepkg --install-new ncurses-5.9-x86_64-4.txz Following this, iotop works again.

Same for me. Looking at the github repo, it looks like the plugin (NerdTools) may have been abandoned, which is a shame.

I'm interested in a write up of settings/etc. I thought i had it setup, but 4k transcoding seems to just...stop, unless i put it back to software transcoding.

Fairly good guide, but needs more content - you've fallen into the same trap that a lot of OSS guides fall into, and made some leaps of faith in wording and knowledge. To make this easier for people you should probably elaborate more on the below sections - to be clear, I am not asking for help myself, but for a more complete guide for others - ...In my case, I used /mnt/user/dmz/goaccess/log Why? Is DMZ a folder you've setup? If so, what does it store? Just these files, and is needed for this setup, etc.? There is a nifty script that does this mapping for you here... What does the script do? How and where is it ran? Is it a one time thing? or every time we want to see the logs? What is the effect on NPM? What are the manual steps? Now, open the file goaccess.conf again and comment out the line: Is there a reason why this isn't done in the earlier editing of the goacces.conf file? If so, why? Minor adjustments to an otherwise good guide. Thanks.

To clarify for people - you do not need multiple tunnels, nor a large config to proxy several subdomains through an argo tunnel. You can literally just have the config point at the IP/port of your proxy manager (NPN, SWAG, etc.) and add records for each subdomain in Cloudflare DNS as needed. The key however with the current argo version however is to turn TLS verify off in the config and set the SSL/TLS mode in Cloudflare to Full, otherwise there will be redirect issues.

...and its back. Hmm.

Portainer is free. https://www.portainer.io/products

Its not the flash drive. No errors elseware on the system, and its been functioning fine in the same port for over a year. Strangely, installing a different dynamix plugin seems to have resolved it, will keep an eye on it though.

Look into Portainer.

I've started getting lots of similar today as well, but in the plugins tab. Not found a solution yet...