SAL-e

Hi everyone, I successfully follow this guide and I have my serial console running... mostly. I can see most of the boot process, but I can't see any messages from the '/sbin/init' process. As result I also don't see any of the shutdown messages. I suspect, some additional configuration is required to instruct '/sbin/init' to write its messages to the serial console (not only the primary monitor). I wonder if somebody already figured it out. Thank you.

Hi Everyone, I ran into the same issue. My setup is different. My unraid server has two smb shares: pve-iso and pve-backup. Both shares are mounted on my proxmox host: pve. On regular basis my pve-backup share mount point will become stale resulting in failing backups. Search on Internet suggests that different kernel bugs could result in this issue. Most common suggestion is to lower smbversion to 3.0 or 2.0. In my case this didn't help. And I didn't expect to help because only pve-backup share is becoming stale. The only difference between pve-iso and pve-backup share is 'cache' option. Because pve-iso is mostly read share and I don't care about performance cache is set to 'no' . On other hand pve-backup's cache is set to yes. Based on that I managed reliably to reproduce the problem: 1. Make sure the share is not stale. 2. Run the backup scripts. The share stayed healthy. 3. Manually ran the unraid's Mover. The share become stale on my PVE server. Next, I changed pve-backup's cache to 'no'. And I can't reproduce the issue. I will keep eye on it for sometime and see if this is exactly the issue. Looks like when the file is moved from cache pool to the disk array result in broken share. Stay tuned... UPDATE: It have been few weeks since I disabled the cache on 'pve-backup' share and it has stayed connected since.

Hi everyone, I ran into "DOCKER HIGH IMAGE DISK UTILIZATION" issue as well. Thanks to this thread I fix it without rebuilding the docker.img file. Here is the root cause in my case: 1. By default my containers are tracking app's official 'Repository' 2. I have few containers that are tracking different branch usually older 'stable' release. 3. After I have chance to fully test the newer release, I will manually update the App configuration: Repository. The problem with this method is that it leaves the old images behind filling my docker.img file. I used: docker system prune --all --volumes WARNING: Before you run this command pay attention to Squid's comment here: https://forums.unraid.net/topic/57479-docker-high-image-disk-utilization-why-is-my-docker-imagedisk-getting-full/?do=findComment&comment=827838 Thank you

Getting ready to submit my Docker templates for phpIPAM - Open source IP address management. It is using the two official docker images: phpipam-www and phpipam-cron published by phpipam on DockerHub. - phpipam-www - provides the WebGUI; and - phpipam-cron - scans your networks in order to discover network changes. This app requires external database like MariaDB or MySQL. It has been tested with linuxserver/mariadb

Hi, I'm running containers (Docker) on all three docker networks: br0 (macvlan), host or bridge. The containers running on host or bridge docker network use port-mapping and the host's ip (10.1.1.99 for example). Those containers can 'talk' to each other and they can 'talk' to the host as expected. But the containers running on br0 (macvlan) network are isolated from the host or containers running on host or bridge networks. THIS IS NOT A BUG, BUT SECURITY FEATURE. That said in some cases you might want to able to communicate between br0 and the host. There are two possible solutions: 1. Using "Macvlan 802.1q Trunk Bridge Mode" where the host and br0 use different VLANs and routing is provided by external router and your switch should support VLANs. This is the preferred method because provides the best security controls, but setting it up correctly is not as easy. 2. Creating Macvlan interface on the host itself. This is quite simple. Here is an example: http://blog.oddbit.com/2018/03/12/using-docker-macvlan-networks/ I have not tested it under Unraid, but I don't see any reason why should not work. The 'difficult' part would be to make the new Macvlan host interface and routing persistent. My questions are: 1. Is it possible to create persistent Macvlan interface for Unraid host? 2. Are there other Unraid users interested in 'feature' like this? (build-in, plug-in or user-script?) Thank you, SAL-e PS. Currently running Unraid 6.6.7.