TheJJJ42

args! that´s bad. Storing the system log is not that easy, when all the drives are 'gone missing' or the system hangs. One does not actually remember doing this, when worrying errors occur. I expected that these quite important (and not that big) logs are stored somewhere by default. Seems, that there isn´t a dedicated addon to do this? I would like to store them to the unraid usb drive as well. Can someone recommend a addon / tool that is good for this job? cron´d rsync?

Hi My unraid had troubles in the last days: - all nvme caches and pool drives 'gone', - all disks greyed out, - hang, - disabled data disk, To check the disk, I rebooted several times (also in other Linux live systems with only the troubled disk connected. Seems to be fine.). - now rebuilding array from the parity drives. Now I want to check, what was wrong. But I can´t find the system logs of the last days / week.

Nowadays I consult youtube for stuff like that. https://www.youtube.com/results?search_query=syncthing+android Find the qr-code and take a picture.

Hi. Two of my devices are not capable of finding each other in the same LAN. (Unraid server and windows box.) It was especially weird, because all other devices had no issues. (these had no firewalls, open ports.) In the end I found out, that this container is missing the announce UDP port 21067 from its configuration and 22000 stays closed. Using nmap from windows and another Linux machine, 22000 is detected as closed. When I add 21067, it does not show up in the 'docker allocations' (neither do other ports I tested with - on this and other containers), and nmap obviously shows it as closed. Changing between host and bridge network, does not help. root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name='binhex-syncthing' --net='host' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e 'TCP_PORT_8384'='8384' -e 'TCP_PORT_22000'='22000' -e 'UMASK'='000' -e 'PUID'='99' -e 'PGID'='100' -e 'UDP_PORT_21027'='21027' -e 'UDP_PORT_75'='75' -e 'TCP_PORT_76'='76' -v '/mnt/user':'/media':'rw' -v '/mnt/user/appdata/binhex-syncthing':'/config':'rw' 'binhex/arch-syncthing' ... The command finished successfully! nmap scanning windows shows every interrsting port closed, even if the firewall has rules for syncthing or is disabled completely. Do I do anything wrong? Is this a configuration issue on my machine? A Docker bug?

Trying to install the latest update: Something really wrong went on during getCategoriesPresent Post the ENTIRE contents of this message in the Community Applications Support Thread <br /> <b>Warning</b>: Invalid argument supplied for foreach() in <b>/usr/local/emhttp/plugins/community.applications/include/exec.php</b> on line <b>1714</b><br /> [] "Unknown error happened. Please post a screenshot in the support thread of the Statistics screen" (see attached)

+1 for multiple arrays. Ralf and some others had good points. Adds flexibility and new options, many never thought of. An encrypted and an unencrypted array would be great. Also, I got lots of disks and don't want to stress the parity drives for everything. Spin array 1 down if just array 2 is working. Alternatively: load balancing for two simultaneous workloads. My disks are quite different sizes. Just seems wrong to have some giants and dwarfs in the same team - in my case, their use-cases are different sports. I already see the situation, when I need to move my data to bigger disks and use this for a cleanup. Copying between two arrays will be much easier. As mentioned already: my backups won't need parity. Also, I farm chia. I don't want parity for that. Some might also fancy a btrfs raid 5 or 6 as additional array.

+2 I copy & paste the text to a text document to read it. :-(

+1 Would have helped me, especially in the initial setup (with some used disks).