AlexB108

Fantastic, thanks for the tip, I will swap them over and see if I get the same issue!

I am having a weird problem where my 14tb WD disk (WDC_WD140EDFZ-11A0VA0_9KH23VWL in the diagnostics) will become unmountable while the array is up. I have had it happen a couple of times, and each time stopping the array, starting the array in maintenance mode, then running: xfs_repair -L -v on the drive fixes the problem for a while, before it then happens again. I had thought it was a bad SATA cable (had the problem every day or so), so replaced that and I had assumed that had fixed it as the problem went away for a few weeks, but it has started happening again over this week. I have run extended SMART test, and getting no errors. The warranty for the drive runs out in Jan, so trying to work out if it is a drive problem, or if something else I am running is causing it. I have run the above command and moved all data off the drive since the last time it did it, just incase there is a drive problem (I also know that I should be running a parity drive, but I set it up without one during testing and never got round to installing one - may repurpose this drive if it isn't on its way out). Any help would be appreciated! Alex tower-diagnostics-20220917-1045.zip

Hey guys, Loving the netdata container and having fun playing with it. Currently trying to get the back end configuration for getting data into influxdb, so I can talk myself into out of buying a new CPU by having data to back up my hypothesis I am smashing my CPU. I have got the netdata.conf file from http://{localhost}:19999/netdata.conf and edited it to contain the following: [backend] # host tags = enabled = yes data source = average type = graphite destination = udp:10.0.0.2:8086 prefix = netdata hostname = Tower # update every = 10 # buffer on failures = 10 # timeout ms = 20000 # send names instead of ids = yes # send charts matching = * # send hosts matching = localhost * I then saved this to /mnt/cache/appdata/netdata/netdata.conf (which is what I have mapped to /etc/netdata/override), and restarted the container. However it doesn't seem to be picked up, and when I then do http://{localhost}:19999/netdata.conf again, it is set to the defaults. I have a feeling that I am missing something stupid, but for the life of me I can't work it out. I have tried remapping /etc/netdata/override to a different location, as well as using vim to create the file rather than saving it locally and then dropping it into /mnt/cache/appdata/netdata/ location. Any help would be greatly appreciated! Thanks, Alex