I'm not sure the hardware is relevant to this issue but I will start with that:
SCALE beta released. Decided that native docker would be cool for some future projects. Exported the pool in CORE. Installed SCALE 21.06 beta. Imported the pool. Created an SMB share. First issue. I was receiving an error when trying to set ACLs on the share. Found a post with others talking about the same error. ACL type was blank. So I selected POSIX. Now ACLs changes were applying. Accessing it from my windows box working great.
Now changing focus to the Nvidia Shield, I went and enabled NetBIOS-NS (disabled by default understandably). Now running into two issues:
- 2x Xeon X5670 (2x 6c/12threads, base 2.93/max 3.33 GHz)
- 24gb ddr3 ecc (6x4gb)
- LSI SAS 9210-8i controller
- Super Micro X8DTL-iF motherboard
- Intel quad gig nic
- some seasonic 620w psu
- a bunch of WD HDDs
SCALE beta released. Decided that native docker would be cool for some future projects. Exported the pool in CORE. Installed SCALE 21.06 beta. Imported the pool. Created an SMB share. First issue. I was receiving an error when trying to set ACLs on the share. Found a post with others talking about the same error. ACL type was blank. So I selected POSIX. Now ACLs changes were applying. Accessing it from my windows box working great.
Now changing focus to the Nvidia Shield, I went and enabled NetBIOS-NS (disabled by default understandably). Now running into two issues:
- This could be an issue on the shield but if I restart the server, I have to first disable NetBIOS-NS, save, then re-enable it. Ignoring the webgui, how can I verify if this setting is staying enabled after restarts?
- No matter what settings I play with, try different credentials, enable/disable legacy items like SMB1, the nvidia shield continues to give the unhelpful vague message "connection failed". I want to blame the nvidia shield for this but it was working flawlessly on CORE. Any ideas how I can go about troubleshooting this?