Jump to content


Popular Content

Showing content with the highest reputation on 03/05/20 in all areas

  1. 2 points
    Why did you start a new thread for this? I have merged your threads.
  2. 2 points
    Limetech is the best! I can't say enough for the transparency of this company! Thank You! I have been running unRAID as a daily driver for over a year now, and it has been GREAT, if it quits working properly because of a security breach or something, well that is okay, i'm sure it would get fixed as a top priority. unRAID isn't an enterprise grade product, though I think it performs better than some, and there aren't thousands of workers behind the scenes. If you want that level of stuff, then you have to deal with constant forced updates and go pay the premium for it. I will back this company for as long as it stands!
  3. 2 points
    According to the X470D4U manual it does support DDR4 3200 RAM modules if you are using only two memory slots. Matisse Ridge is Ryzen 3rd generation. In most unRAID uses, you will not see much difference at all (if any) between 3200 and 2666 Mhz RAM speeds. By the way, you should NEVER overclock your RAM in a server. That's asking for instability. You are tying yourself up in knots and overthinking many things. Figure out what you really want/need you server to do and pick what appears to give you most of what you need. I don't have any experience with Ryzen systems and I just upgraded my system to the latest Xeon CPU, but either one (or even an i5 to a lesser degree) will work well for you based on your list of wants and needs in your first post.
  4. 1 point
    Parity Check Tuning plugin The Parity Check Tuning plugin is primarily designed to allow you to split a parity check into increments and then specify when those increments should be run. It will be of particular use to those who have large parity drives so that the parity check takes a long time and who leave their Unraid servers powered on 24x7. The idea is that you can specify time slots when the increments should be run and these can be chosen to be at times when the Unraid server is likely to be idle. As an example on my system I have a 10TB Parity Disk and an uninterrupted Parity Check takes about 30 hours to complete.. I have my normal scheduled parity checks set to run monthly. By using this plugin to run using 3 hour increments the elapsed time extends to 10 days (10 x 3 = 30) but I do not notice any impact on my normal use as the increments are run when I am not using the system. Once enough increments are run to complete the scheduled parity check then no further increments will be run until the time for the next scheduled check comes around. The plugin also allows other types of long-running array operations to be Paused and Resumed. These are Parity-Sync/Disk Rebuild and disk Clear operations. However since pausing these is less likely to be something the average user wants these can be individually controlled. For those who have problems with cooling on their Unraid systems it is also possible to set array operations to be Paused if the disks reach defined temperature thresholds and then Resumed when they cool down sufficiently. A much better solution is to have your Unraid system set up so that the cooling is sufficient to never let the disks overheat, but for some people this is not always practical. The plugin will update the standard parity-check log to accurately reflect the duration and speed of parity checks to take into account that the check was run in increments as well as recording the number of increments, the total elapsed time and the type of check run. The Settings page is added as an extra section to the Settings->Scheduler page (see the screenshot below) in the Unraid GUI as this seemed the most logical place for it to appear. Debug/Testing logging feature If you enable the option for debug logging then you will see additional entries appearing in the syslog about how this plugin is functioning internally. All these entries will include the word DEBUG so It is clear that they have been activated by turning on the Debug logging. This feature is primarily aimed at giving users a sense of what the plugin is doing under the covers for any users interested in such matters. In addition the logging level can be set to TESTING if trying to track down any suspected bugs in the plugin operation. This is primarily used during plugin development but can also help tracking down any issues that might be reported by users. It can be very verbose so users should not normally leave this option enabled. When this option is set to Yes then you are offered an additional option of Hourly for the frequency at which this plugin should pause/resume parity check increments. This was added primarily to help with testing and to help track down any issues that users might experience in using the plugin. Early feedback ahs suggested that users new to this plugin can use this feature as a way of getting a feel for how the plugin operates. Server Shutdown A feature has been included that allows users to set a temperature threshold for their array and cache drives that if exceeded will force the server to start its shutdown sequence. The prime Use Case for this is seen as protecting the disk drives in the event of the servers cooling failing for some reason. If activated this check runs even when there is no array or cache operation active. Command Line (CLI) options When this plugin is installed it adds the 'parity.check' command to the system which makes the following capabilities available from the command line: Usage: parity.check <action> where action is one of pause Pause a rumnning parity check resume Resume a paused parity check check Start a parity check (as Settings->Scheduler) correct Start a correcting parity check nocorrect Start a non-correcting parity check status Show the status of a running parity check cancel Cancel a running parity check Built-in Help The settings page for this plugin has built-in help to describe the meaning of the various settings. You can click on the description text for any particular setting to toggle it on-/off for that particular setting or you can turn it on/off at the page level by using the standard Help toggle in the Unraid GUI. Suggestions for improving the wording or expanding on the provided text are welcomed as it is not intended to produce any separate documentation. Planned Enhancements All originally planned features are now implemented. Suggestions for other possibilities are always welcomed. Wish List This a holder for "blue sky" ideas that have been expressed for which there is no idea if it is even technically possible. They are kept here as a reminder and for others to perhaps expand on, and even perhaps come up with ideas for implementation.. Auto detect idle periods: The idea is that instead of the user having to specify specific start/stop times for running parity check increments the plugin should automatically detect periods when the system is idle to resume a parity check. This would need the complementary option of automatically detecting the system is no longer idle so that the check can be paused. Avoid running parity check if mover is running. Mover and parity Checking severely degrade each others performance. Some way of removing (or at least minimising) this conflict would be desirable. Thee are lot of permutations that need to be thought through to come up with a sensible strategy. It may be simpler for users to simply schedule the parity Check Tuning plugin to run its increments at a time when it is known the mover is not scheduled to be running. Stop docker containers during a parity check. The ability to schedule the parity check to stop specified docker containers prior to check running and restart the docker containers after the check is paused or completed. A workaround for this would be to use the User Scripts plugin to do this although an integrated capability would be easier to use. Resume parity checks on array start. The current Limetech implementation of pause/resume does not allow a parity check to be started from any point except the beginning. If the ability to start at a defined offset is ever provided then this could be implemented. Partial parity Checks: This is just a different facet of the ability to Resume parity checks on array start where you deliberately set the system up to perform part of a parity check with reboots in between the parts. Feedback Feedback from users on the facilities offered by this plugin is welcomed, and is likely to be used to guide the direction of any future enhancements. It will be interesting to hear how useful users find this plugin to be in the normal running of their system. Please feel free to suggest any changes that you think would enhance the experience even if it only rewording of text . Requirements Unraid 6.7 rc3 or later Community Applications (CA) plugin. It is expected that this plugin will be installed via the Apps tab (i.e. the Community Applications plugin) and the appropriate template has been prepared to allow CA to handle it tidily. Installation The parity Check tuning plugin is available for installation by using the Community Applications plugin. If you navigate to the Apps tab and search for 'Parity Tuning' this plugin will show up and it can be installed from there. Once the plugin is installed then if you go to Settings->Scheduler in the Unraid GUI you will see an extra section has appeared that allows you to specify the settings you want to be used for this plugin. Restrictions/Limitations This plugin does not initiate a parity check - it only provides facilities for pausing/resuming them according to the specified criteria. If there is no parity check running during the timeslot specified for an increment then this plugin take no action. If the array is stopped for any reason then the current progress of a running parity check is lost. This means that the next time the array is started the parity check will need to be restarted from the beginning. This is a restriction imposed by the current Limetech implementation. The plugin is designed so that this restriction can easily be removed if Limetech can provide a way of starting parity checks at a specified offset rather than starting all parity checks from the beginning.
  5. 1 point
    It is time to start a new thread and share my tips, and we can discuss here. For those who don't have much information, see SpaceInvaderOne's **VIDEO GUIDE** How to Install MacOS Mojave or High Sierra as a VM There is not much information about hackintosh in VM, so I will not make an installer guide but some important tips which everyone had miss. If you wanna get quick start(with opencore), I made a github repo to help people. *** if you like those tips, don't hesitate to push the button "like" below this thread, thanks *** 1. CPU 1.1 CPU Model Every Tutorial told us to use Penryn but didn't tell us why. After some digging I've found that CLOVER had some limitation when using simulated newer cpu family than Ivy-Bridge. So If u have older clover, you should use Ivy-Bridge instead of Penryn (I will explain later in performance part)(opencore do not have such problem). with lastest clover (5093) and opencore: If you have Intel Process, you can just use host-passthrough or newer cpu family like Skylake/Cascade-Lake to get most features available. If you have AMD Process, it can't be passthrough directly yet in clover, but is possible when using latest opencore (0.5.2). see this PR I've made. 1.1.1 Why Penryn is recommanded before After digging a lot of code, I have some conclusions why they recommanded Penryn as prefered CPU Model: Penryn is classic, and it missing some features compared to newer generation, which lead to a similar situation with VM. Penryn do not have a msr 0x00000198 leaf to read the perfstatus (like bus ratio, cpu frequency) which the same as a VM. Penryn do not have a msr 0x35 leaf to read topology structure, which also most hypervisors haven't implemented yet.Instead, the MacOS will try to get the topology from acpi when it detect a Penryn process, which the same as a VM. Some bootloaders do have some compatibility issues when using a newer generation in a VM, some causing dividing by zero errors(They can't get correct frequency from acpi or msr, so they may be zero). Some articles have outdated so long from now. It don't have some cpuid features like avx/avx2/bmi/fma so MacOS won't recognized those features even thought you just passed through. 1.2 CPU Topology If you are not using Penryn or a wield cpu thread count, it is safe to remove the cpu-topology line in xml to avoid problems. <cpu mode='host-passthrough' check='none'> <!-- REMOVE THE LINE <topology sockets='1' cores='3' threads='2'/> --> </cpu> I've found it is related to the lack of virtualization support in clover and opencore, also the MacOS. If you using a model newer than Penryn, they try to get the topology from a MSR which the hypervisor(QEMU/KVM) not implement yet, causes some dividing by zero error, and the system won't boot. Update: It is safe to declare the topology of your cpu without any performance reduction now. All you have to do is add one single patch to avoid a x86_validate_topology error (MacOS will compare the acpi topology and the one reading from msr 0x00000198(which most hypervisors don't have), then the error occured.) Although there will still some issues in virtualization support in clover and opencore(like TSC/FSB frequency reading and topology, many hypervisors didn't implement some important msrs like 0x35). Details can be found here(which I submit a PR to opencore to support hypervisor.I'm not familar with svn so clover may not support in near future). 1.3 CPU Performance 1.3.1 Important cpuid features If you gonna get a nearly bare metal cpu performance, you should pass some important cpu features in xml.I will list some and you may try to find which feature your cpu is supported. AVX: without this the newer MacOS will not boot FMA: it is important for metal support AVX2 INVTSC: without this the newer MacOS will not boot BMI1 BMI2 BTW, there is no more need to add "vmware-cpu-freq=on" in the xml because it is default to be on in latest QEMU. 1.3.2 Newer CPU Model is recommanded so MacOS will recognize the features correctly And also, it is important to use a more newer cpu model to make MacOS recognizing the feature correctly. IvyBridge is the bottom line(This is why Penryn is not recommend any more, when you using Penryn, MacOS won't recognize some important feature like avx2 amd fma, then some application will not using those features). 1.3.3 How to check whether the features are recognized correctly in MacOS 1.3.4 Other flags should be notice You should passthrough the "+hypervisor", "+invtsc" and "kvm=on" along with others features. MacOS/opencore will read "0x40000010" to get TSC/FSB frequency only if the hypervisor flag is exposed. QEMU only exposes "0x40000010" leaf when "kvm=on" and "invtsc" is passthroughed. 2. GPU 2.1 GPU assignment It should be noticed that unRaid did not set GPU and its audio correctly by assigning them in same bus but different function, you have to mannaully adjuct it to make it work. IT IS IMPORTANT FOR METAL AND HDMI AUDIO! AND SOMEHOW IT IS RELATED TO AMD PCI RESET BUG! <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/domains/mojave/Sapphire.RX560.4096.170419.rom'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0' multifunction='on'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x2d' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </hostdev> As you can see , the gfx and graphic audio should be put in same bus (0x01) but different funciton (gfx in 0x0 and audio in 0x1), otherwise the HDMI audio will not work (even with Lilu/WEG/ALC). If you misconfigured it, it will lead to some unknown issues: The HDMI Audio will not work at all If you using a AMD card, you may face the "pci reset error 127" (seems the driver will reset the grahpics in a wrong way) it also makes onboard audio recognized incorrectly. (AppleALC will confuse which audio is truely onbaord, details can be see here) 2.2 GPU Metal Support Every tutorial told us to use Lilu/WEG to make graphic work and get metal support, but I've found Lilu doesn't work in QEMU/KVM at all! I've submit an issues to Lilu, and Lilu add QEMU support after 1.3.9. You have to use this version or newer to make Lilu/WEG works. (This is unofficially released yet, so use the attachment in this thread). You do not need any patch after using the Lilu I mentioned, the Lilu and WEG do the magic tricks. 2.3 GPU DP/HDMI audio Lilu/WEG/AppleALC only works with correct bus assigned gpu and audio so see part 2.1. If you set under the instruction I've made, then check the other hackintosh audio guide to find next step. 3. Networking There is no much choice of nic in hackintosh VM: e1000-82545em, vmxnet3, virtio, passthrough 3.1 e1000-82545em Advantage: Most stable and OOB, recommanded. Disadvantage: The nic will not work in installing a MacOS(seems the installer did not have such driver).So when installing the MacOS, you'd better change it to vmxnet3 or add a second vmxnet3 nic to get network working. 3.2 vmxnet3 Advantage: Better networking throughput (3Gbs~5Gbs) sometimes Disadvantage: quite buggy ( icloud/apple store not work or lower upload speed). 3.3 virtio apple add virtio-net support after catalina, I've found a way to make it work but now, See this post. Advantage: 30Gb/s Disadvantage: it is buggy too. To use virtio net, you have to do two thing: 1. hotplug virtio ethernet instead of predefined 2. boot args with debug=0x100 and keepsyms=1 3.4 passthrough 3.4.1 ASUS XG-C100C It is known to be problemic when using this nic, but after catalina, you will get native support after update the latest firmware. 3.4.2 X540-AT2 and X550-AT2 3.5 nic xml assignment You should assign the nic in bus 0x00 and slot 0x0y(y is number ,recommand to be greater than 5 which not likely occupied by other devce) to make nic recognized by macos as builtin .This is important to make AppleStore and iCloud work. 4. onboard Audio It's important that: 1. you make the graphics audio correctly by step 2.1 2.change your onboard audio from bus 0x0y, to bus 0x00 and slot 0x0z (where x, y means integer. This will make your onboard audio built-in, so AppleALC can easily handle it. detail and discussion can be found here. <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1b' function='0x0'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </hostdev> the snippet set the onboard audio (00:1b.0) in bus 0x00, slot 0x02, and this makes the audio built-in. 5. USB working on it now. 6. Others 6.1 SMBios When using kvm, the MacPro7,1 and iMacPro1,1 is preferred, because we don't have iGPU and these two SMBios is super match for us. Update 2019.10.29: MacPro7,1 is no longer prefered as MacOS not officially release this product so will lead to some unpredictable problems. 6.2 Exceptions Lilu-1.3.8-DEBUG.zip
  6. 1 point
    Self hosted remote support would be amazing. https://www.connectwise.com/software/control/download https://hub.docker.com/r/kenayagi/screenconnect/
  7. 1 point
    @Burizado Thanks! Yep, I contacted ASRock after I bought the combo to request the beta BIOS. They replied fairly quickly with a link to download. Also, while not directed to me, both VT-x and VT-d were enabled by default in the BIOS. The problem I made was configuring the BIOS first then flashing. Some of the settings didn't seem to stick (explicitly enablling the onboard graphics, for example). I'd recommend flashing first thing, then configuring. Flashing is super simple. Throw the binary onto a flash drive, plug it in, and select the option for Instant Flash during POST.
  8. 1 point
    Mitigations that are handled via microcode will still show as being mitigated. Those shouldn't affect performance anyways
  9. 1 point
    Binhex mentioned Mullvad in the GitHub and I can get an offer on Surfshark where it's 80% off and cashback.
  10. 1 point
    x4 is more than enough for 4 spinners. Also note that the JMB controller is PCIe 3.0, so approximately same bandwidth as an x8 PCIe 2.0 slot, assuming board supports PCIe 3.0 obviously. Some performance numbers in this thread.
  11. 1 point
    I assume you mean disk5, if so a few reallocated sectors can be OK, if it remains stable, though it's never a good sign, especially on a fairly new disk, you should at least run an extended SMART test, as for warranty you'll get a refurbished disk, and those are a crapshoot, sometimes the devil you know...assuming the extended SMART test is OK. Regarding the data in case you decide to replace it, you can use the server with the emulated disk for a few days, especially since you have dual parity, or rebuild to a spare.
  12. 1 point
    With Unraid 6.8 IPv6 will be disabled on the interface when it is configured as IPv4 only.
  13. 1 point
    Hi, can you try running the plugin from the command line to check the output ? Something like killall controlr /usr/local/emhttp/plugins/controlr/controlr -port 2378 -showups run both commands on the command line and post the output here.
  14. 1 point
    An enterprise build has features that you won't find on consumer build e.g. PSU monitoring, IPMI, intruder protection, encryption, etc. These features will be available on enterprise motherboards, which require enterprise CPU (e.g. Intel Xeon and AMD EPYC). Even when you compare an Intel Xeon and an Intel i7 of exactly the same feature-set, the Xeon CPU is more expensive just because of market segmentation i.e. you have less money than [insert the name of a corporation]. As for the motherboard, yes, go for the other 2 examples instead of the Aorus Elite as long as the feature set match your requirements. Picking a Gigabyte motherboard with 2 x16 slots is defeating the purpose. (X570) mobo with 3 x16 slots will have the 3rd slot running at x4 speed (i.e. slower). So if required, you can put a low-end GPU in this slower 3rd slot and save the 2x fast slots for other things. Mobo with 2 x16 slots only have fast slots. A vbios is likely required to pass through a single GPU to a VM. There are 2 methods to get a vbios (both methods require some Hex editing to work (watch SpaceInvader One Youtube videos) but that is beside the point): Dump your own, which requires a 2nd GPU to boot Unraid with before dumping Download from Techpowerup The vbios must match the exact brand, model and revision. That means the version on Techpowerup may not match your GPU exactly. Dumping your own is the only way to ensure it's the right one. Once you have dumped the vbios and create a VM that works with the passed through GPU, you may be able to remove the low-end one and run your server with just a single fast GPU. It depends on the exact hardware so it's impossible to tell in advance. So IF you need a low-end GPU for it to work, having the ability to use a slow PCIe slot for the low-end GPU for Unraid to boot with (and reserve the fast slot for the fast GPU that would be used for the VM), in addition to NOT needing to physically swap GPU slots, makes life easier. And that's why I said you can borrow the low-end from a friend but budget for "the possibility" of needing it. Also, you asked about "can Unraid boot". Unraid will boot with a single GPU. We are talking about passing that GPU to a VM. On a side note, that's also why it's usually easier to pass through a GPU on an Intel build with iGPU. The iGPU serves as the low-end so dumping vbios is trivial.
  15. 1 point
    Glad you got your speeds back!
  16. 1 point
    Intel monopolised the CPU market, both enterprise and consumer, for decades until AMD came back with Ryzen. So that's why Intel is already generally more expensive than AMD. Then you are comparing AMD consumer CPU vs Intel Xeon line (i.e. enterprise clientele), of course the Xeon build is (a lot) more expensive. The reason why AMD has risen was because Ryzen offers better performance than Intel for cheaper. Also for your X570 motherboard, don't pick the one with only 2 x16 slots (i.e. the long ones). Go for the one with 3 x16 slots. It would be defeating the purpose to get Gigabyte motherboard for the Initial Display Output functionality but then cut off 1 of the possible 3 x16 slots (i.e. one that can be used for a GPU). And budget about $30-$50 more for the possibility of needing a low-end GPU for Unraid to boot with (or borrow it from a friend) so you can dump the vbios.
  17. 1 point
    Thanks for the info, I have done this and changed the required settings in ltConfig. I can confirm that the speeds are now much better in the region of 45 - 50MB/s which is the max speed of my connection.
  18. 1 point
    We can now using stock OVMF from qemu (unraid) instead of using third-party patched OVMF by using apfs.efi and opencore. Detail can be found here. So there is no need maintain another OVMF-VARS/CODES any more.
  19. 1 point
    @swallace It is very strang, you don't even have metal support according to your screenshots. Check this: 1. What is your Lilu/WEG version? Don't use clover updater, manually download from github and place them into kext/others. 2. What is the BIOS version of your graphic?Download from techpower and add it to your xml. 3. Then check your Lilu/WEG is loaded(you can get the log from hackintool)
  20. 1 point
    Sorry for not being around for a while. Real life catches up sometimes. Unfortunately, I don't have the time required to fix additional issues that may come up with this app currently. For the most part, it should be working fine. The Statistics part has always kind of been a bit of an issue, since it interfaces with Tautulli, and I can't update the app anytime the Tautulli dev decides to change something about his that may break NowShowing. This app was originally written to be useful before other apps like Tautulli and Ombi integrated their own newsletter/email update systems. But now that they do similar newsletters as this NowShowing app, I don't feel this app is probably needed as much as it once was. Anyways, for those that it still works for and use it, great. For anyone new, I might recommend using one of the aforementioned apps that are more regularly maintained. Thanks all!
  21. 1 point
    What are some symptoms of missing QEMU Support? I googled it and it sounds like it would cause issues with running VM's but I haven't noticed any issues, granted I only have one MacOs VM running. I'm currently running unraid 6.8.2 on the following hardware: Gigabyte TRX40 AORUS XTREME Threadripper 3990x The mobo has dual 10gbps ethernet. I'm currently only using one of them ( haven't got around to configuring link aggregation yet ), but its recognizing both of them. I'm also using an nvidia GTX 960, ( Haven't decided on the new GPU yet ) and was able to get that handling hardware transcoding in a plex docker container via the Unraid Nvidia Plugin. All of this to say I haven't noticed any issues with sTRX40 and unraid. But to be fair this is my first unraid server, and I've only had it running for a couple weeks so maybe there may be things I just haven't run in to yet.
  22. 1 point
    From the troubleshooting section of the quickstart guide:
  23. 1 point
    TO my knowledge it will with some limitations.. Limitations include QEMU isn't fully supporting the 3k series yet and without the 5.x kernel temp monitoring will be fubar..
  24. 1 point
    I have split your post into its own topic because it isn't likely that moving files around is the correct approach to your problem. Might even be that there is nothing wrong with your disk. Go to Tools - Diagnostics and attach the complete Diagnostics zip file to your NEXT post. Since some of your ideas are definitely wrong, please don't do anything without further advice.
  25. 1 point
    Do you do all the things I've mentioned? Make sure your smbios is MacPro7,1/iMacPro1,1 Using Latest Lilu/WEB Put the audio and gfx in same bus If you do so, post your screenshot of sysinfo and your graphic vendor I'm using opencore but 0.5.5, some problem I can't solve, maybe your have some ideas? My 10gb nic not work in bare metal hackintosh(smalltree driver said there is "cable unpluged", but works well in a VM... I can't get hotkey working neither VM nor bare metal.... With PollAppleHotKeys=yes and KeySupport=yes. I think maybe I should make a git repo for hackintosh VM user to build a bare metal hackintosh.
  26. 1 point
    Is there an ETA on a 5.4 LTS kernel? I need it for the threadripper server I'm building with an ASRock sTRX40 Creator MB. My current 8-core Xeon is doing OK, but I plan on needing a beefier chip in the near future as I'm hosting a VM for a Linux distro build server.
  27. 1 point
    I did the same thing as you did in my first attempt to set this up. Here's what you need to do: Add a path like below, except use "/mnt/user/Download/complete/" Change your Sonarr and Radarr paths to "/torrents".
  28. 1 point
    Looks stable with qemu 3.0 now I added "pcie_no_flr=1022:149c,1022:1487" to boot parameters and changed qemu to 4.2 on one of my w10 VM .......... so we will see after some day how it works.
  29. 1 point
    The fix common problems plugin handles that, and shortly a new update to CA will also handle the most egregious must-be-seen notifications.
  30. 1 point
    For the time you can enter: 'su minecraft' and then connect to the screen session (this is only a workaround a new update is coming soon) EDIT: Please try this from the server console and not the container console: 'docker exec -u minecraft -ti <Name of your MCContainer> screen -xS Minecraft' (without quotes) to exit the screen session press CTRL+A and then CTRL+D or simply close the window in the first place (don't press CTRL+C since you are going to shutdown the MC server).
  31. 1 point
    Nonsense. So much more has to change first, support for Multiple Arrays. You can't have realistic protection with only 2 Parity Drives for higher drive counts.
  32. 1 point
    Something else I wanted to add, as long as we're talking about security measures in the pipe: we are looking at integrating various 2-Factor solutions directly in Unraid OS, such as google authenticator.
  33. 1 point
    Thanks! Here you go!
  34. 1 point
    I use Parity Tuner to Only run from 12AM-6AM which normally takes 2.25 Days from start to finish I use Mover Tuner set to NOT move files while Parity check is running I have CA Backup set to run on the 5th of every month I have SSD Trim setup to run Daily at 3AM I have all my scripts set to run whenever they are scheduled, but not during Parity check I have Plex set to scan my drives at 6:30AM-8:00AM
  35. 1 point
    Nothing to install. Extract mprime from http://www.mersenne.org/ftp_root/gimps/p95v2810.linux64.tar.gz and save it on the flash drive then cd /boot mprime and answer the questions and then watch your cpu utilization and temperatures climb on unRaid's dashboard. Text files are created at the end indicating the results
  36. 1 point
    In general, you want the latest version that works. ACPI v3.0 adds SATA and PCI Express support, as well as numerous other features (processor performance and throttling etc) and numerous bug fixes. The latest version is v3.0b. If you don't mind the time, boot with each ACPI version, give the system a simple workout (copy a small file from each drive, then copy a small file to any one drive), then capture the syslog (label it with the ACPI version). I think you will know very quickly if there is a problem with a version, and I'll be happy to compare the 3 syslogs and look for other anomalies or improvements.