• Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About TreyH

  • Rank
  1. 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
  2. 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
  3. 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.
  4. 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
  5. 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
  6. (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
  7. 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 [...]
  8. 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
  9. 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?
  10. Thanks, that makes sense, but following the guide for 6.9, I went to Tools → System Devices, and all my disks—my array disks and these Intel RST disks—are in the same IOMMU group. Which makes sense, as I don’t have a separate storage card but the built-in mobo one. So how does one go about hiding devices rather than the entire IOMMU group?
  11. So I tried this, first with an UEFI ArchLinux boot USB to verify I could still mount and access the data on my RAID 5 set okay (I could), and then booting 6.9.0-rc2 (created with the Unraid USB Creator with UEFI checked) on the same USB port. The Intel RST status on the BIOS screen showed everything green, but when I got into the UD settings, I got this (with the green highlighting the three drives in the RAID 5 set): They showed up as separate drives (which, in itself, isn't necessary worrying, since ArchLinux sees them as four drives, each of the 3 raw 3TB disks, and then t
  12. (tl:dr: I’ve boldfaced my questions below so you can see what I’m asking without having to read all the background info.) I am in the process of trying to use Unraid to replace a bare-metal Windows 10 Pro install. I used it as a (light-duty) Windows development workstation and for some gaming with a GTX 1080. I also used this Windows host OS for an SMB server for other devices in the house, as a Hyper-V hypervisor for (very light-duty) Docker images, and a Ubuntu development workstation. Most of my “real work” was in Ubuntu, so the heaviest load was when I was interactively using U
  13. I have a network-based backup (though apparently—as I discovered—I can’t rebuild the boot OS from it, unfortunately, the data files are all there and fine from spot-checks)—but building a new installation from scratch based off of it would take many days (and be costly, as I’m on a storage plan where I pay for bulk transfer). I would truly rather use the media I already have installed here. That said, someone on the official Discord has suggested that all I need do is change the Unraid boot USB to UEFI rather than legacy, and then UD will address the RAID volumes fine? This would m
  14. I think I may have made a very costly mistake... I was aware that Unraid cannot address disks that use Intel RST RAID. But I thought that just meant it couldn’t use them directly, when I’m now reading that it needs to be turned off in the BIOS/UEFI? That truly messes up my plans to use the Unassigned Devices plugin to migrate my RAID 5 data into Unraid, after buying enough new SSD’s and HDD’s for the purpose that I thought it “should” work.... The background: my workstation recently had a catastrophic unrecoverable Windows update error. I decided to capitalize on the need to reinst
  15. (Boldface mine.) Just a small factual correction: Linux is perfectly capable of using Intel RST logical drives. Typically, each physical disk is seen as a normal block device (/dev/sd*), while the RAID drives are visible as logical drives: # lsblk -M -o NAME,FSTYPE NAME FSTYPE ┌┈▶ sda isw_raid_member ┆ ├─sda1 ntfs ┆ ├─sda2 ntfs ┆ └─sda3 ntfs └┬▶ sdb isw_raid_member ┆ ├─sdb1 ntfs ┆ ├─sdb2 ntfs ┆ └─sdb3 ntfs └┈┈md126 ├─md126p1 ntfs ├─md126p2 ntfs └─md126p3 ntfs Here, a mirrored pair across sda and sbd (note