Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

5 Neutral

About Zer0Nin3r

  • Rank
    Advanced Member


  • Personal Text
    We're looking down on Wayne's basement. Only that's not Wayne's basement. Isn't that weird?

Recent Profile Visitors

276 profile views
  1. I was playing around with the setting despite reading the vfs_fruit package documentation and I had it turned on for two shares. I haven't played extensively enough to notice any file errors. However, any shares I mount within Mojave, I cannot access the sub-folders. They all read 0kb and have a "red negative icon" on them. I'm turning it off for now. I thought it might help with Spotlight searching on network shares...wishful thinking on my part.
  2. If the link I pulled is from the "official" site for Monero, then this should be what you are looking for: https://ww.getmonero.org/resources/user-guides/mining_with_xmrig_and_docker.html I found the guide by going to their site under Resources > User Guides > Mining > Mining with Docker & XMRig Who wrote the guide is beyond me especially since they refer to themselves in the guide. I'm sure you can message some of the Monero devs and inquire more about the author of the guide. I don't know anything about XMRig, but it looks like their code is up on GitHub, so I'd dig around in their source code for anything dubious. The same thing goes for looking at a Docker image. It looks like the "official" software from the monero developers has a function to solo mine built into the software. Have you thought about starting there? Maybe the function is also built into their CLI It looks like the CLI version of their software can mine so, you might be able to build a docker image using the Alpine docker image as your base. A quick search on Docker Hub shows me that kannix's docker image is the most popular. You will want to examine the Dockerfile for more clues. in kannix's case he's chosen Ubuntu for the OS install — which, if you want a lean install, you should go with Arch Linux (I know @binhex is a fan of Arch Linux due to his Docker builds.) Although, after some digging around it looks like Alpine docker is even leaner. However, in looking at his GitHub repository, someone filed a bug report stating that "Did you know that your container was used by someone else to make a virus?" but then doesn't reply when kannix inquires for more information. Not only that, but kannix's response doesn't instill confidence. Moreover, kannix likes to fork branches instead of developing code for the main branches he's forking off of; for what reason, I don't know. Even though he explicitly says it in his Dockerfile read me, you will see that if you run his docker image with the default settings, that you will be mining monero for him. With that being said, there could be many other maintainers out there throwing their version of mining software that may or may not throw kickbacks to the author — much like how people share referral codes on social media. So, check out some Dockerfiles from devs that you already trust to see what they are doing with the files and also check out some tutorials on how to create and wrap your own dockers. Hopefully that will help you decide on which dockers to install. And like I said before, take a look at the program's source code for clues. Thanks for the interesting question and for the boondoggle. I might just have to tinker around myself for fun one of these weekends.
  3. Thanks for the feedback. I appreciate it @steve1977. I'll stick with the i440fx for now since it's working for me. I don't feel like making a backup of the vm, rebuilding the drivers upon boot, and tinkering with the vm. But in looking at the documentation for both machine types, logically it would make sense to build Windows 10 machines with Q35; the documentation out there needs to be refreshed, it's been a while. Good to know. I tried searching for something that says it in stone, but can't really find anything substantial — just what the conventional wisdom in the forums dictates. That being said, I asked my question again, since it's been several years since the conventional wisdom has been passed around and the documentation on CPU pinning didn't really give me much to work on; again information atrophy. I can attest this: Gaming on cores 16–31 with the Threadripper 1950x results in poor performance/FPS. Not sure why this is since the cores pinned should be purely on chip #2. I've tried with 6/8 cores and the FPS is lower than if I were to pin cores from the 2–15 pool. I've tried like hell to get pass-through to work on the EVGA GTX 1060 6G in Slot 01 and it simply wouldn't work for me. I tried even loading the VBIOS into the Unraid template with no success. It wasn't until I bought a cheapo card and threw it into the server that I was able to successfully pass-through my GPU; I'm passing through the GTX 1060 without having to dump the VBIOS and load it into the template. You know pass-through is working when you can see the GPU in your Windows device manager and it is not displaying any error codes. Additionally, you know pass-through is working when you can install the video drivers, reboot, and not see any error codes. You should see a "This device is working properly." in your device manager. Yes, there will be a degradation of graphics quality when game streaming. I am running Unraid in a headless state and using Parsec on a thin client for gaming with First Person Shooters in online multiplayer. I can tell the difference of quality when I look at the playback of my past matches. Moonlight seems to have a better picture quality than Parsec, but you cannot readily access the desktop or your other applications. Also, I seem to get better FPS with Moonlight than Parsec, but Parsec allows me to open and run Discord or any other application that I need to get to. @everyone: Please edit your posts with new thoughts/insight and throwing in a reason for the edit rather than creating multiple subsequent posts — it makes reading the threads easier and allows everyone to use their time more efficiently.
  4. I haven't ran into any issues of this sort with PUBG, Battlefield V, or Rainbow Six Siege. All the games have been working great with GPU passthrough (EVGA GTX 1060 6G) in Windows 10 Pro with i440fx-3.0. Occasionally, BFV will crash or experience some stutter, but I believe that's a problem with the game and not the Unraid + VM setup. PUBG uses BattlEye. And Ubisoft has ant-cheats to my knowledge. BFV...well the jury is still out on that one as EA/DICE uses FairFight which relies on server side statistical analysis, so...yeah.
  5. Are you noticing any performance improvements after switching to Q35-3.0.0? I've been happy so far with the gaming performance on i440fx-3.0 running BFV, R6, and PUBG. Maybe, I'll give it a try and report back. Also, I was trying to search on the forum, but is it imperative that we don't pin anything to CPU 0/1? I'm running a Threadripper and I think I would get better performance if isolating VM's to a single chip versus spreading the workload of the VM across the Infinity Fabric. Does Unraid OS specifically like the first CPU pinning slot? Or it doesn't matter as long as you leave a single core & hyperthread open for Unraid? === I also, want to link back to another thread that discusses Q35 and gaming performance so we have a cross-reference here.
  6. I'm definitely keeping an eye on the developments here and looking forward for this project to mature some more and come out of beta. At the moment, I have the Handbrake docker setup with thanks to SpaceInvader One. It was a little cumbersome to setup initially with tweaking here and there for my tastes and needs; it works. One thing that is lacking from the Handbrake hack is the ability to flag certain videos to not encode them and simply pass them through to Sonarr. For example, a nightly news show or late night variety show that automatically gets deleted after you watch it doesn't need to be encoded into h.265. The Handbrake workflow also doesn't check for h.265 and will re-encode the file regardless thus, being redundant with some loss to picture quality. Another thing that I will be curious to see are the encoding customization settings for Unmanic. The Handbrake GUI is something that I am familiar and comfortable with (although, it could use a little more K.I.S.S.) and I would like to see some of those features in Unmanic. e.g., sound/surround sound encoding/downmixing, video encoder speed, etc.
  7. @1812This is so clutch!! When you said to remove topology, I had no clue what you were referring to. It's as simple as removing the line: <topology sockets='1' cores='2' threads='2'/> from the xml file after toggling the CPU's that you want to assign to the VM. So again, thank you for the pro tip!
  8. Could the plugin version be incompatible with the version of Deluge that you're running? I recently ran into the problem of a pluggin/egg file (Copy Completed) not installing via Web GUI and the version that SpaceInvaderOne had was one version newer than the one I pulled from the Deluge site/forums. Not sure if this will help solve the issue, but try making your changes to the preferences using the Web GUI and Apply/OK them. Next, go Connection Manager > Disconnect > Reconnect > Stop Daemon > Start Daemon Stop/Start the Deluge docker I was running into an issue of the Plugin's settings were not being saved after stopping and starting the Deluge docker. Doing this, seemed to help me and I got the idea from here. Initially, I thought it might be a permissions issue as this was showing up in my log: WARNING: file 'credentials.conf' is group or others accessible So, I deleted the perms.txt file thinking that would solve the issue. I also, understood not to run the New Permissions (Located under Tools > New Permissions) on the /appdata directory as it will have a negative impact on any Docker containers — so, I didn't run New Permissions.
  9. Would this fix the Zen states warning in Fix Common Problems app? Honestly, I haven't experienced any perceivable performance issues with the Zen states warning that the Fix Common Problems plugin reports; the corresponding thread that the plugin links to doesn't seem to pertain to Threadrippers per say.
  10. Is there a benefit to the ~+27 C for some processors? I thought I shared a screenshot from the terminal showing the "four" temperature readings. Regardless, thank you for the informative response @John_M
  11. Report Findings: Dynamix Auto Fan Control is incompatible with the Threadripper 1950x running on a Gigabyte Designare X399. Only the CPU Temperatures are detected by Sensors command. This is after performing sensors-detect command and saying YES to all the prompts.
  12. Testing with a 1950x on a Desginare X399 So initially clicking on Detect didn't do anything. typing Sensors or k10temp into the field allows the plugin to pull in the temps. But, only two sensor readings. I have the latest bios installed for the Desginare X399. This command worked. Output: But I do not know what those sensors reading from. I do have three (3) wire temperature sensors that I attached to the motherboard that come with the Designare X399. Loading into the bios when I have a monitor attached, you can see all the temperature readings and fan readings. Just wished there was a way to get all of this data inside Unraid since I am running headless. Also is this relevant?: source: https://github.com/groeck/k10temp Kernel driver k10temp ===================== Supported chips: * AMD Family 10h processors: Socket F: Quad-Core/Six-Core/Embedded Opteron (but see below) Socket AM2+: Quad-Core Opteron, Phenom (II) X3/X4, Athlon X2 (but see below) Socket AM3: Quad-Core Opteron, Athlon/Phenom II X2/X3/X4, Sempron II Socket S1G3: Athlon II, Sempron, Turion II * AMD Family 11h processors: Socket S1G2: Athlon (X2), Sempron (X2), Turion X2 (Ultra) * AMD Family 12h processors: "Llano" (E2/A4/A6/A8-Series) * AMD Family 14h processors: "Brazos" (C/E/G/Z-Series) * AMD Family 15h processors: "Bulldozer" (FX-Series), "Trinity", "Kaveri", "Carrizo" * AMD Family 16h processors: "Kabini", "Mullins" * AMD Family 17h processors: "Ryzen", "Threadripper" Prefix: 'k10temp' Addresses scanned: PCI space Datasheets: BIOS and Kernel Developer's Guide (BKDG) For AMD Family 10h Processors: http://support.amd.com/us/Processor_TechDocs/31116.pdf BIOS and Kernel Developer's Guide (BKDG) for AMD Family 11h Processors: http://support.amd.com/us/Processor_TechDocs/41256.pdf BIOS and Kernel Developer's Guide (BKDG) for AMD Family 12h Processors: http://support.amd.com/us/Processor_TechDocs/41131.pdf BIOS and Kernel Developer's Guide (BKDG) for AMD Family 14h Models 00h-0Fh Processors: http://support.amd.com/us/Processor_TechDocs/43170.pdf Revision Guide for AMD Family 10h Processors: http://support.amd.com/us/Processor_TechDocs/41322.pdf Revision Guide for AMD Family 11h Processors: http://support.amd.com/us/Processor_TechDocs/41788.pdf Revision Guide for AMD Family 12h Processors: http://support.amd.com/us/Processor_TechDocs/44739.pdf Revision Guide for AMD Family 14h Models 00h-0Fh Processors: http://support.amd.com/us/Processor_TechDocs/47534.pdf AMD Family 11h Processor Power and Thermal Data Sheet for Notebooks: http://support.amd.com/us/Processor_TechDocs/43373.pdf AMD Family 10h Server and Workstation Processor Power and Thermal Data Sheet: http://support.amd.com/us/Processor_TechDocs/43374.pdf AMD Family 10h Desktop Processor Power and Thermal Data Sheet: http://support.amd.com/us/Processor_TechDocs/43375.pdf Author: Clemens Ladisch <clemens@ladisch.de> Description ----------- This driver permits reading of the internal temperature sensor of AMD Family 10h/11h/12h/14h/15h/16h/17h processors. All these processors have a sensor, but on those for Socket F or AM2+, the sensor may return inconsistent values (erratum 319). The driver will refuse to load on these revisions unless you specify the "force=1" module parameter. Due to technical reasons, the driver can detect only the mainboard's socket type, not the processor's actual capabilities. Therefore, if you are using an AM3 processor on an AM2+ mainboard, you can safely use the "force=1" parameter. There is one temperature measurement value, available as temp1_input in sysfs. It is measured in degrees Celsius with a resolution of 1/8th degree. Please note that it is defined as a relative value; to quote the AMD manual: Tctl is the processor temperature control value, used by the platform to control cooling systems. Tctl is a non-physical temperature on an arbitrary scale measured in degrees. It does _not_ represent an actual physical temperature like die or case temperature. Instead, it specifies the processor temperature relative to the point at which the system must supply the maximum cooling for the processor's specified maximum case temperature and maximum thermal power dissipation. The maximum value for Tctl is available in the file temp1_max. If the BIOS has enabled hardware temperature control, the threshold at which the processor will throttle itself to avoid damage is available in temp1_crit and temp1_crit_hyst.
  13. General rule of thumb is to leave CPU 0 and its corresponding hyperthread open to Unraid. All other CPU & HT are free game. Try moving your VM's to CPU 1&2. Dockers can go later. There is a thread somewhere in the forums that go into further details on how to discover which CPU's are on which particular die. Also, subscribe to @spaceinvaderone's YouTube channel, as he has a video on CPU pinning and VM's. Good luck and share with us your discoveries! P.S. - If you don't like the forum's search engine, use the syntax: site:forums.unraid.net search terms Into a search engine such as DuckDuckGo, StartPage, or Google, replacing search terms with your intended query. I'm sure that you'll find what you are looking for in the forums as many have asked similar questions in the past.
  14. The Hide button simply became a mystery that only the Invision Community devs know about.
  15. LoLz. No I haven't. I can see a use wherein a forum user will want to post to the forum and yet, they don't want it fully and readily accessible by a search engine such as Google. e.g. information that the user deems as sensitive in nature; limit meta-data