TreyH

Members
  • Posts

    39
  • Joined

  • Last visited

Everything posted by TreyH

  1. Somehow my Steam installation (the Windows app directory, not the games library) ended up with nonsense extended Linux ACLs that were preventing Steam from opening. (I have no explanation for this—Steam had plenty of updates but unless Samba’s bugged it shouldn’t be changing Linux ACL’s, right? Other than that, I was playing with the Krusader Docker image and was just poking around and I remember looking at my Windows apps drive, maybe somehow I inflicted ACL changes? I really haven’t the foggiest…) Searching support, I found the `/usr/local/sbin/newperms` script which I looked over, and seemed like it would do the job even though it was designed for pre-Unraid 5 migration and I’ve never run anything earlier than Unraid 5. Unfortunately, I didn’t look at the script closely enough to see that it expected absolute paths only, and since I was in the Steam directory looking at the perms, I ran `/usr/local/sbin/newperms .`. That ended up considering `.` from the perspective of the emhttp server—and voilà, the whole tree under /usr/local/emhttp was changed to owner nobody, with all files to execute off. I did a quick `chown -R root:root` and `chmod -R u+x` on it just so the server itself wouldn’t experience any permissions issue, but then I ran Fix Common Problems, and that’s been just hanging for an hour. (Update: Maybe because I started Fix Common Problems after the recursive chown, but before running the recursive chmod, I think it only managed to display the “running” pop-up; I could find no evidence it was actually running, so I reloaded the page, and was able to re-scan at a normal pace with no issues found. So that’s that…) I haven’t noticed any issues per se with the fileserver, hypervisor, guests, or the GUI, but I’m worried it’s just a matter of time until a cron job or something breaks and I have no confidence I will successfully be able to reboot the host or get back up from a host crash. (For my husband, at least, it’s consolation that Steam’s working now that I ran `newperms` with the correct absolute path!) Is there some tool I could use to fix the permissions on the emhttp directory properly?
  2. Both those things should become available just by upgrading Unraid, I believe. But you’ll need to modify your VM configuration (with Windows shut down) to point at the new drivers (on the VirtIO Drivers ISO: line) and change from i440fx-4.2 to -5.1 (in the Machine: line). Start back up and then install the new drivers inside Windows. (I think that’s how the virtio driver upgrade works; I’m recalling from memory.)
  3. Curious… did you have GPU and USB passthrough? I wonder if we’re dealing with motherboard/GPU/USB bridge differences or what, that some are just breezing through with standard installs and even upgrades, and others are having no luck.
  4. Yes, it does, but following its directions exactly on Ubuntu 20.04 LTS under Unraid doesn’t work. It took me some fiddling to find the right combination, so I really hope this helps someone else out later! These alterations are necessary because most Linux distros have recently (well, gradually over the past 5–10 years, Ubuntu LTS just a few years ago) switched from swap partitions to swap files. If you have an actual swap partition (fairly unlikely these days, but possible) then the steps in the AskUbuntu question above should work better for you. (Funny, we (well, not me we—but people who were alive then) used swapfiles on Unixes all the way back to the 1970’s (!), switched to swap partitions in the 1990’s, usually abandoned swaps entirely in the next decade, and now we’re back to swap files—I’m not sure why we call them two-word “swap files” now when we used to call them one-word “swapfiles”, but, ya know…) Anyway… Here’s what to do: Locate your swap file—almost certainly it’s at “/swap.img” or “/swap”, but you can run “swapon” (not as root, and with no arguments, lest bad things happen!) to find out. (It should also be listed in /etc/fstab.) Run this (replacing “/swap.img” below if necessary), and make a note of the UUID generated (which I’ll call <SWAP_UUID> below). It should be a hexadecimal-dashed value in a 8-4-4-4-12 form like “b34dc0d3-5968-5a32-f4d9-f9e6b5d4afa6”. sudo findmnt -no SOURCE,UUID -T /swap.img Then run sudo swap-offset /swapfile and make a note of the number value (I’ll call it <OFFSET> below). Save a backup copy of /etc/default/grub (in your home directory or somewhere else it will stick around between reboots, not /tmp!) and then edit it (with sudoedit or your favorite method for editing system files) to modify the “GRUB_CMDLINE_LINUX_DEFAULT” line that should already be there, but is probably currently blank. Insert the UUID from the last step at “<SWAP_UUID>”. (Yes, that does mean there are two equals signs in “resume=UUID=<SWAP_UUID>”, it’s not a typo…) It’s possible you’ve had to edit it before to make booting Linux work with a passthrough device; if so, keep those arguments while adding the “resume” and “resume_offset”. GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=<SWAP_UUID> resume_offset=<OFFSET> quiet splash" Run sudo update-grub Important: if you run into any trouble below this step and don’t have a working hibernate/resume, come back here and restore /etc/default/grub to its prior state and re-run this command. If your machine refuses to boot after an attempted hibernation, attach to its graphical console at startup time with VNC, and select a safe boot from the startup GRUB menu. [Continued below at bottom¹.] Install the uswsusp package: sudo apt install uswsusp Configure it with: sudo dpkg-reconfigure -pmedium uswsusp Answer “Yes” to “Continue without a valid swap space?” Do not select the /swap.img choice; instead, select the choice corresponding to the UUID above, probably “/dev/disk/by-uuid/<SWAP_UUID>”. Answer “No” to encryption—unless on this Linux VM you’ve done the steps usually associated with getting a Windows gaming VM to work with native GPU/USB, there is no keyboard or graphics attached to the VM at resume time (which is a slightly weird state not really corresponding to traditional BIOS/UEFI startup), so there’s literally no way to enter the password because the VM doesn’t have any connection to the “outside world” when it asks. If you have done those GPU/USB steps and want to enable encryption, you probably have other work to do, and I can’t tell you what will work. But needing encryption on a shutdown VM in a running virtual host is surely quite a niche case… When you finish the three questions in the uswsusp wizard, it will exit and should give messages showing it’s refreshing your initramfs config itself. But if for some reason it does not, (or, if for your own reasons you know you need to manually modify your initramfs.conf further) run: sudo update-initramfs -u But whether the wizard updates initramfs or you do, ensure it does not make any complaint of “no matching swap device is available”; if it does, you should look at a guide (there are many out there) for removing and recreating your swap file, and then start over with #1 above. Now test that uswsusp hibernation works: sudo s2disk If you’re logged in via graphical console, you should see the machine shutdown. If you’re logged in via SSH, your connection should quickly go dead. Either way, refreshing the VMS tab of your Unraid console, you should see your VM as “Stopped”. Start the VM again, just as if you were booting it cold (most easily, by clicking on its icon in the VMS tab and choosing “Start” from the pop-down. Within seconds, your machine should be back up and you can SSH back in, or attach to its graphical console. Run “uptime” to verify that, as far as the OS is concerned, the VM never rebooted (that is, the uptime value should be back to the last time you rebooted the OS, not just the seconds or minutes it took to get here from clicking “Start” in this step). Any other running processes that don’t die when a network connection is interrupted should continue running normally. You’ve manually hibernated and resumed now, but unfortunately this still won’t respond to Unraid asking Linux to hibernate itself. To do that, you need to modify systemd. Run: sudo systemctl edit systemd-hibernate.service You’ll have an editor with either a blank file, or a file that wasn’t working before. Clear it and replace it with: [Service] ExecStart= ExecStart=/usr/sbin/s2disk ExecStartPost=/bin/run-parts -a post /lib/systemd/system-sleep (The two “ExecStart=” lines, the first with an empty right-hand side, is intentional and required.) Save and exit the editor. You can verify you now have a hibernate systemd function by running systemctl status systemd-hibernate.service It should give output including a mention of an “override.conf”. Now test the systemd hibernate manually: systemctl hibernate It will likely ask you for your password several times. (Don’t worry, when Unraid requests a hibernation, it won’t need your password.) Once again the VM should shutdown, and you should do the same to bring it back up and verify it worked as in step 7. Now you can test the real thing by selecting “Hibernate” from the VM’s pop-down menu in the Unraid VMS tab, waiting a few seconds, reloading to verify the VM is stopped, selecting “Start” from the VM’s pop-down menu, and one last time checking it worked as in steps 7 and 10. If this doesn’t work (whether by the VM’s failing to respond to the Hibernate, or its shutting down hard instead of hibernating, or appearing to hibernate but not successfully resuming) when everything before this did, make sure you’ve installed the recommended “guest” packages for your Linux distro on the VM. (It is usually necessary to reboot after installing the guest packages and before attempting a hibernate/resume cycle.) Now, if you wish, you can set the VM to auto-hibernate when Unraid reboots. A timeout of 90 seconds should be more than sufficient (unless you have very large RAM and very slow disk, I suppose…). —— ¹ If after this step, you attempt to boot and you don’t even get a GRUB safe boot option; or, if you have no way to access the graphical console in order to interact with GRUB; and so the machine endlessly reboots, hangs at boot, or shuts itself back down immediately after boot; you’ll need to boot from a live rescue installer image and restore GRUB. To do that, you’ll either need to change the Unraid VM settings to include a live rescue installer as the OS Install ISO: option, or you’ll need to create a whole new VM with the live image and with the old disk image available as a primary or secondary disk via 9p or other such means.) And then follow its instructions (or the many guides online, such as this one) to repair a corrupted GRUB config. The Boot-Repair tool for Ubuntu (described here for if you accidentally install Windows on your preexisting Ubuntu machine) is a no muss, no fuss way that works in most situations (but I’ve actually never tested it in an Unraid VM—so you may need to fall back to one of the more manual options described in these guides!). But… Much safer and easier: If you have the available disk space, the safest and easiest thing to do is to make a backup copy of your entire VM’s boot disk image; that way, even if GRUB gets corrupted so badly it won’t let you boot into safe mode, you can revert back to the backup image of your Ubuntu installation before you modified it. I happened to have installed a brand-new SSD just before starting this process, so I made image backups as manual “snapshots” at several points above before eventually landing on the above steps I could do start-to-finish.
  5. I think I’ve got too many cooks spoiling the broth here (with “cooks” meaning “conflicting apt packages”). Imagining that one or the other of the many managed apt packages promising to solve “hibernation” would just solve the issue, I installed them one by one and tried hibernating, but none got farther. (A possible clue: when I’ve tried using each of those packages’ inside-guest CLI command to hibernate, they each suspended and turned off the VM, but on resume gave different error messages—none that have been particularly revealing—but, when I “Hibernate” from the Unraid VM interface, I consistently get the above “PM: Image not found (code -16)” message. This was disappointing, especially with the pkg actually called “hibernate”, which goes on at some length in its manpage about how it tries multiple ways until it find one that works. But reading through those links I haven’t found a solution yet. I have checked the contents of /sys/power/image_size (it seems fine—it is larger than either my total available memory or my currently used memory, but smaller than the size of my swap (at /swap.img), and the swap seems to be working. I haven’t tried the “nomodeset” kernel parameter, but I’m using VNC graphics on this VM, so I don’t think it’s applicable… I think my problem may be that my /etc/default/grub has no “resume=” boot command, so I think I’ll give that a try—but for that I need the stable block-device UUID for my swap. And as it’s an img file in the root filesystem, I’m not sure how to locate that.
  6. I’m confused by this because you earlier wrote That certainly sounds like “harm in trying” to me! Unless—knowing what you now know—there’s an additional step you could’ve done in backing up your 6.9 configuration that would have made rolling back easier?
  7. I have “Hibernate” set in VM Manager as the shutdown action, and for years it’s worked flawlessly with my Windows 10 VM. I’d always shutdown and started up my Linux VMs manually, though. It was just when my husband had to power the box off to rearrange power cables the other day that I found out it wasn’t working on Ubuntu—Windows still thought its uptime was months, but Linux’s uptime is just since the power cycle. So testing, I manually did “Hibernate” from the VM popup menu actions, and nothing happened (as far as I can tell from the logs, nothing even registered Ubuntu-side). Poking around the interwebs it seemed like the qemu-guest-agent service was the ticket, so I installed its apt, did sudo systemctl start qemu-guest-agent and tried “Hibernate” again. Seemed to work—after about 30 seconds, the machine showed as powered off in VMs and the host disappeared from my network. But then when I did “Start”, it didn’t resume but booted anew. In syslog, I found (truncating around the moments the VM was off): Aug 3 18:22:17 ubuntuvm systemd[1]: Started QEMU Guest Agent. Aug 3 18:22:53 ubuntuvm gnome-shell[837]: Failed to set DPMS: Failed to set connector 37 property 2: Permission denied Aug 3 18:22:53 ubuntuvm gnome-shell[837]: Screen lock is locked down, not locking Aug 3 18:22:53 ubuntuvm NetworkManager[655]: <info> [1659565373.9953] manager: sleep: sleep requested (sleeping: no enabled: yes) Aug 3 18:22:53 ubuntuvm NetworkManager[655]: <info> [1659565373.9954] manager: NetworkManager state is now ASLEEP Aug 3 18:22:53 ubuntuvm ModemManager[702]: <info> [sleep-monitor] system is about to suspend Aug 3 18:22:54 ubuntuvm systemd[1]: Reached target Sleep. Aug 3 18:22:54 ubuntuvm systemd[1]: Starting Record successful boot for GRUB... Aug 3 18:22:54 ubuntuvm systemd[1]: Starting Hibernate... Aug 3 18:22:54 ubuntuvm kernel: [ 4607.208769] PM: Image not found (code -16) Aug 3 18:22:54 ubuntuvm systemd[1]: grub-common.service: Succeeded. Aug 3 18:22:54 ubuntuvm systemd[1]: Finished Record successful boot for GRUB. Aug 3 18:22:54 ubuntuvm systemd[1]: Starting GRUB failed boot detection... Aug 3 18:22:54 ubuntuvm systemd[1]: grub-initrd-fallback.service: Succeeded. Aug 3 18:22:54 ubuntuvm systemd[1]: Finished GRUB failed boot detection. Aug 3 18:22:54 ubuntuvm systemd-sleep[2912]: Suspending system... Aug 3 18:24:08 ubuntuvm systemd-modules-load[390]: Inserted module 'msr' Aug 3 18:24:08 ubuntuvm systemd-sysctl[401]: Not setting net/ipv4/conf/all/promote_secondaries (explicit setting exists). Aug 3 18:24:08 ubuntuvm systemd-sysctl[401]: Not setting net/ipv4/conf/default/promote_secondaries (explicit setting exists). Aug 3 18:24:08 ubuntuvm systemd[1]: Starting Flush Journal to Persistent Storage... and looking back, the messages starting with “Inserted module ‘msr’” on were common to the previous reboots. IOW, it looks exactly like a hibernate and system sleep happened, but for whatever reason it wasn’t resumed. I have no trouble with other virtio features. Searching here, I’ve found multiple references to https://wiki.unraid.net/Manual/VM_Guest_Support but that page seems to only discuss Windows guests. (The page is organized as if it will discuss other guest OSes, but I can’t see anywhere it does so.) I’d appreciate any pointers on how to proceed troubleshooting this! ——- Additional info This is Ubuntu 20.04.4 LTS. Besides the new package qemu-guest-agent, I already had the qemu-kvm service installed and it isn’t clear to me what it does, but checking its status gives me: root# systemctl status qemu-kvm ● qemu-kvm.service - QEMU KVM preparation - module, ksm, hugepages Loaded: loaded (/lib/systemd/system/qemu-kvm.service; enabled; vendor preset: enabled) Active: active (exited) since Wed 2022-08-03 18:24:05 EDT; 55min ago Process: 578 ExecStart=/usr/share/qemu/init/qemu-kvm-init start (code=exited, status=0/SUCCESS) Main PID: 578 (code=exited, status=0/SUCCESS) Aug 03 18:24:05 ubuntuvm systemd[1]: Starting QEMU KVM preparation - module, ksm, hugepages... Aug 03 18:24:05 ubuntuvm systemd[1]: Finished QEMU KVM preparation - module, ksm, hugepages. If you look above, the timestamp here (18:24:05) is actually just prior to the first post-reboot message appearing in syslog. And, for completeness: root# sudo systemctl status qemu-guest-agent ● qemu-guest-agent.service - QEMU Guest Agent Loaded: loaded (/lib/systemd/system/qemu-guest-agent.service; static; vendor preset: enabled) Active: active (running) since Wed 2022-08-03 18:24:08 EDT; 1h 2min ago Main PID: 668 (qemu-ga) Tasks: 1 (limit: 4608) Memory: 952.0K CGroup: /system.slice/qemu-guest-agent.service └─668 /usr/sbin/qemu-ga Aug 03 18:24:08 ubuntuvm systemd[1]: Started QEMU Guest Agent.
  8. Ditto here—this thread is marked “solved”, but I see no solution. I was literally just about to pull the trigger on my own 6.9 → 6.10.3 upgrade—I’d made my last flash backup and was set to go—when I happened to see this thread. My Windows 10 VM has been working flawlessly up till now for years as the primary userland OS on the box, and the mere existence of this thread has me scared now!
  9. Okay, perfect. Yes, that comment link would lead one to believe migration and old-plugin deletion isn’t automatic, so it gave me a scare. Thanks for running this one to ground!
  10. If this is an FAQ, pardon me—I couldn’t figure out the search terms to unearth it. My Unraid host rebooted 2 days ago (on July 26), and I was trying to figure out why. Prior to that, my uptime had been about 3 months. My husband said he installed Windows Updates in the Win10 guest VM, requiring reboots at about that time (not sure exactly when, though—it could have been before or during the host reboot). He says he didn’t touch a reset button or power switch/cable. I’ve never seen action on the Win10 VM cause a reboot of Unraid—that VM is “his PC” so I barely ever touch it—so I’m perplexed. My vfio-pci log, dmesg, and syslog all start at the same time uptime gives me, and prior to that in /var/log I have nothing between mid-April and Jul 26. I do have guest support installed such that if I command Unraid to reboot, it suspends the Win10 VM gracefully and restarts it when Unraid comes back, and that has worked flawlessly in the past. So all this sounds to me like it’s pointing to an unexpected powercycle—except We were both home then and would normally have noticed the reboot chirp, and Windows says its VM’s uptime is the same minute as Unraid’s, and Windows’ diags says it was a normal reboot, not a powercycle crash. So… very, very odd. Can anyone suggest next diagnosis steps?
  11. #!/usr/bin/env php <?php #begin USB_MANAGER if ($argv[2] == 'prepare' || $argv[2] == 'stopped'){ shell_exec("/usr/local/emhttp/plugins/usb_manager/scripts/rc.usb_manager vm_action '{$argv[1]}' {$argv[2]} {$argv[3]} {$argv[4]} >/dev/null 2>&1 & disown") ; } #end USB_MANAGER if (!isset($argv[2]) || $argv[2] != 'start') { exit(0); } $strXML = file_get_contents('php://stdin'); $doc = new DOMDocument(); $doc->loadXML($strXML); $xpath = new DOMXpath($doc); $args = $xpath->evaluate("//domain/*[name()='qemu:commandline']/*[name()='qemu:arg']/@value"); for ($i = 0; $i < $args->length; $i++){ $arg_list = explode(',', $args->item($i)->nodeValue); if ($arg_list[0] !== 'vfio-pci') { continue; } foreach ($arg_list as $arg) { $keypair = explode('=', $arg); if ($keypair[0] == 'host' && !empty($keypair[1])) { vfio_bind($keypair[1]); break; } } } exit(0); // end of script function vfio_bind($strPassthruDevice) { // Ensure we have leading 0000: $strPassthruDeviceShort = str_replace('0000:', '', $strPassthruDevice); $strPassthruDeviceLong = '0000:' . $strPassthruDeviceShort; // Determine the driver currently assigned to the device $strDriverSymlink = @readlink('/sys/bus/pci/devices/' . $strPassthruDeviceLong . '/driver'); if ($strDriverSymlink !== false) { // Device is bound to a Driver already if (strpos($strDriverSymlink, 'vfio-pci') !== false) { // Driver bound to vfio-pci already - nothing left to do for this device now regarding vfio return true; } // Driver bound to some other driver - attempt to unbind driver if (file_put_contents('/sys/bus/pci/devices/' . $strPassthruDeviceLong . '/driver/unbind', $strPassthruDeviceLong) === false) { file_put_contents('php://stderr', 'Failed to unbind device ' . $strPassthruDeviceShort . ' from current driver'); exit(1); return false; } } // Get Vendor and Device IDs for the passthru device $strVendor = file_get_contents('/sys/bus/pci/devices/' . $strPassthruDeviceLong . '/vendor'); $strDevice = file_get_contents('/sys/bus/pci/devices/' . $strPassthruDeviceLong . '/device'); // Attempt to bind driver to vfio-pci if (file_put_contents('/sys/bus/pci/drivers/vfio-pci/new_id', $strVendor . ' ' . $strDevice) === false) { file_put_contents('php://stderr', 'Failed to bind device ' . $strPassthruDeviceShort . ' to vfio-pci driver'); exit(1); return false; } return true; } Checking the contents of the dir for anything starting with ‘u’ or including ‘usb’: root@NAS:~# ls /usr/local/emhttp/plugins | grep -i '^u' unRAIDServer/ unRAIDServer/ unassigned.devices/ unassigned.devices-plus/ usb_manager/ user.scripts/ ls /usr root@NAS:~# ls /local/emhttp/plugins | grep -i 'usb' usb_manager/ Looking at the scripts in usb_manager/, I see there’s a $docroot variable set as $docroot = $docroot ?: @$_SERVER['DOCUMENT_ROOT'] ?: '/usr/local/emhttp'; that is later used in ./event/stopping_svcs: #!/bin/bash # DOCROOT=`grep -Po '^chdir = \K.*' /etc/php-fpm.d/www.conf 2>/dev/null` if [ -z ${DOCROOT} ];then DOCROOT="/usr/local/emhttp" fi logger "Stopping Daemon(USBIPD)" -t"unraid.usbip-gui" ${DOCROOT}/plugins/usb_manager/scripts/rc.usb_manager stop_daemon #logger "Detach All USBIP Devices..." -t"unraid.usbip-gui" #${DOCROOT}/plugins/unraid.usbip-gui/scripts/rc.unraid.usbip-gui detach_ports suggesting to me that if usbip-gui were still installed, I should still have a /usr/local/emhttp/plugins/unraid.usbip-gui directory—but as shown above, I do not.
  12. @SimonF and @Squid: Ok, I don’t know how to resolve this. I can assure you, with 100% certainty, I did not 1. See the dialog message posted above (“You must uninstall USBIP-GUI…”) 2. Open a second web tab to UnRaid 3. Uninstall usbip-gui 4. Go back to the tab in step 1, and click “Install” But unless I misunderstand you, I hear you saying if I did not do steps 2 and 3 (or the equivalent at the CLI) then 4 should not have worked and/or usbip-gui should still be installed. But this is not the case. What’s going on here? Again, if the install logs are saved somewhere let me know the pathname and I’ll paste it in; I am 95% certain it wrote “uninstalling usbip-gui…” before continuing with the install.
  13. But it happened. So your understanding must be incorrect. Is there a place later on to view the logs you get in the overlay when you click Install so that I can post that? Poking around I don’t see it. I can tell you I have done absolutely nothing on my server since doing the USB Manager install except type here, and at this moment, my plugin list shows: Note that USB Manager is there, usbip-gui is gone. I can assure you I did not uninstall it—the only reason I was motivated to post here was because I went “nooooo…” when it deleted before I had a chance to backup the config.
  14. Ah—our messages crossed! Yes, if you can change “OK” to “Proceed” as well, please do! I wasn’t sure the flexibility there. But the main thing would be to change “You must uninstall…” to “USBIP-Gui will be uninstalled in order to use this plugin. See HERE.” With a message to backup the config if it fits as well.
  15. Will do, thanks—I had no idea that people other than plugin authors were writing their install manifests on the CA. When I’ve released PyPI/CPAN/Node/Docker/etc. packages onto central install servers I have to do all that stuff myself; I guess the division of labor here is different. But just to be sure I understand before posting—there’s nowhere in your plugin package that you mention the URL https://forums.unraid.net/topic/100511-plugin-usb_manager/page/3/?tab=comments#comment-1002707 or have the words “You must uninstall usbip-gui”—that was written by Squid?
  16. They were in the CA interface—but I’m assuming they were part of your plugin since they included that wording with the link to that comment earlier in this thread. If someone else writes the CA warning messages then lmk to whom I should redirect my suggestion. Thanks!
  17. I just wanted to mention a deprecation UX issue that can probably be fixed fairly easily… I got a notification today from Fix Common Problems that usbip-gui had been deprecated. Following the instructions I got to USB Manager, and when I tried to install it, it said it was incompatible with usbip-gui and said “You must uninstall it first” or something like that. It also linked to this comment, which I read and saw, yes, said you must install it—but that the configs were compatible. So I decided I’d make a backup first. I returned to the UnRaid GUI to see where the config was, but first I had to dismiss that message from when I tried to install USB Manager, so I clicked “OK”. Oops. It deleted usbip-gui and installed USB Manager (presumably, deleting the deprecated config at the same time?). I think the problem was that I had an expectation that Unraid’s plugin system doesn’t really make room for: there’s a general consensus in UI that action-gating warnings should never have both an “OK” and “Cancel” button, since it isn’t clear what “OK” means in that context. It’s usually advised to either have a single button to do nothing but acknowledge the warning until the thing being warned about is fixed/forced elsewhere (it doesn’t really matter whether it says “OK” or “Cancel”—whichever makes more sense with the wording of the message), or the buttons should change to “Proceed/Force/Yes, really do it/Delete all my files/etc.” and “Cancel” (preferably with the order of buttons reversed and default swapped, so that someone on autopilot will cancel). (Sometimes an alternative used is an “I understand, proceed” checkbox that must be clicked to make the OK button do something other than cancel.) Simon, given you can’t change that UI, I think you tried to make the best of it with your warning and link, but I think the wording strongly implied that the USB Manager plugin would not install until I had uninstalled usbip-gui first. So I was surprised when it did—hopefully I won’t have unexpected issues as a result. My suggestion would be just to change the wording (I didn’t take a screenshot so I can’t see it now, going from memory) from “You must uninstall usbip-gui first” to something like “If you continue, usbip-gui will be uninstalled. Make a backup of your configuration first: see HERE.” I know that usually you don’t get anything at all when you hit “Install” from the plugins list before installation just happens—but I still think in this case a little more is needed. (If I’m misremembering, and the buttons say “Install” and “Cancel”, or the warning didn’t say ‘you’, then my bad—but it just now happened, so I think I’m recalling correctly.) Thanks!
  18. 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 USB busses except for the USB-C one. This meant I couldn’t use USB-C devices in Windows, but that wasn’t a big deal. The alternatives were to only passthrough two USB 2 or three USB 2.1 ports plus a USB-C port, and that just wasn’t sufficient for my Windows installation. I’ve now run into a more difficult issue. I have an Intel WiFi/Bluetooth PCI card that has a USB header—basically, the WiFi goes through PCI but the Bluetooth goes through the USB (though it can’t be powered via USB, so the card has to sit in a PCI slot even if you aren’t using it for WiFi). This was weird, but fine—the USB bus that saw the Bluetooth adapter was one of the ones I was already passing through. But, I needed to move the card to a different PCI slot to accommodate a new SATA HBA since I was adding a couple new disks to my pools—the Intel wireless card was in a full-width slot even though it was just an x1 card. Unfortunately, when I moved the card to the free x1 slot, the Bluetooth’s USB device moved, too—to the same bus the USB-C port is on. I don’t understand this—I’d think that the header would determine the bus, not the PCI slot, but I don’t really understand how this odd hybrid PCI/USB card works. I’d already broken up the IOMMU groups as much as possible before finding my only choice for the boot flash was the USB-C port. So what now? Are either buying a Bluetooth card that doesn’t require USB, or else an actual Bluetooth USB dongle I can plug into (a hub attached to) one of the currently passed-through buses, my only options (other than not using the new HBA)?
  19. 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. If there's a way to change the install location of new apps without using this screen, that's fine too, I just don't know what that is? Thanks for any help!
  20. 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.
  21. 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?
  22. 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).
  23. 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.
  24. 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 already set correctly as I wrote, but altering it didn’t seem to matter)? Should I submit a bug report? (addendum: I just tried other commands that tell me what the shell is seeing when I press ⌃C, and it’s seeing a ⌃J. But ⌃J and ⏎ (aka ⌃M) also send a ⌃J. Sooo.... weird.) (This is on 6.9.0-rc2.)
  25. 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 working now.