Jump to content

eschultz

Administrators
  • Content Count

    487
  • Joined

  • Last visited

  • Days Won

    7

Everything posted by eschultz

  1. When I add macOS "labels/tags" on a file or directory from a Unraid share via samba protocol it adds EA data: root@Tower:/mnt/user/testshare# getfattr test_folder/ # file: test_folder/ user.DOSATTRIB user.DosStream.com.apple.metadata:_kMDItemUserTags:$DATA user.org.netatalk.Metadata Additionally, 'getfattr' will show the values, along with the keys above, with the -d argument. I did another test involving a cache pool setup: Created another share named 'cache-first' with Cache mode set to 'only.' Browsed to the 'cache-first' share from a mac, created a new folder, and then applied macOS "tags" to it. Verified those EAs were present using 'getfattr folder-name'. Change 'cache-first' Share's Cache mode to 'yes'. Run the mover Verified 'cache-first' share exists on the array now, and the EAs are still present. My mac again shows the correct "tags" I added previously. I can also copy/move files or folders between my mac and Unraid, in either direction, and the "tags" persist. macOS version 10.14.6 Unraid version 6.8.3 Two BTRFS formatted SSDs in my Cache Pool Array disks all XFS-luks If you're working from a terminal, using 'cp,' 'rsync,' or 'scp' for example, ensure you provide any arguments you may need to preserve xattr.
  2. Maybe a index rebuild will help that but it'll take about an hour to run... ***EDIT*** Index rebuild completed, any activity missing from the last couple days should be restored now.
  3. Which motherboard or add-on card are you using that has thunderbolt?
  4. eschultz

    noVNC errors

    Which web browser are you using?
  5. We have backup script execute at that time which causes timeouts / 502 errors for a minute or two. I'll try to optimize the backup scripts to lessen the impact.
  6. A new build is ready for internal testing but I haven't upgraded to Catalina yet. Could someone please test it out?: https://s3.amazonaws.com/dnld.lime-technology.com/tools/Unraid.USB.Creator.macOS-1.7.dmg
  7. The duplicate 'My Activity' menu item should be fixed fixed now. Thanks for reporting.
  8. Has anyone here tried Unraid 6.7.1-rc2 release to see if the sqlite corruption issues are still there?
  9. Yeah, get rid of the following from network.cfg: IFNAME[1]="br1" BRNAME[1]="br1" BRNICS[1]="eth1" BRSTP[1]="no" BRFD[1]="0" DESCRIPTION[1]="VMs connections" PROTOCOL[1]="ipv4" USE_DHCP[1]="no" IPADDR[1]="192.168.86.125" NETMASK[1]="255.255.255.0" GATEWAY[1]="192.168.85.1" METRIC[1]="2" Also change SYSNICS="2" to SYSNICS="1" at the end. Then reboot server.
  10. Looks like in 6.7 the default route is being set incorrectly to br1 instead of br0. Are you using br1 for anything? It looks like eth1, the link for br1, is disconnected anyways...
  11. We actually removed git from 6.7.0 but it'll probably be added in to 6.8
  12. We'll include QEMU 4.x in Unraid 6.8
  13. Unfortunately IPS (our forum software) removed that in version 4.4.x: "Removed the name of the content (e.g. topic) from the “Next Unread” link which could consume significant server resources on large communities."
  14. Both of these issues should be solved now, please let us know if it's still not working for you.
  15. Latest version of Plex (1.14.1.5488) is now live. Sorry for the delay, ran in to a couple snags with the new version.
  16. Not see that error here. Maybe one of your installed plugins are causing this? (try booting in safe mode)
  17. Try adding https_proxy in the mix too: http_proxy=http://proxyserver:port https_proxy=http://proxyserver:port /usr/local/sbin/emhttp &
  18. This plugin will need to upgrade to using the openvpn-2.4.6-x86_64-2 package since it is compiled to work with the newer versions of openssl. The legacy version of openssl (libcrypto.so) was removed in 6.7.0-rc1.
  19. Please contact us here and we'll take care you: https://unraid.net/contact
  20. Check the connections to TOSHIBA DT01ACA200 s/n 13MGREJAS... I think that's the drive/port reporting errors in your System Log.
  21. Actually since the motherboard has a Z68 Express chipset it most likely does not support VT-d: https://ark.intel.com/products/52816/Intel-BD82Z68-PCH
  22. Looks like either of those models without the 'K' support VT-d: i7-2600: Yes i7-2600S: Yes i7-2600K: No i7-3770: Yes i7-3770T: Yes i7-3770S: Yes i7-3770K: No
  23. Witch motherboard are you using? Are you running the latest BIOS?
  24. Oddly I only have one numa node:
  25. I'm a little behind and still running on BIOS 7B09v1B (08/14/2018) - AGESA Code 1.1.0.1A. Should be the same version as your motherboard now it seems.