• Posts

  • Joined

  • Last visited


  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Limy's Achievements


Rookie (2/14)



  1. Upgraded from 6.10.0-rc2. Did not see any issues. Big improvement wit Samba though. Backup with OS X Chronosync was taking 6 hours 15 minutes. This now changed to 1 hour 45 minutes. Still not as fast as what I had with AFP on 6.9.2, but much better.
  2. Thanks for giving us ipvlan. I wish this was available a few years ago. No more macvlan unraid lockups since upgrading to 6.10.0-rc2 and switching to ipvlan. My machine was locking up every second day, but now I haven't had a lockup for over a month.
  3. Changed Status to Closed Changed Priority to Annoyance
  4. So I was able to try the suggestions you gave me. I pretty much had to, because OSX samba client connecting to UNRAID 6.10.0-rc2 and the finder in OSX was locking up. The results are that things are working again, not sure how long...Speed is still slower than normal, but at least it's working. In my opinion, I think unless it was absolutely necessary, I think unRAID should have kept the AFP protocol capability for legacy users. I realize that there are security updates all the time and things need to move along, but do we have to force everyone to move forward all the time. I have systems in place that cannot be upgraded for legacy reasons and personally I think SAMBA sucks big time. It would be interesting to know what other people's experiences are. Thanks for your help.
  5. I took the plunge and went from 6.5.3 to 6.9.2 No issues except SMB. Something that normally took 20 minutes to complete now takes 2 Hours. I've also read about people having issues with this in the unraid forums and some on reddit, regarding people upgrading to 6.9.2 from 6.8.X or earlier and having the same problem. I also have seen reports that this is occurring in 6.10.X. I am not using a cache drive on my system whatsoever. I am accessing the share from an older OSX (10.13.4) client.
  6. I’m using Nextcloud on a MacBook Pro. Very happy with this solution. I basically installed the Nextcloud application on a Mac Pro and then a MacBook Pro. You just drop the files in your Nextcloud and the files are synced to all devices running Nextcloud. It works similar to Dropbox, but all of the files are stored on each computer as well as on unRaid.
  7. Glad I could point you in the right direction. I and others will undoubtedly find that incorrectly setting up VLAN’s will cause those broadcast messages and cause the sort of issues you were facing. My thanks goes to @ken-ji for initially pointing me in the right direction.
  8. Another alternative you could try is I have successfully used it instead of VNC and it worked very well.
  9. I’m not saying this is your issue, but I had a lot of problems connecting from a Vlan to my Krusader docker when my Vlan wasn’t configured properly. I was constantly getting lockup’s. This post helped to clear up my Vlan issues: At any rate, this should help you to determine the proper setup of your Vlan’s.
  10. I don't have AFP enabled under settings. Other than that, I have my security set to private and I have my SMB User Access set to Read/Write. I don't use sabNZB, but maybe it's locking the files. I guess a good way to test would be to stop sabNZB and see if you can delete a file.
  11. So I have been running my system since Wednesday of last week and I no longer have any call traces on macvlan. I may try the next suggestion and place with a DHCP pool on br4. Right now, I’m very happy that I can eliminate the call traces. *** Just an update on this. No more call traces in my system as of July 4th. I would say my problems have been resolved. ***
  12. I get roughly the same error when I boot unRaid. I haven’t delved into it.
  13. Windows 10 has a firewall. You may have to turn that off.
  14. Well I'm glad my odometer doesn't go up like my cache otherwise I would need a new vehicle a lot sooner
  15. So basically, nothing to be concerned about.