AmishJoe

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by AmishJoe

  1. Yes, I cannot connect to the samba shares from windows.
  2. Sorry. I meant Private (user and only the user gets RW access). But at this point, I have deleted that share and the user. I have unmounted the existing shares and rebooted the desktop. I get an authentication prompt when I try to mount the share, and nothing I enter will work. I am, right now, unable to mount any Public shares.
  3. Hi All, quick summary of what happened to maybe help root cause it: - Shares were all originally marked public, all working - Created new share, wanted it to be Private (RW to one particular user) - Create new user - Set share to Private, granting user RW access - Try to map share from windows using user account, failed - Now, no shares are mountable, even previously working Public shares - Delete share, delete user, still cannot mount any shares still flagged as Public Assistance appreciated... at this point I'm wondering if I need to start my smb.conf all over but am not sure on how to do that. No custom additions to smb.conf
  4. Post a screenshot, sounds like something not set right. Network attached. Have tried multiple reboots. This configuration worked before upgrading to Beta23 (came from Beta21). MTU9000 worked before upgrading to 6.2, others have reported it broken. Switch is configured fine (PowerConnect 6248), and I can access WebGUI and SSH no problem. EDIT: I manually added nameserver 172.17.10.1 to my /etc/resolv.conf and this allows me to ping google, but interesting how I cannot configure this from GUI. I also assume this will not survive a reboot. Have not yet tested with MTU set back to 9000. Looks like a remnant of your previous configuration. - Switch the setting for IP assignment to "automatic", this will enable the setting for DNS. - Now you can change DNS setting to static and enter the desired IP address(es) - Switch IP assignment back to static I'm sure this will work, but I do have to say - I have only ever had a static configuration here. DNS worked previously...
  5. Post a screenshot, sounds like something not set right. Network attached. Have tried multiple reboots. This configuration worked before upgrading to Beta23 (came from Beta21). MTU9000 worked before upgrading to 6.2, others have reported it broken. Switch is configured fine (PowerConnect 6248), and I can access WebGUI and SSH no problem. EDIT: I manually added nameserver 172.17.10.1 to my /etc/resolv.conf and this allows me to ping google, but interesting how I cannot configure this from GUI. I also assume this will not survive a reboot. Have not yet tested with MTU set back to 9000.
  6. After setting MTU back to default, I am unable to configure a DNS server in the GUI (grayed out, unable to change from Automatic) and still unable to talk to Github or ping google.com
  7. I re-enabled MTU9000 in the Network settings (with 2x 802.3ad bonded cards, with a properly configured switch for LACP) and I am still unable to check for Docker updates. "Fix Common Problems" is reporting that I don't have DNS set up properly, although this works fine as soon as I disable MTU9000. I can view the WebGUI and SSH to the server no problem. Diagnostics attached. wopr-diagnostics-20160612-1236.zip
  8. Glad I found this thread, having the same issue on an upgraded 6.2.0-beta21. Jumbo frames worked fine before. Boooo.
  9. Been using for a week, but I have an odd problem: All of my Dockers say they have an update available, but when I go to update them they do not connect and ultimately fail. The Dockers themselves have full network connectivity, and when I SSH to the unraid host I can ping github/etc. just fine. Any thoughts? Using mostly linuxserver.io Docker images. EDIT: Appears that the Docker engine does not like Jumbo frames. I have 2 NICs bonded, and the NIC interfaces and the bond0 interface all have MTU9000 set. This appears to be the bug.
  10. Went ahead and did it, worst-case I had the data I could re-sync. This seems to have done the trick, thanks! (But why is this so difficult? It seems like I should be able to remove a disk much easier than this...) Thanks
  11. I didn't have a clean parity in the first place. So, New Config, reassign disks, will all the data be lost or will it be saved?
  12. Hi All I'll try to summarize a long story short: I had an SSD cache. I ran into issues where it would fill up, and rather than data copy to then go straight to the array, it would just fail. So I removed the cache, and everything was happy. Remaining 12TB copied no problem. Now, I want to re-add the SSD cache. To "start over" I decide to format the disk. To do so, I add it to the array, format it, then remove it from the array. Now, when I add it back as a cache, the array shows that it's missing the disk. How can I convince the array that it doesn't need this disk anymore? Thanks.
  13. I just installed it on 6.1.6 no problem. Worked out of box with Observium and SNMPv2.