Audio01

Members
  • Posts

    19
  • Joined

  • Last visited

Recent Profile Visitors

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

Audio01's Achievements

Noob

Noob (1/14)

4

Reputation

2

Community Answers

  1. Thank you! But it's still in the AWS server (as I mentioned, I found it thanks to the Internet Archive / Wayback Machine): https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.3-x86_64.zip There's no link or mention anywhere in the Unraid webpage anymore (was until a few days ago).
  2. Hi, I need it because I would like to give AFP a try. SMB is practically useless with macOS (very very slow), and NFS is a mess to use (and no "simple" permissions per user basis). Unraid resulted in a very frustrating experience so far. I already found unRAIDServer-6.8.3-x86_64.zip with Internet Archive / Wayback Machine: https://web.archive.org/web/20220223192953/https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.8.3-x86_64.zip BTW I can't believe that Lime Technology doesn't have a repository of all Unraid versions. Being a Linux-based server solution, where many users would expect some basic structures/principles and safeguards, I just don't understand it. Cheers! EDIT: Yes, I already tried all the possible suggested tweaks in the server side and client side. Nothing really improved SMB performance in macOS accessing an Unraid server. With SMB over Gigabit LAN I'm having 10-30 MB/s transfer rate (sometimes just a few KB/s!), maybe some 60 MB/s peaks, but with periodic stalls. With NFS I always have 100+ MB/s with 125 MB/s peaks, but I can't use it because it's very unpractical and convoluted.
  3. Hi, I'm trying to download version 6.8.3 but it isn't in the download section anymore! Is there any repository with all previous Unraid versions? Thanks!
  4. Hi, please could someone explain step by step how to configure and connect to a NFS share from macOS? I'm having the same results as the previous post. Thanks!
  5. Hi! the problem is not the network. I repeat: I can transfer from Windows to Windows, Mac to Mac, Mac to Windows, Windows to Mac, always saturating the Gigabit connection (100-125 MB/s). The problem is only with Mac to and from Unraid server. Not any other combination, not Windows to and from Unraid. I'm using a UDM-Pro router/switch, working perfectly. Not using VLANs, nothing fancy, nothing strange. Just plain interconnection between machines. The network is completely out of question, the iperf tests give complete saturation of Gigabit from and to any of the computers.
  6. Hi, so what's your hardware specifics and tuning for the Unraid server? I already tried all SMB configurations suggested here, no change. My systems' specifications: Server computer: Xeon E3-1281 v3 (3.7 GHz 4 core with Hyperthreading), 32 GB RAM, 4 x 6 TB WD Red Pro (7200 RPM drives), now running Unraid 6.10 RC8 macOS Client computer: Mac Pro (6,1), Xeon E5-1650 v2 (3.5 GHz 6 core with Hyperthreading), 64 GB RAM, 1 TB SSD, running macOS 10.14.6 (Mojave). Windows client computer: Intel Core i7 8700K (3.7 GHz 6 core with Hyperthreading), 64 GB RAM, 1 TB SSD, running latest revision of Windows 10. All conected with Gigabit Ethernet, using Unifi networking gear.
  7. What I still don't understand, why it would be a problem only with macOS? Doing the same exact transfer with a Windows machine to the same server running Unraid gives me much better performance. At least double and it doesn't stall every few seconds. When I mean stall, I'm saying that there's practically no transmission between the macOS system and the Unraid server. It just transfer a few KB/s!
  8. Just for the record, I just updated Unraid to 6.10 RC8, did some testing, nothing changed.
  9. Yes, I'm writing to an uncached user share. Which would be the problem? I'm not seeing high amounts of CPU core utilization (nothing moves over 10%) or disk throughput saturation. The culprit seems to be the SMB implementation. If I copy files from a Windows machine to the same uncached user share in the Unraid server, there's no problem, the performance is ok. Also the culprit is not macOS, I can copy files from a macOS machine to another and always results in top performance. The same from macOS to Windows, and vice versa. The slowness is only between macOS and Unraid. Just for clarification, I'm always using SMB for all these shares/transfers.
  10. Hi, thank you for the answer. Already tried that configuration, didn't change anything. Still the transfer speeds are very slow and intermittent. The transfer rate goes from a few KB/s up to 40 MB/s, and very rarely a little more. But it doesn't compare at all with transferring from a Mac to another Mac machine, or even another Windows machine for instance. Any other solution? Should I try some of the 6.10 RC versions? Should I downgrade to 6.8.3? (BTW I'm on Unraid 6.9.2). Should I discard completely Unraid and look somewhere else?
  11. Hi, I already watched a bunch of Linus Tech Tips (basically promoting it), another bunch of tutorials in YouTube (like the Spaceinvader One's). Everything looked fine and from every perspective Unraid was the best option for a DIY server. I paid my license, etc. But it looks like nobody mentions the "elephant in the room": using Unraid with a Mac is practically useless. The SMB transfer speeds are abysmal! And no, the problems isn't macOS. For example, If I copy a folder from one Mac system to another Mac system (obviously using SMB) the transfer speed is great! Over Gigabit Ethernet it never goes down 90-100 MB/s and most of the time is over it. Trying to do the same with a SMB share in the Unraid server (a good performing Xeon computer, with fast storage) the speeds are 30-40 MB/s and stalls for periods of time. The same folder from Mac to Mac takes 1-2 hours, the same folder from Mac to Unraid server reports 10 hours or more!!! What the heck??? Please, I already looked for solutions everywhere. Nothing really improved the slowness. I need a definitive answer, does this product (Unraid) is really compatible with macOS or should I look somewhere else? Thanks!
  12. Hi, just a quick update... I tried updating the bootloader, changing the machine version, even reinstalling Mojave with the updated Macinabox app (docker + scripts)... nothing worked. The problem is with Mojave itself, it receives the ACPI shutdown request, but instead of shutting down, it displays that annoying dialog. The QEMU agent doesn't seem to work. It isn't running, and if I execute it, nothing happens. No error, not a single message (although there're some basic logs without much info), and still the agent doesn't come alive. Looks like it's a bug that never was fixed. I'm surprised that macOS (since Mojave, I guess) comes with a built-in QEMU agent. When I was looking for information there was no mention of it. Now that I searched for "AppleQEMUGuestAgent" I found some (few) posts about it. Now, I tried Installing Big Sur and also Catalina. Stopping / shutting down the VM works 100% right! Thank you @ghost82 for your help, really appreciated!
  13. Hi, is the VM power management working correctly with this kind of installation (i.e. with Macinabox)? I installed Mojave, everything works fine, except the "Stop" (shutdown) of the VM. If I try to "Stop" the VM from the webUI, or even issuing a shell command "virsh shutdown", only the "Restart / Sleep / Cancel / Shut Down" dialog in the guest macOS appears, and no automatic shutdown happens, ever. It just get stuck there. So there's no graceful/automatic shutdown posible, as explained in this post: Any help really appreciated! Thanks!
  14. Hi again, thank you for your quick answer! I used SpaceinvaderOne's Macinabox app (docker + scripts) for the installation and setup: I'm on Unraid v6.9.2 Stable, running on a Xeon E3-1230 V2 processor. Installed macOS 10.4.6 (Majove). I can't use Big Sur or Monterey. machdep.cpu.features in guest macOS shows me VMM support. The bootloader is Opencore v0.7.0, the one installed by Macinabox. I tried searching for QEMU guest agent support in macOS and didn't find anything relevant. This is the xml of the VM. The Q35 is v4.2. About the agent, I'm not 100% sure. Is anything wrong in the xml? <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'> <name>Macinabox Mojave</name> <uuid>cf1cb8db-d41c-401f-abfd-ed5ca27d4878</uuid> <description>MacOS Mojave</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="osx"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='4'/> <vcpupin vcpu='2' cpuset='1'/> <vcpupin vcpu='3' cpuset='5'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/cf1cb8db-d41c-401f-abfd-ed5ca27d4878_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none' migratable='on'> <topology sockets='1' dies='1' cores='2' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='utc'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Macinabox Mojave/macos_disk.img'/> <target dev='hdc' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <controller type='pci' index='0' model='pcie-root'/> <controller type='pci' index='1' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='1' port='0x10'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/> </controller> <controller type='pci' index='2' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='2' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/> </controller> <controller type='sata' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/> </controller> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:be:22:55'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-usb'/> <qemu:arg value='-device'/> <qemu:arg value='usb-kbd,bus=usb-bus.0'/> <qemu:arg value='-device'/> <qemu:arg value='************************'/> <qemu:arg value='-smbios'/> <qemu:arg value='type=2'/> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/> </qemu:commandline> </domain>
  15. Hi! Please, could you give more information about how to do this? Is there any mechanism to run a script earlier (not late) in the shutdown sequence? Thank you!