BrianIsSecond

Members
  • Posts

    17
  • Joined

  • Last visited

BrianIsSecond's Achievements

Noob

Noob (1/14)

2

Reputation

  1. Does anyone know of a way to make multiple partitions on a single unassigned device? It's easy/standard to format for a single partition, but I would love to be able to create multiple partitions (e.g. xfs and btrfs).
  2. Ok... so here is what I've done. SMB: I downgraded back to 6.6.6 and tested SMB. The speed was still 50MB write and 450ish read. Therefore, I think it's safe to say that the speed issue is not Unraid. AFP: Although there are settings for AFP in Unraid 6.7, it no longer works. That's actually the reason why I was trying to use SMB in the first place. Downgrading to 6.6.6 does allow me to use AFP properly again, which gives me speeds of 397MBs write and 790MB/s read. I think I heard that Apple was releasing more support for SMB in 10.15 this Fall. If that's the case, I might just use AFP via Unraid 6.6.6 until 10.15 comes out. No rush, but I would still be curious how your MacOS 10.14 connects to an Unraid SMB share with 10gbe. Especially for those who might find this conversation online in the future. Again... thank you so, so much for your help!
  3. Thanks so much for your help! SMB2_2 was definitely worth a try. Unfortunately, that didn't work either. No difference. What's in: /tmp/unassigned.devices/smb-settings.conf ?
  4. This is a great question. I just replied the following to user 1812: ... which are where they need to be. It's the writes that are the issue. Therefore, that should verify that it's not the machine. Unfortunately, I don't have another 10gbe adapter lying around or I would have swapped that out too. However, I don't think that's the case, because the adapter works great with MacOS 10.13. Also still not sure what Unraid means when it says to: "disable samba auto-register with avahi for now." As a last resort, I am also thinking about downgrading the Unraid back down to 6.6.6 for now to see if there is a difference with that. Never downgraded Unraid before. I'm assuming that's safe, since they give a nice clean button for it. Is that a bad assumption?
  5. I'm agree with you. I'm inclined to believe it's MacOS as well. I'm just not sure what they changed. That would be wonderful if you could test it with MacOS 10.14.5 to verify. I really appreciate you testing that. I myself had an old laptop laying around running High Sierra and it worked well using same server and same 10gbe adapter, but as soon as I updated it to MacOS 10.14.5, it also slowed the write speeds down to 50MBs. So both machines at 10.14.5 write at 50MBs. Reads are around 500MB/s - 600MBs. Do you know what Unraid meant by the following options in their upgrade announcement? smb: when Enhanced OS X interoperability set, include "fruit:nfs_aces = no" to be compatible with Unraid security model (I'm assuming this just means typing "fruit:nfs_aces = no" in the blank under Settings > SMB > Samba extra configuration, correct?) smb: disable samba auto-register with avahi for now (No idea what this means.) Oh.... here are my configurations settings:
  6. Cache: Yes, cache is involved. Sorry, I should have mentioned that. I'll include screen shots of all my settings in a corresponding message, but I've got 2 of the 250GB NVMe 970 EVO SSDs using btrfs for cache. Before the upgrades (MacOS 10.14.5 and Unraid 6.7), the speed was fantastic. Probably, 250MB/s - 350 MB/s. It's been so long since I've had issues, I forgot the exact write numbers. Definitely not the 50MB/s I'm getting now. The 1gbe get's 109 MB/s, as expected with 1gbe, so it's definitely something to do with 10gbe and SMB. In past versions of MacOS I had to put "max protocol = SMB3_10" in the Unraid SMB Extra Config settings, but I don't think that's required anymore. Again, can't thank you guys enough for your input.
  7. Thanks so much for your help and reply! I'll reply with quotes below.
  8. A couple things... Was wondering if anyone else was having speed issues with combination SMB, Unraid 6.7, and 10gbe (mine is an adapter). Would anyone mind helping to explain the 2 Mac related settings when upgrading to Unraid 6.7: smb: when Enhanced OS X interoperability set, include "fruit:nfs_aces = no" to be compatible with Unraid security model (I'm assuming this just means typing "fruit:nfs_aces = no" in the blank under Settings > SMB > Samba extra configuration, correct?) smb: disable samba auto-register with avahi for now (No idea what this means.) Current Setup Unraid 6.7 SMB > Enhanced macOS interoperability: YES Mac directly connected to Unraid server through 10gbe adapter (Thunderbolt 2 Akitio 10gbe) For example, server is 192.168.11.220 and Mac computer is 192.168.11.1. Therefore, I just "connect to server" via smb://192.168.11.220 (no issues connecting) Proper Updated Driver Install for Thunderbolt 2 Akitio 10gbe (And, yes, I removed all old drivers and reinstalled new version.) MacOS 10.14.5 Mac Network Settings > Advanced > Hardware Configure: Manually Speed: 10Gbase-T Duplex: full-duplex, flow-control (only option) MTU: Jumbo (9000) What Works: MacOS 10.13 - smb://192.168.11.220 - Thunderbolt 2 10gbe Akitio adapter - Unraid 6.7 = Good Speeds MacOS 10.14.5 - smb://192.168.11.220 - No 10gbe Adapter (built in 1gbe) - Unraid 6.7 = 109MB/s read/write (as expected for 1gbe) What Doesn't Work: MacOS 10.14.5 - smb://192.168.11.220 - Thunderbolt 2 10gbe Akitio adapter - Unraid 6.7 = 50MB/s write (problem) & 550MB/s read I am struggling trying to determine the exact issue is. It would seam to me like this has to be an MacOS 10.14.05 issue, but I know there were lots of changes to Unraid 6.7 to make things like TimeMachine work over SMB, which I am not using. I also have no idea what "disable samba auto-register with avahi" means in the Unraid 6.7 instructions. Plus I believe MacOS 10.14 supports a higher SMB version, so there still might be a setting on the Unraid server that needs adjustment. Any help would be great, greatly appreciated! Thanks so much!
  9. Version: 6.6.6 Problem: Unable to update a VM. After clicking "update," the button simply changes to "updating..." and never finishes. Replication Steps: 1. Select VM and click "Edit" 2. Change Name (or toggle "autostart"... just to test some kind of change😞 3. Click "Update". Other Notes: If it helps to diagnose the problem, toggling "auto start" from the "Virtual Machines" main menu works perfectly (see image below). However, clicking into a specific VM via "edit", and then choosing "update", as mentioned above, does not.
  10. Even after switching to public, I am still getting the same issue. Any update on this?
  11. Gotcha. Thanks! That's good to know. Another thread mentioned that this might happen when booting to non-UEFI. Good to know that's not the case, so that I can eliminate that as a possibility. I'll investigate further.
  12. Is an "FF" code normal after booting in Unraid? Everything works great in my build. Unraid works great booting in legacy and UEFI. My Asus motherboard manual says that "FF" code is "Reserved for Future AMI Error Codes." I'm not 100% confident in what that means. I've gone through the troubleshooting process of unplugging everything I can. Still get "FF" when booting into Unraid. Again, everything seams to work great. Loving Unraid! Just want to make sure the "FF" is normal in this case. Specifications: Asus P10S WS motherboard 1 NEMIX 8 GB DDR4 2133 ECC UDIMM RAM Intel Xeon E3-1245 v5 3.5 GHz Quad-Core LGA 1151 Processor CORSAIR HX750 Full Modular PSU
  13. Thank you! Great product! I'm so excited to use it! 🙂
  14. I tried both methods (manually, and usb creator). Neither worked. I posted a bug report here:
  15. I used the same "SanDisk Cruzer Fit CZ33 32GB USB 2.0" to create a bootable UNRAID USB using a computer running macOS Mojave and a different computer running High Sierra. High Sierra worked flawlessly. Mojave took forever, said it succeeded after a long period of time, but would never boot. I tried to create the boot USB on Mojave with the "USB Creator" and manually. Neither worked. Again, High Sierra works great. I believe Mojave is the issue. When trying to create the boot USB manually through Mojave, one can actually see where it hangs up via the terminal.