zoggy

May 27 08:05:07 husky root: Hard File Path: /mnt/cache/TV/TV/Shark Tank/Season 14/<removed>.mkv May 27 08:05:07 husky root: LINK Count: 1 May 27 08:05:07 husky root: Hard Link Status: false ... May 27 08:35:18 husky move: file: /mnt/cache/TV/TV/Shark Tank/Season 14/<removed>.mkv May 27 08:35:30 husky root: mover: finished When mover fires off there is a bit of log spam for hard link stuff.. then the actual mover log. Any way a user can turn off the hard link set of logs?

I assume also that you want one path per line like: /mnt/user/x /mnt/user/y And related, the "Ignore Hidden Files" also could probably use the help line to denote that its excluding paths (file/folders) to be moved that start with a dot (.*) (ex: .config)

feature request idea: add root/custom? password to backup

minor quibble, this is v3 of the plugin but still uses the old page name "BackupMainV2" verify backups has same warning of ignore errors, which i suspect is in error Verify Backups? This can lead to broken backups - Only enable if you know what you do! Ignore errors during backup? This can lead to broken backups - Only enable if you know what you do! when you use the "Excluded Folder Browser" you can only pick top level folder, would be nice to have it show actual tree and be able to pick the nested folder to be a bit more surgical. right now i do this via cli then come back and just put in the path manually (which works fine). the folder selector for USB Backup Destination: / libvirt.img Destination: show up in the wrong spot:

no you can not take a random mono/.net app and snip out part of their code and just shove it in another app. you should look at setting up a reverse proxy. but also you shouldnt just blindly have your nas exposed to the internet either. look at requiring a vpn..

Using unraid 6.11.5 Single nvme drive in cache, btrfs. No scrub/anything special. We were talking in discord recently about this, and I notice that my cache (created 6.9.x after the 1 MiB alignment) doesnt include the discard option like it mentions it should: # mount | grep /mnt/cache /dev/nvme0n1p1 on /mnt/cache type btrfs (rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/) /mnt/cache/docker.img on /var/lib/docker type btrfs (rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/) /mnt/cache/docker.img on /var/lib/docker/btrfs type btrfs (rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/) /mnt/cache/system/libvirt/libvirt.img on /etc/libvirt type btrfs (rw,noatime,ssd,space_cache=v2,subvolid=5,subvol=/) Is there a known bug/issue where it doesnt add the discard option if its a pool named 'cache' or only single drive with some other criteria?

to make it a little easier for those, one liner to copy+paste to update (and guarded so even if you run it multiple times it wont mangle the line) sed -i "s#distribution.manifest.v2+json'#distribution.manifest.v2+json,application/vnd.oci.image.index.v1+json'#" /usr/local/emhttp/plugins/dynamix.docker.manager/include/DockerClient.php

confirmed this fixed issue i had with "netdata-glibc" saying not available when there was an update. (unraid: 6.11.5)

I've never seen this before until 6.11.4 and now 6.11.5 and have the same plugins for a bit now. The newest plugin I installed was the "CA Mover Tuning" one, which per my logs I've had installed since 6.11.0-rc3 (August). I do not have array auto start. When array comes up after upgrade, says config is good. I go to start array, and in firefox 107 it shows the resend prompt. If you hit cancel, it works fine. If you hit resend, it puts the array in a 'stale configuration' state. Where you can only reboot/shutdown server. plugins: CA Auto Update Applications CA Backup / Restore Appdata CA Cleanup Appdata CA Mover Tuning Community Applications Dynamix Active Streams Dynamix System Information Dynamix System Statistics Dynamix System Temperature Fix Common Problems Tips and Tweaks Unassigned Devices Unassigned Devices Plus Unassigned Devices Preclear unBALANCE

for what you were installing with nerdpack, look for what you had set to yes in it's cfg (even if nerdpack is disabled): grep yes /boot/config/plugins/NerdPack/NerdPack.cfg for what is installed currently in unraid: ls -lah /var/lib/pkgtools/packages/

or once you are on 6.11 you can install several just via CA with, "<x> package".. python2/3 for example are there also with 6.11, there are several plugins that are included by default that save the need for many people to use nerdpack anyways. for example perl is included now.

another update, 6.10.x corrected/enabled a lot of the asus sensors but still had no fans. with unraid 6.11rc3 I can confirm fans are there now as well and all is working well: **update** updating to 6.11rc4 I can see even more fan/sensors added (asusec).

if you are confused, just enable mover logging, enable test mode on the mover tuning plugin, and set the "Move Now button follows plug-in filters:" to yes. so you can just fire off the script and see what it would move. tweak values and repeat. once all good, turn off test mode... testing myself as i have it set to move stuff older than 10 days and "Move All from Cache-yes shares pool percentage:" set to 50%. with mover running weekly. with only 18% cache used, and a few files older than 10 days. firing it off.. it moved a few files older than 10 days. so the logic to move by age does not limit by the cache usage.

unraid 6.11rc already comes with docker engine 20.10.17 # docker version Client: Version: 20.10.17 API version: 1.41 Go version: go1.17.11 Git commit: 100c701 Built: Mon Jun 6 22:56:42 2022 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.17 API version: 1.41 (minimum version 1.12) Go version: go1.17.11 Git commit: a89b842 Built: Mon Jun 6 23:01:45 2022 OS/Arch: linux/amd64 Experimental: false containerd: Version: v1.6.6 GitCommit: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1 runc: Version: 1.1.2 GitCommit: v1.1.2-0-ga916309f docker-init: Version: 0.19.0 GitCommit: de40ad0 but "docker compose" is not valid # docker compose docker: 'compose' is not a docker command. See 'docker --help' so looks like docker-compose-plugin will still have to be installed.