fwiler

Thank you for your help.

Not only should you - you will need to. You can't mount multiple pools to the same path. I did some more reading, and I see my original question wasn't clear due to wrong naming convention. Mount points can be the same for multiple pools according to what I read. The pool names obviously have to be different. For instance zpool create -m /mnt/disks/zfs poolname mirror sdb sdc and zpool create -m /mnt/disks/zfs poolname2 mirror sdd sde. The actual mount point for both is /mnt/disks/zfs. I guess my confusion is that I don't see the pool name when browsing to /mnt/disks/zfs/, only datasets created under those pools.

Yes, I have them currently like you list. (Although I don't see the actual pool names under zfs, just the datasets). I just didn't know if I should put 2nd pool at i.e /mnt/disks/zfs2. Essentially a different mount point for a different pool. Or if it made any difference. I had picked /mnt/disks/zfs as the mount point because 1. One of the developers or moderators said not to mount at /mnt/ and suggested /mnt/disks/xxx. 2. When I tried /mnt/zfs/ I received complaints from Fix Common Problems. Probably not a big deal, but easy for me to change. If I shouldn't use /mnt/disks/xxx then I will change it as I'm just setting things up. As far as sharing, I believe I understand as I've tested out several different configurations for shares. I was just asking about the permissions on the location of the mount point. For instance mnt, disks, and in my case zfs all have different permissions. But if setting the correct permissions on the share is what matters, then I won't worry about it.

I have two pools because of different types of disks, with mount point of /mnt/disks/zfs Is there any issue with this? Or should the 2nd pool be mounted on a different location such as /mnt/disks/zfs2 ? For Samba share purposes, does 'zfs' in my case need any permissions set, or should these be set at the datasets? Thanks

Following thread, as I'm hoping this can be fixed in OS and not rely on specific Docker fixes. I've actually stopped using all Dockers for now.

Thanks for quick reply.

I have trial on my one good usb drive (all other usb drives are too large) Problem is I used trial on temporary PC, not the final hardware I want to use unRAID on. What is best way to proceed? Do I purchase unRAID with current USB drive, even if it's plugged into temporary PC? Then move USB drive to new hardware. Or is it best to just purchase a new USB drive to put onto new hardware? I do not need to save any configuration or setup and worried that old hardware config on USB will mess up install on new hardware.

That's unfortunately is not the right question to ask. It may very well be Unraid and how it handles or identifies your hardware, but you have to narrow down the issue first before you can fix it. All the other one's you have tried, may be using a different driver for the nic (This is just an example) It could be chipset, memory controller, sata controller, etc. In my example we had issues with Broadcom nic that came with Dell server. It was on the Windows WHQL list It had the same issue you describe where you can start a transfer, and then it just slowly dies down to 0. The nic couldn't handle anything over about 1GB before slowing down. It ended up being a vmq setting on the nic that was partially the issue, but also firmware, and the driver. NIC worked great under Linux. So as you can see, one operating system may just not like your hardware. Hope you can get it figured out. If possible maybe try a 2nd hand computer just as a test.

Having a separate account for Veeam is actually recommended, as is most backup software. It's not unusual because you can't have same user account accessing same share and backup at same time. It would create a massive amount of errors and /or corruption. Just don't become an admin You have to keep track of accounts for hundreds of different services and security features to do it correctly.

This is the correct answer for a domain joined computer. Otherwise Windows will automatically assume you are trying to use a Windows domain user and try to authenticate to the domain controller. Example. Login with user Administrator will login to domain Administrator. To login to Administrator on local computer you have to type .\Administrator for user name.

This sounds very similar to a nic driver problem. I see this quite often on Windows server side connecting with clients. Especially with older nics from Broadcom or Realtek.. but also on Intel. Usually upgrading the firmware of the nic will help, but also knowing the driver being used. If Unraid is not using the correct files needed or misidentifies your nic, then you will see this problem. Also an issue- Multiple Windows machines with same user signed in. This will cause issues with shares. Especially prominent if Settings > Accounts > Sync your settings. By default, the option to Sync settings is turned on. I don't know what motherboard you are using for Unraid, but judging by the $30 cpu, I would guess the motherboard may have issues., sense you have multiple clients even a mac that exhibits the same issue. Upgrade firmware. If no new firmware for nic is available, that is a problem. Check what Unraid detects it as. Never try to bond different manufacturers nic's. No vendor or OS supports this as best practice. There are so many issues with Realtek, it's unbelievable. You say you have server grade network equipment. Unfortunately that doesn't mean a thing. The very best $10,000 switches have issues and if you are not invested in support there is no way for you to know all the issues. We have contracts with Cisco and HP because equipment doesn't always do what they claim it will. You aren't going to find these fixes in a forum. Point is. Connect PC directly to Unraid without any switch. If you still have issue, then I highly suspect NIC.