Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

8 Neutral

1 Follower

About gilahacker

  • Rank
    Advanced Member


  • Gender

Recent Profile Visitors

640 profile views
  1. Then one of us misunderstood what @Zer0Nin3r was asking about regarding `copy --reflink`, which requires the `reflink=1` flag to be set when the disk is formatted.
  2. I just added a new disk to my array and found out about the reflink thing while trying to figure out exactly why it shows 66 GB used* on an empty, newly formatted 10 TB disk. All of my old disks have reflink=0 (per xfs_info command), and I don't believe it's possible to enable it without a reformat. *Seemed high, but I'm honestly not sure what it was on other disks when I added them. Something I stumbled upon in a Google search indicated that new XFS disks have significantly more "used" space to start with when that feature is enabled.
  3. @Hoopster brings up an interesting point. Because, unlike many (most?) Linux distributions, unRAID runs completely within RAM and nothing else gets mounted over-top the default rootfs (special instance of tmpfs). I believe this is similar to any "Live" distro, but don't have experience with those. So even though my /tmp isn't a tmpfs mount itself, it is *on* a tmpfs mount and exists only within RAM. Thus, either /tmp (a path on a tmpfs mount) or /dev/shm (an explicit tmpfs mount) should work exactly the same other than the fact that some of the space on / will be in use already.
  4. On *my* server, running 6.6.6, I have a /dev/shm tmpfs mount that is allocated 32 GB of RAM (per df). I have 64 GB total RAM, not sure why it's set to 32. I do not have a /tmp mount. I do have a /tmp directory, but it's not a tmpfs "RAM drive", just a plain directory. You can run cat /etc/mtab to see what your current mount situation is. I imagine it's similar. I have the Plex /transcode folder mapped to /dev/shm in its Docker settings. No issues so far.
  5. The article about TCP BBR just recently popped up in my news feed. Did a Google search for "unraid tcp bbr" and it led me here to find that it's already been added to the next version. 😁 Dunno if I'll actually see any difference myself (sightly faster downloads? smoother remote streams?) but I'm glad to see that Limetech included it just the same.
  6. I am not a developer, though I do have some experience in that regard, but I don't think an entirely separate branch would be necessary. Toggles to allow users to enable/disable features should be sufficient. A tool to build a custom USB image with/without features could also work*. Splitting different components into their own packages might be best so different parts can be updated independently and not even need to be downloaded by those not using them. For example, if the GUI were a separate package it could be updated without needing a full "OS update", and those not using it wouldn't need to have it installed or even download that new package when they update their system. *But may require significant dev work to make things more modular.
  7. https://lime-technology.com/forums/topic/61771-optional-gui-resolution/?do=findComment&comment=656621 TLDR: Switching from HDMI to DVI got me 1920x1080px resolution in the GUI. I have no idea why, but it worked.
  8. Okay, it makes absolutely no sense, but switching from HDMI to DVI worked for me. I'm using a Zotac GeForce GT 710 (only thing I could find that's cheap, fanless, and fits in the x1 slot) and I've been stuck with a stretched-out, blurry, wrong-aspect-ratio 1024x768px resolution when accessing the GUI locally (using a 4k Sony TV as my monitor). I tried everything I could find software-wise, even attempting to install drivers from Nvidia (never managed to get them installed), and couldn't get the resolution any better than 1024x768. Just now, I swapped out the HDMI cable for a DVI cable with a DVI>HDMI adapter on the TV side, since the TV doesn't have DVI, and rebooted. The GUI came up at 1920x1080 (the terminal even looked like it was higher res before the GUI loaded). Running at actual 4k would have made things too tiny. 1080p is perfect. ? If anyone understands *why* it works better with DVI than it did with HDMI, I'm all ears.
  9. I've never done the zenstates thing. No problems. Asus ROG Zenith Extreme mobo.
  10. Can confirm video passthrough works with Threadripper on 6.4.1rc1. Passmark Performance Test still freezes the VM before even running a benchmark, but games seem to work fine.
  11. Bump. Geforce 710 w/ a 4k TV and the local GUI runs at 1024x768. I've manually added 1920x1080 using the directions here, but get a "Failed to change the screen configuration!" error when I try to actually apply it.
  12. Bump. I have a Geforce 710 hooked up to a 4k TV and my GUI is running at 1024x768, which looks like crap. I have to zoom out in the browser to fit everything on the screen and the text ends up too small and horribly pixelated. It's far more convenient for me to mess with the web GUIs for my various Dockers through the unRAID GUI than it is on my phone (in the market for a new laptop), so I'd like to make it usable. xrandr lists the available resolutions as 640x480, 800x600, and 1024x768. I was able to add a custom resolution following directions I found here, but can't switch to it. I just get a "Failed to change the screen configuration" error message. I've tried 1920x1080@60hz and @30hz with the same results. I went so far as to reboot into non-GUI mode and try to install the Linux drivers for my card (after using the devpack plugin to install things like gcc) but it wants kernel source files that I don't have (I think I'd need a kernel-devel package?). I'm highly doubting that even if I got drivers installed that they'd persist a reboot, but figured it was worth a try. If anyone has any suggestions, I'm all ears. :-/
  13. Just chiming in that the modified kernel @Jcloud made worked for me, but I had to scrap my existing SeaBIOS VM and create one with OVMF. SeaBIOS VM had no video output, OVMF worked as expected.
  14. Update: The issues with launching my Steam games appear to be purely due to software configuration w/ my new Windows 10 install trying to use my already-installed Steam games. Nothing to do with Threadripper or the ugly patched kernel. I installed the old DirectX runtime from http://www.microsoft.com/en-gb/download/details.aspx?id=8109 because when trying to manually launch Doom outside of Steam I got an error saying that xinput1_3.dll was missing. Doom now works in normal and Vulkan (and looks oh-so-pretty at 4k60). Bioshock Infinite and Descent: Underground were also working after the DirectX install. When trying to launch Sonic Adventure 2 though, same behavior as the others. I launched it outside of Steam and got a generic error, but Windows helpfully popped up a message saying that I needed to install .NET Framework 3.5. I'm guessing that'll fix some of the other Sonic games I haven't tried yet as well. FWIW, I did first try uninstalling and re-installing the games through Steam with no luck. I probably should have just started from scratch on the installs. :-/
  15. Can't get any games to launch. Steam says they're running but nothing ever pops up. Within a second or two it changes from "running to syncing". Installed the Passmark Performance Test and it locked up and rebooted the VM when trying to access the 3D test page. Not running the test, just accessing the page you run it from, so I'm guessing something is wonky with the video card detection? GeForce Experience sees it fine, Windows is running at 4k60, etc. Can't even get steam to launch now. Going to install all the Windows 10 updates and try again. I'm not sure if it has anything to do with the issues I'm seeing, but Windows is listing several devices, including the GPU, as if they're removable devices (see attached screenshot).