TreyH

Members
  • Content Count

    22
  • Joined

  • Last visited

Community Reputation

2 Neutral

About TreyH

  • Rank
    Newbie

Recent Profile Visitors

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

  1. I’ve managed up till now passing through all my USB ports via IOMMU groups except the one the boot flash was plugged into. But adding a new device has scrambled this, and I don’t know how to proceed. I’ve been operating fairly happily for four months now with Unraid as my home NAS and as the hypervisor for my Win 10 gaming/dev machine. Few problems, none on the Unraid side, just on the Windows side. But getting it set up right required Putting my boot flash on a USB-A → USB-C adapter and plugging it into my mobo’s lone USB-C port Passing through all the US
  2. I created a small `C:` drive vdisk, installed Windows 10, installed some apps like Steam that allow further installation on network drives, used shares for that, and no problem. But now I need to install some things from the Windows Store (some of which are quite large). Unfortunately, if I go into Settings > System > Storage > Change where new content is saved: I'm not allowed to change any of these--they are all locked to the C drive only. I have mapped drive letters for my shares, and they work as storage locations for other contexts, just not this one
  3. Is there a release notes version giving 6.9.0-rc2 → 6.9.1 changes? With a year of betas trying to figure out what changed from rc2 by teasing out what’s already changed from 6.9.0 → ~30 builds... → 6.9.0-rc2 isn’t straightforward! I’m probably just missing the obvious place to look... Edit: Uh, all those numbers are one off, obviously, in one direction or the other. No coffee yet, sorry. Y’all know what I mean, just the changes from rc2 to the brand-new stable release.
  4. Could you elaborate on what “this” is? Your link is to the release notes for 6.9.0-beta25 and it’s not clear what “the emulated version” refers to in that context. What did you change, settings-wise?
  5. I’m a newbie so didn’t have a previously-performant Windows 10 VM, but for me I tried to set mine up first with a GPU vBIOS grabbed from the online database—which didn’t work at all—and then pulled off of my GTX 1080 with the vBIOS tool. The latter worked but was noticeably _slower_ than not passing in a vBIOS at all. Insofar as the changes to the VM manager I’ve read in the changelog since 6.8, one thing I might check is ensuring you have a) CPU isolation and b) no “odd hyperthreads”—cases where you’ve assigned one hyperthread of a core and not the other(s).
  6. Oops, sorry—I missed this message last month or i would have replied sooner. It turns out the checkbox is unclickable, but the particular colors used for a dimmed checkbox compared with an active checkbox on this device (Safari/iPadOS) wasn’t clear. Sorry for the confusion.
  7. I just executed a command I very much did not want to execute, because it turns out that for some reason ⌃C gets interpreted by the Webterminal’s shell as a ⏎, even though NAS# stty -a intr = ^C [...] is this a known issue? I’ve tried it on different devices and it seems to work this way on all of them. I’ve never seen this before on any Linux distro; universally (until now) I’ve found ⌃C aborts the current command and gives you a new clean command line, it doesn’t execute it! Can anyone shed light on what’s going on? Can this be worked around (`stty` was a
  8. Yes, definitely the usbip-gui package. Hmm.... strangely, after trying to open its settings from the Plugins tab, I tried to visit it via Settings -> USB Settings, which just took me to /USBIP_Settings with the two options (Enable USBIP and Enable USB on Dashboard) both "Disabled", but doing this--just visiting that page without making any changes--resulted in the USB tab appearing in my interface, with that URL /USB. I just tested it to mount a USB flash drive in Windows 10, and it worked fine. So I'm not sure what happened here to delay its working, but it does seem to be work
  9. Does this work on 6.9, or without the usbip kernel extensions installed? I installed this via Community Apps and when I click its settings, it takes me to the URL /USB, which is totally blank. I haven't installed any of your other plugins.
  10. For the record, this may have been a “Windows 10 is still settling with updates, etc.” issue—starting about 12 hours after I posted the earlier message, my keyboard has been waking up the display. In that time, I: activated Windows, installed more virtio drivers, installed the driver for my LG monitor (which I had to download directly from LG’s support site; Windows couldn’t autodetect the monitor as anything but a general plug-and-play monitor, which gave me 800 × 600 resolution on a 3440 × 1440 screen), and installed essential updates (and reboots as ne
  11. In the 6.9 interface, it’s offering me the chance to bind the USB port my Unraid boot flash is on. Is this normal and correct behavior? What will happen if I try it? Will I be able to see the flash device both in vfio vm’s and in Unraid, or will Unraid keep that one to itself? (I have worked on Linux kernel internals this present century—just barely!—so I’m guessing if this has something to do with the vagaries of USB Storage, such that the flash device can remain mounted by Unraid while the underlying USB port appears present but unavailable for any functions to the VM, then this
  12. (See below for possibility that this was transient.) I have Windows 10 with a GTX 1080 and USB keyboard and mouse passed-through. I went through and changed all the power settings (never sleep, etc.), but because my display is very bright even when displaying all black (it's a 40-inch ultra wide, so the LED's have a lot of bleed through) I enabled display sleep. It seemed to work, as the screen turned off but Windows network services were still available from other devices... but then I couldn't get it to wake the monitor back up, via keyboard or mouse. From other threa
  13. How do you pass those through to a VM, then? (Would I have been unable to do the same thing to /dev/sde, if I hadn't clicked the settings and switched on passthrough on the disk that did have settings?) I'm not sure why it thinks this disk and only this disk has a filesystem whose type is "isw_raid_member", when it's actually an NTFS filesystem striped across two other disks as well: root@NAS:~# lsblk -fM NAME FSTYPE FSVER [...] sdb isw_raid_memb 1.3.00 sde isw_raid_memb 1.3.00 └─sde1 isw_raid_memb 1.3.00 sdf isw_raid_memb 1.3.00 [...]
  14. Hi, I'm just setting up my first array and VM's planning to migrate data from my old pre-Unraid disks. In this thread in another topic, I was advised to passthrough all three 3 TB drives in an Intel RST RAID 5 set, but as shown below, only one of the there (marked in green) has the gears while the other two drives in the set (marked in red) do not: How do I pass them through? Addendum: Sorry, just as I sent this I got a reply in the other thread: I was under the impression that "normally" as of the 6.9 UI is via the gears? The passthrough switches h
  15. Thanks, but if you look at the screen grab above, only one of the three 3 TB drives has the gear icon—what do I do about the other two?