milouz

May I ask you what is the prupose of using mergerfs on unraid?

is there any news on that? What can I do to make the plugin automatically calculate hash for new files that where moved by the mover from cache to array? is it possible to make the plugin calculate hash for file even if it is on cache and not on the array? I discovered that I have a lot of files without blake3 hashes despite '"Automatically protect new and modified files" option is enabled.

Thanks for your help. I'll try to ask tailscale also. nas-diagnostics-20230609-2323.zip

My logs are full of this kind of line: Jun 9 15:47:12 NAS tailscaled: 2023/06/09 15:47:07 wg: [rNaiD] - Failed to send handshake initiation: peer's node key has expired all my devices on my tailscale network have valid key and my unRAID server has Expiry disabled what does these errors mean?

Hi @binhex, I made my own docker image in order to get btrfs snapshot working corectly, it seems you need the user to run urbacksrv to be urbackup, ie do not change USER="urbackup" at the end of /etc/default/urbackupsrv, instead I use entrypoint.sh for re-writing uid and gid to map urbackup and nobody. feel free to give it a try if you want. entrypoint.sh Dockerfile

@binhex similar problem here using mullvad and 4.4.5-2-01. resolve by using 4.4.5-1-01 instead.

Hi! I'm facing a strange issue. in fact, i have a custom docker network supporting ipv6. radarr, sonarr and others are able to talk to each other using container name instead of ip, but binhex-qbittorrentvpn is unreachable. ping binhex-qbittorrentvpn from radarr and sonarr give me Addresse unreachable, unless I explicitly ask for ipv4 ping. even stranger, ping work briefly when I restart qbittorrent container... Any advise?

I never saw any spin up in the log, and I was taking care to not make any action in unraid and plugins were disabled to avoid any activity.

So, I ordered a new PSU, and it seems it was the cause of the problem. I really do not understand why reboot was occuring only while all disk spin down and never at any other moment, but since I changed the PSU the problem disapeared. At least, if this thread help somone else later, it'll be great. Thanks all for your help.

but why the PSU would cause reboot only when all disks spin down? weird no?

Nop, no UPS, the server is directly plugged to the electrical outlet

up.

Just made few new tests, it seems that if i spin down the last disk which is still spinning, then, within the next 10 s, 30 s or 60 s i spin up it back, unraid doesn't reboot. Weird.

just tried to spindown last disk that was still up, it take roughly 7 minutes, but it rebooted again.

2 Ironwolf 6TB as parity et 3 6TB seagate ST6000DM003 for data, got a nvme 256GB as cache also. Parity are sdd and sdb, data are sde sdc and sdf. Does it answer to your question? edit: 29 is parity 2 drive. others drives seems correctly numbered: parity is 0, disk 1 => 1 disk 2 => disk 3 => 3.