Nodiaque

I think the parity rebuild interfere with the diagnostic

well, the tab crashed, no diagnostic available...

It's been scanning my jellyfin folder (well, it says it's scanning /mnt/cache/appdata but that folder is empty) for the past 30 minutes and still doing it. I don't think it's right.... edit: an hour later, still no diagnostic yet, it's still scanning appdata....

Everything was disabled before moving (vm, lxc, vm). I'm wondering if I corrupted my docker subsystem. Haven't started the vm yet, I'm waiting for the parity to be restored first. I'm running the diagnostic right now but is it normal that it's scanning these files? Like my whole appdata folder. edit: what I don't get is that /mnt/cache is empty so what is it scanning. Appdata is currently under /mnt/user/appdata on the array, not on the cache.

Hello everyone, I'm currently setting multiple cache/pool and I think I did something per mistake and I'm looking at the info. Right now, I'm moving most of the stuff that were on my "cache" to a new pool. Thing is when I moved the file from the cache to the pool, it got from 352gb to nearly 700gb. Weird thing is I don't even have move my appdata yet which is the 300gb. This is what I have set to be on the cache pool: - Appdata - domains - lxc - mcron - syslog - system I have already moved everything except appdata. Appdata is on the array currently (dockers, vm, lxc are all shutdown and disabled). System is the one that's about 650gb by itself. I'm wondering if system was on the cache or not but looking at the docker configuration, it says /mnt/user/system/docker should be on the ssd so I'm pretty sure it was. But is it possible not everything from /mnt/user/system was on the cache? Or maybe before it was /mnt/cache/system and I changed it somewhere in the past? Thus this post is to get the default value of these share normally or the configuration so I can find out where's the problem thank you edit: I'm currently rebuilding my parity (error which invalidated my parity disk) and I see that the folder /mnt/user/system/docker/btrfs is gaining in size non stop. It seems the 600gb+ is coming from there. But docker is currently disabled...

Ah great to know, thank you!

Hello everyone, I have a drive and pool configuration as follow: Array 7 hdd Cache pool raid 1 2x ssd cacheappdata pool raid 1 2x ssd cachedownload 1x ssd cachetemp 1x ssd cameras 1x hdd downloads 1x hdd My goal was to have thing setup as follow Everything that belong to the array goes by the cache first except appdata, which goes on cacheappdata. Thus, in share configuration, I set primary storage as cache/cacheappdata and secondary as array. Good. Now, I would like to do the samething with my downloads. I want primary storage to be cachedownload and secondary to be downloads, but under secondary, the only thing I can select is array. Is it possible to have secondary as any other pool? Thank you

Summary: Support Thread for Nodiaque EVCC Docker - Official Docker Image Application: EVCC DockerHub: https://github.com/evcc-io/evcc This is only an unraid template for the official EVCC docker. For problem with the app itself, highly suggest going to the project github.

that mean recreating manually each docker? Ouf, that's going to be long. I guess restoring from appdata backup/restore plugin not a good idea?

could use userscript plugins to do that

Hello, I'm having a hard time with the pre-backup script. I created a small one that create an sql dump of my mariadb. If I run the script from cmd, no problem. But when I run from prebackup, the filename are weird. Script: now=$(date +"%Y-%m-%d_%H:%M:%S") docker exec mariadb sh -c 'exec mariadb-dump --all-databases -uroot -p"password"' > /mnt/user/Backup/mariadb/mariadb_$now.sql now=$(date +"%Y-%m-%d_%H:%M:%S") docker exec mariadb-nextcloud sh -c 'exec mariadb-dump --all-databases -uroot -p"password"' > /mnt/user/Backup/mariadb/mariadb-nextcloud_$now.sql The result: I don't get where these filename come from. The content is good, but its not how I named them. Thank you

another easy way is to set this as a user script (using user script plugin) that run "sysctl "vm.overcommit_memory=1"" at the first run of the array.

I had the problem when it was an image file, was recreated as a folder to see if it would remove the problem.

was wondering if you had any idea with these information or something else I can do to continue the diagnostic?

Hello, I was wondering if someone was able to have telegraf working with pihole v6 api? I don't get how to fetch data with the new api. Thank you!

Oh didn't know about nebula sync. I'll check that. Thanks.

It seems with pihole v6, this doesn't work properly anymore. Sync result in database corruption on the receivers end and the password is also overwrite.

Hello, Enshrouded is known to have these kind of issue. You can try either the proton or non proton container. Some have better performance with one VS the other. It is only something you can see with the official dev themself unfortunately.

Here's the diagnostic. I just reproduce the problem with fileflow container. That's what I get on the gui servraid-diagnostics-20250220-1102.zip

Hello, I have this problem since a long time. Most docker I have, when I press stop or restart, it timeout with an error on the gui saying an unexpected error appeared. The docker do stop. If I use docker cli, the docker stop nearly instantly. I have the same docker with same configuration on another server and they stop/restart without a problem so I know it's not the docker image. I get this problem even with new docker. The problem also appear when updating, it timeout while trying to close the docker before replacing it. I tried recreating the docker environnement, I even moved to directory instead of docker image and still the same problem. Thank you

By the look of it, you got corrupt file. Are you already running other container with steam? If not, try deleting the container and both appdata folder, do a cold start without any data. Once it's up (it does take a while to download everything and start), shutdown and edit the config file.

Hello, The docker itself doesn't try to create or erase anything. When that happen, it's usually a corruption in the data. The game itself manage everything. The backup is a simple file compression of the data Dir. You can simply extract and overwrite the content. Using a file extractor, you can see the content and see where it goes. I highly suggest the plugin appdata backup restore which backup the whole appdata folder and provide even better backup.

I didn't know that Linux Io left unraid. That's new to me considering the amount of app I see from them still being release in ca

AH, ok. I do like having it on the side, allow for better db backup