Flavio61

I'm resuming this discussion because the problem that seemed to be solved by disabling Roon's docker actually always comes up again. Now I've done some tests and I've found that if instead of double-clicking on the Unraid server icon I use the network path with the IP address, the folders all open on the first attempt without problems. So I guess it's DNS issues, I've checked on our DNS server and everything seems fine the entry for the UnRaid server is there and the IP address is properly logged. What can I do?

Yes, with the Roon docker down everything seems to work. But I have no idea how to fix when the docker is active.

n my Windows PC I have problems accessing Unraid server shares, often to be able to access the shares I have to click several times on the server icon before it opens. Investigating the problem I noticed that if instead of using the name of the server (Tower) I use the IP address this opens immediately. In the Unraid server log I found this warning: "WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended." lsof -i -P -n | grep 5353 and I have this reply: avahi-dae 15225 avahi 14u IPv4 3572990 0t0 UDP *:5353 RoonAppli 20514 root 280u IPv4 1883480 0t0 UDP *:5353 RoonAppli 20514 root 282u IPv4 1883482 0t0 UDP *:5353 RoonAppli 20514 root 284u IPv4 1883484 0t0 UDP *:5353 It therefore seems that Roon's docker creates an incompatibility with avahi's mDNS. Unfortunately I am not so experienced as to understand how to solve this problem. Any help? Thank you.- Edited 3 hours ago by Flavio61

I think the problem is in the mDNS because I noticed that if I enter the server with its IP address (\\192.168.100.7) the shares open immediately on the first attempt. I tried this command found on the net: lsof -i -P -n | grep 5353 and I have this reply avahi-dae 15225 avahi 14u IPv4 3572990 0t0 UDP *:5353 RoonAppli 20514 root 280u IPv4 1883480 0t0 UDP *:5353 RoonAppli 20514 root 282u IPv4 1883482 0t0 UDP *:5353 RoonAppli 20514 root 284u IPv4 1883484 0t0 UDP *:5353 It therefore seems that Roon's docker creates an incompatibility with avahi's mDNS. Unfortunately I am not so experienced as to understand how to solve this problem. Any help? Thank you.

On my Windows PC I have problems accessing Unraid server shares, often to be able to access the shares I have to click several times on the server icon before it opens. Investigating the problem I noticed that if instead of using the name of the server (Tower) I use the IP address this opens immediately. In the Unraid server log I found this warning: "WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended." lsof -i -P -n | grep 5353 and I have this reply: avahi-dae 15225 avahi 14u IPv4 3572990 0t0 UDP *:5353 RoonAppli 20514 root 280u IPv4 1883480 0t0 UDP *:5353 RoonAppli 20514 root 282u IPv4 1883482 0t0 UDP *:5353 RoonAppli 20514 root 284u IPv4 1883484 0t0 UDP *:5353 It therefore seems that Roon's docker creates an incompatibility with avahi's mDNS. Unfortunately I am not so experienced as to understand how to solve this problem. Any help? Thank you.-

From different PC is the same. In the Syslog the only warning that I read is: Sep 30 11:34:42 Tower avahi-daemon[15225]: *** WARNING: Detected another IPv4 mDNS stack running on this host. This makes mDNS unreliable and is thus not recommended. *** Could that be the problem?

I am resuming this discussion because Unraid share connection issues are not resolved. I always have the problem from Windows where I have to click several times on shares to be able to open them. I tried from an Android device to access Unraid nfs shares and nothing opens. Any suggestions? Thank you.

Same problem for me too

Also with a share I have same problem: after some clicks all works:

Any help?

I installed UnRaid 6.11.5 for several months everything works correctly I have only one problem when from Win11 I have to access shared folders. The server is immediately seen when I open the Windows Explorer but to access the folders I have to double click on it for about ten times before it opens. How can I overcome this problem?

I solved the only problem is that this controller takes more than six minutes to start up. I have other LSI controls and they all start almost immediately so I hadn't waited that long.

Hello, I installed a LSI sas2008 IT mode 9201-8i PCIe x8 6gb DUAL SAS RAID CARD on my server which is equipped with a Supermicro X11SSL-F motherboard compatible with the controller. Unfortunately, with the controller mounted, the server does not complete the boot and stops immediately after recognizing the LSI controller. The server remains blocked on this screen: I have tried all three expansion slots on the motherboard, I have tried with the disks connected and with the disks disconnected, I have tried with the SAS-Sata cables connected and disconnected but to no avail. Any help. Thank's

Any help?

Hi everyone, my server needs a hardware upgrade because I am reaching the maximum capacity of the current disks. The server configuration is as follows: M/B: Supermicro X11SSL-F Version 1.01 - s/n: UM206S007636 BIOS: American Megatrends Inc. Version 2.5. Dated: 11/26/2020 CPU: Intel® Xeon® CPU E3-1220 v5 @ 3.00GHz Memory: 16 GiB DDR4 Single-bit ECC (max. installable capacity 64 GiB) Network: bond0: bond down eth0: 1000 Mbps, full duplex, mtu 1500 eth1: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 5.10.28-Unraid x86_64 OpenSSL: 1.1.1j I have one 10Tb parity disk, three 10Tb data disks, one 6Tb data disk and one 1Tb cache disk. All disks are connected to MB Supermicro X11SSL-F SATA ports. The idea is to add at least two SATA ports, replace the power supply and the case. For the power supply I already have a Corsair RM850x at home and I think I use this, but I have no idea about the SATA card and the case. As mentioned above I would like to add at least two SATA ports and I would like a case that can accommodate the current six drives plus at least two more and if possible I would like to have a case with removable discs from the outside without having to open the case. I have no idea which board and which case is right for me and I trust the community for suggestions on how to proceed. Another doubt I have is how to continue when I have the new case and I will have to transfer the whole system inside. In order not to lose the current configuration, do the current disks have to be connected to the same SATA ports to which they are currently connected or can they be connected to any of the available ports? Thanks for the help you will want to give me.