Leaderboard

Would it be possible to add a module for USB Attached SCSI (CONFIG_USB_UAS) protocol? This is required to support a card like the StarTech PEXUSB3S44V. There are a number of users trying to get this card working. The UnRaid kernel enumerates the card but it does not actually work. This card has 4 independant USB3 controllers and it looks as if you could pass each controller to a different virtual machine. UASP Information On this thread @Siberys details his issue with the StarTech PEXUSB3S44V USB3 card with 4 separate USB3 controllers that needs UASP support to function. 08:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02) (A) 09:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02) (B) 0a:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02) © 0b:00.0 USB controller [0c03]: Renesas Technology Corp. uPD720202 USB 3.0 Host Controller [1912:0015] (rev 02) (D) /sys/kernel/iommu_groups/42/devices/0000:08:00.0 /sys/kernel/iommu_groups/43/devices/0000:09:00.0 /sys/kernel/iommu_groups/44/devices/0000:0a:00.0 /sys/kernel/iommu_groups/45/devices/0000:0b:00.0 Post 1 Post 2 UPDATE: I have built a unRaid 6.4 rc6 test kernel with USB Attached SCSI enabled and have a card to test with on the way. I will hopefully have and update after July 1. Thanks

When mounting volumes in docker, we're missing some propagation options ("Access Mode") for the mounted volumes. They are not well documented on the official docker documentation, but some more information can be found here. Currently we can do: RW, RW/Slave, RO, RO/Slave Default is private, we can specify slave but we're missing the "shared" option so we can do -v /mnt/disks/acd_volume/:/data:shared Current work around is just to use the "Extra Parameters". Here some more information regarding the propagation options (c/p from manpages): By default bind mounted volumes are private. That means any mounts done inside container will not be visible on host and vice-a-versa. One can change this behavior by specifying a volume mount propagation property. Making a volume shared mounts done under that volume inside container will be visible on host and vice-a-versa. Making a volume slave enables only one way mount propagation and that is mounts done on host under that volume will be visible inside container but not the other way around. To control mount propagation property of volume one can use :[r]shared, :[r]slave or :[r]private propagation flag. Propagation property can be specified only for bind mounted volumes and not for internal volumes or named volumes. For mount propagation to work source mount point (mount point where source dir is mounted on) has to have right propagation properties. For shared volumes, source mount point has to be shared. And for slave volumes, source mount has to be either shared or slave. Use df <source-dir> to figure out the source mount and then use findmnt -o TARGET,PROPAGATION <source-mount-dir> to figure out propagation properties of source mount. If findmnt utility is not available, then one can look at mount entry for source mount point in /proc/self/mountinfo. Look at optional fields and see if any propagaion properties are specified. shared:X means mount is shared, master:X means mount is slave and if nothing is there that means mount is private.

From what I remember the min/max allocation have never really worked. It's been discussed in some threads a while ago. The advice have been to set min and max to the same.

So using torrent clients without an incoming port is a really bad idea, not only does it give you cripplingly low download speeds, but also causes problems for the swarm. Can I ask why you specifically want to connect to a us endpoint? Sent from my SM-G935F using Tapatalk

Was looking through your diagnostics and found this for eth1: Settings for eth1: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Speed: Unknown! Duplex: Unknown! (255) Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on MDI-X: off (auto) Supports Wake-on: pumbg Wake-on: g Current message level: 0x00000007 (7) drv probe link Link detected: no Apparently, it is not detecting a physical connection to your network switch/router. (You see to be trying to use by the entries in the network.cfg.) Check to see that you have good connection, switch ports on the switch and replace the cable if necessary.

I've been good lately... (At least until what I'm working on right now gets released )

First read this post: If you are still having problems after this: First make sure that your unRAID server is the Local Master. Second, try booting in the "OS Safe Mode (no plugins, no GUI)" option on the unRAID boot menu. Of course the Local Master plugin would be working... Third, there is a program that will run on Windows computers that will tell you what computer that computer is using as the Local Master. You can find it here: https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/ (All of the usual warnings about downloading stuff from the Internet apply. I have used this program in the past and not had any problems.)

V6.4 RC6 builds all done and uploaded.

Luckily you can pass the keyboard/mouse on a machine without vt-d so just add a keyboard! You only need vt-d for pci passthrough. Also try adding this below the xml for the disabled nic, if above fails <interface type='bridge'> <mac address='52:54:00:35:d1:d2'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x03' slot='0x03' function='0x0'/> </interface> This will add a second nic best of luck !

Install this first Then install this and this by following this tutorial https://www.linuxserver.io/2017/05/10/installing-nextcloud-on-unraid-with-letsencrypt-reverse-proxy/ to get it all working together.

yes, a comma separated list will do it, e.g. LAN_NETWORK=92.168.1.0/24,10.1.0.0/24