RussellinSacto

Members
  • Posts

    347
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

RussellinSacto's Achievements

Contributor

Contributor (5/14)

0

Reputation

  1. Thank you all so much for the help... JorgeB and itimpi were totally right.... Needed to "export" each share. With the warning from Frank1940 (Thank You!) I chose the "Yes - Hidden" export setting which will hopefully be enough to keep me from using the disk shares - but will still allow my backup software ARQ Backup to access them. You all are awesome! Thank you! Russell
  2. Thank you both, I haven't found a setting for "export" but I have "enable disk shares" set to Yes. On the Shares screen it shows both User Shares and all of the disks under Disk Shares. Thank you for the warning Frank1940. That is really good to know - also terrifying - seems reasonable this should be BOLD and RED when you turn this function on; I am sure I've violated this rule before. I want to use the disk shares only for backup - so my backup software can backup each of the disks, even if I go and add more user shares later, this works. Is there a better way (that doesn't require me remembering me to add a new backup each time I add a share)? Is there a root of all User Shares that maybe should be the location I backup (from my Windows VM)? Thanks, Russell
  3. Hi Everyone, I am running Windows 10 Pro (Version 21H2; OS Build 19044.2251) as a VM on my Unraid and am no longer able to access my shares via \\tower\disk1 nor \\my.unraid.ip.address\disk1, though I can access my User Shares without issue. I can browse Tower and see and access all User Shares, but Disk Shares are not visible. Under Settings/Global Share Settings I have Enable Disk Shares set to Yes and Included Disks set to All (I have also checked boxes for every drive too); Excluded Disks is None. When I try to access via Start --> Run --> \\tower\disk1 I get "\\tower\disk1 is not accessible. You might not have permission to use this network resource. Contact the adminstrator for this server to find out if you have access permissions. A device attached to the system is not functioning. <OK>" I can access all of the User shares using Start --> Run --> \\tower\usershare it works perfectly. Any ideas? Thanks, Russell
  4. Hi Everyone, After using Unraid for almost 15 years as a NAS solution, I've finally upgraded and now run an Unraid as my Daily Driver Computer (thanks SpaceInvader for the YouTube video on how to run bare metal VM aside/inside Unraid)... So, what's the best way, generically speaking, to setup Plex with Unraid: Install the Plex Media Server App (using Community Applications) directly on Unraid? Install Plex on my always on Windows 10 Daily Driver Virtual Machine and point it to the Unraid drives (which are actually local)? Install Plex on a separate Unraid Server specifically dedicated to Plex? (I have two Unraid systems; the other one is very low horsepower Celeron) Other? Thanks, Russell
  5. Thanks Johnnie, I swapped both power and data to the drive. Unraid still failed to format it. I hooked the drive up to my Windows VM as a USB drive and Windows was happy to format the disk and use it (different cable/power, being USB connected)... I reconnected it and rebooted back to Unraid and the drive still won't format. Logs attached again. palmwood-diagnostics-20200708-2217.zip What else I can try? Any possibility that since this was originally a USB drive (before I "shucked" it) that it might have a jumper setting or something odd that I need to check? Thanks, Russell
  6. Thanks Johnnie, Please find attached. Russell palmwood-diagnostics-20200707-1108.zip
  7. Hi Everyone, I have an 8TB drive that I received from BackBlaze (recovery of another system) as an external USB. I shucked it and have tried to add it to my array, but there's a message next to the drive that says "Unmountable: Unsupported partition layout." There is nothing on the drive so I'm not concerned about formatting it - but when I check the box and ask Unraid to format it, it says "formatting" and a handful of seconds later it comes back exactly the same as it was - with the same message and the option to format the drive again. (I have tried following other forum entries that are similar; I've rebooted, I've added the Unassigned Devices plugin (but it doesn't seem the drive mounts; not sure what to do) and can't figure this out.) It looks to me like there might be two partitions on the drive: How can I resolve this? I'm not Linux experienced at all but I'm wondering if I can somehow drop to the command prompt and format the disk directly? (how can I be sure to select the right disk to format if that's the right course of action?) Thanks, Russell
  8. Hi Guys, I have two pretty old Unraid Licenses I bought about 14-15 years ago. I bought these in the package when Lime offered the license on USB sticks by mail and since they are so old, I'm concerned they may quit working - one gives me trouble every now and then. So, I want to get the licenses moved to new keys. For whatever reason, they don't work with the upgrade technique described in the documentation; the error leads me to think the solution they use now doesn't know about these "vintage" licenses. I found the email address to send for support - and saw that I can expect 3 days for a reply. Tomorrow will be eight days since I sent in my request to get assistance with my licenses - I included the license files in my email messages. Any idea what else I can do to get this resolved? Thanks, Russell
  9. Wow... I figured this out - maybe... It's currently working. I kept noticing that no one else had an "Avocent Corp. Virtual Keyboard/Mouse"... I thought it was part of making VMs work... so I did a bunch of Googling... And realized I might not have the most normal motherboard - I have a Gigabyte MU70-SU0 Server Motherboard... Not sure what makes it a Server Motherboard - I bought it because it had a few cool features: motherboard USB port to hide my unRAID drive, support for hexcore processors, 9 onboard SATA controllers + 1 SATA slot (quick adapter makes it a normal SATA controller) and... <smile> 12 RAM SLOTS. So... apparently it has some "remote management" function to check on it - like if you're in a datacenter and have hundreds of servers to look after, I guess. Anyway, I suspect this virtual keyboard/mouse kept conflicting with the actual keyboard and mouse I had connected... and I couldn't (still can't) figure out how to disable it. I found another great Space Invader video (How to easily pass through a USB Controller in Unraid)... followed all his instructions - set the parameter in the flash syslinux configuration - and only passed through the USB Controller (leaving the unRAID flash and Virtual Keyboard/Mouse unchecked and not passed to the VM). And it seems great now. Hope this helps someone out there (or me, when I forget). Russell
  10. Dang, I decided to just try to get a clean Windows 10 install, forgetting about the dual boot (which I really only want as backup in case I have UnRaid issues - then I just change bios and boot Windows)... So, I followed the steps to create a VM... and booted of the Windows 10 ISO... and had to add the keyboard and mouse via the Hotplug USB plugin - and then I couldn't even type in the enter Windows Activation code before I have the same problem - keyboard no longer works. (Can't disconnect and reconnect in plugin). Hope someone can help... Do I just have a bad hardware combo? Is it the Anker USB hub? (I have to take apart a huge cabinet to get my mouse/keyboard directly connected to the motherboard with the displays near by... planning to try that next, but have no reason to know if it will work.) Thanks, Russell
  11. Just a few more details: My VM keyboard and mouse are always connected to a Anker USB Hub - on a 15 foot extension cord - my Unraid/Desktop are on the other side of the wall than my displays/keyboard. Initial testing seems to be that the Dell keyboard has the repetitive key issue; the HP keyboard just quits working. Russell
  12. Hi Everyone, No real progress - but more information: I installed Community Applications and then the "Libvirt Hotplug USB" plugin. If I boot the machine, then launch the VM... then attach the keyboard and mouse - and then use the Plugin to Attach the keyboard and mouse, I get the same result... Keyboard and mouse work, but as soon as I type a bit, I get the continuous character problem back againnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn Hope someone has an idea to help. Oh, and one other tidbit: I have a Dell L100 keyboard - about the most basic, simplest keyboard ever. Happy to go buy a new keyboard if there's a reasonable chance that fixes my problem. (Not working with HP KU-0316 keyboard either). Russell
  13. Hi everyone, I watched the "Use your Gaming PC's Extra Power as a NAS Ultimate Guide" from Linus Tech Tips on YouTube. I have tried their step (around 10 minute mark) to put a device ID in the Flash SysLinus Configuration to pass through a USB Controller. I rebooted and the controller (Etron Technology EJ188/EJ198 USB 3.0 Host Controller | USB controller (08:00.0) (which I hope is the right one) showed up in the VM settings. I checked the box to include it but when I click Update I get an error that "VM creation error - internal error: unknown pci source type 'vendor'". Working to get this resolved... but I don't even know if I'm headed down the right path. 😞 So close to this working for me - just need this keyboard issue resolved. Hope you can help. Thanks, Russell
  14. Hi Everyone, I've been using Unraid for a long time - but just recently upgraded hardware to do VMs. I followed the video from SpaceInvader to dual boot. I picked this because I have a Windows 10 Pro I'm happy with - and it has all my hardware working (no issues in device manager). I'm setup on a trial key before I move my license over. I got everything going and installed the VirtIO drivers and everything is great... Except when I type quickly (more than a few words), the VM locks up. It usually appears as if a key got stuck on the keyboard: "Now is the time for all goooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo" (etc.) It doesn't seem to matter what application I run - Command Prompt, Notepad, Browser address bar, etc. Sometimes it seems to also lock up the Unraid (local) screen. It feels like the old "device interrupt" type problems way back 15+ years ago. I kinda suspect that the two keyboards and two mice plugged in are somehow conflicting. (Keyboard and Mouse for VM are on a USB Hub, Console keyboard and mouse are directly attached to motherboard.) I've attached my System Devices, the XML of the VM, and the VM logs after the issue has occurred (no errors). Not sure what else might help. Thank you for any help you can provide! Russell PCI Devices and IOMMU Groups IOMMU group 0:[8086:2f81] ff:0b.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring (rev 02) [8086:2f36] ff:0b.1 Performance counters: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring (rev 02) [8086:2f37] ff:0b.2 Performance counters: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 R3 QPI Link 0 & 1 Monitoring (rev 02) IOMMU group 1:[8086:2fe0] ff:0c.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers (rev 02) [8086:2fe1] ff:0c.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers (rev 02) [8086:2fe2] ff:0c.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers (rev 02) [8086:2fe3] ff:0c.3 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers (rev 02) [8086:2fe4] ff:0c.4 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers (rev 02) [8086:2fe5] ff:0c.5 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Unicast Registers (rev 02) IOMMU group 2:[8086:2ff8] ff:0f.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent (rev 02) [8086:2ff9] ff:0f.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Buffered Ring Agent (rev 02) [8086:2ffc] ff:0f.4 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers (rev 02) [8086:2ffd] ff:0f.5 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers (rev 02) [8086:2ffe] ff:0f.6 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 System Address Decoder & Broadcast Registers (rev 02) IOMMU group 3:[8086:2f1d] ff:10.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface (rev 02) [8086:2f34] ff:10.1 Performance counters: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCIe Ring Interface (rev 02) [8086:2f1e] ff:10.5 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers (rev 02) [8086:2f7d] ff:10.6 Performance counters: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers (rev 02) [8086:2f1f] ff:10.7 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Scratchpad & Semaphore Registers (rev 02) IOMMU group 4:[8086:2fa0] ff:12.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0 (rev 02) [8086:2f30] ff:12.1 Performance counters: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Home Agent 0 (rev 02) IOMMU group 5:[8086:2fa8] ff:13.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers (rev 02) [8086:2f71] ff:13.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Target Address, Thermal & RAS Registers (rev 02) [8086:2faa] ff:13.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder (rev 02) [8086:2fab] ff:13.3 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder (rev 02) [8086:2fac] ff:13.4 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder (rev 02) [8086:2fad] ff:13.5 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel Target Address Decoder (rev 02) [8086:2fae] ff:13.6 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 0/1 Broadcast (rev 02) [8086:2faf] ff:13.7 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast (rev 02) IOMMU group 6:[8086:2fb0] ff:14.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 Thermal Control (rev 02) [8086:2fb1] ff:14.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 Thermal Control (rev 02) [8086:2fb2] ff:14.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 0 ERROR Registers (rev 02) [8086:2fb3] ff:14.3 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 1 ERROR Registers (rev 02) [8086:2fbe] ff:14.6 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 (rev 02) [8086:2fbf] ff:14.7 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 0 & 1 (rev 02) IOMMU group 7:[8086:2fb4] ff:15.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 2 Thermal Control (rev 02) [8086:2fb5] ff:15.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 3 Thermal Control (rev 02) [8086:2fb6] ff:15.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 2 ERROR Registers (rev 02) [8086:2fb7] ff:15.3 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 0 Channel 3 ERROR Registers (rev 02) IOMMU group 8:[8086:2f68] ff:16.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Target Address, Thermal & RAS Registers (rev 02) [8086:2f6e] ff:16.6 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Channel 2/3 Broadcast (rev 02) [8086:2f6f] ff:16.7 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO Global Broadcast (rev 02) IOMMU group 9:[8086:2fd0] ff:17.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Integrated Memory Controller 1 Channel 0 Thermal Control (rev 02) [8086:2fb8] ff:17.4 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 (rev 02) [8086:2fb9] ff:17.5 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 (rev 02) [8086:2fba] ff:17.6 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 (rev 02) [8086:2fbb] ff:17.7 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DDRIO (VMSE) 2 & 3 (rev 02) IOMMU group 10:[8086:2f98] ff:1e.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit (rev 02) [8086:2f99] ff:1e.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit (rev 02) [8086:2f9a] ff:1e.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit (rev 02) [8086:2fc0] ff:1e.3 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit (rev 02) [8086:2f9c] ff:1e.4 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Power Control Unit (rev 02) IOMMU group 11:[8086:2f88] ff:1f.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 VCU (rev 02) [8086:2f8a] ff:1f.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 VCU (rev 02) IOMMU group 12:[8086:2f00] 00:00.0 Host bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 DMI2 (rev 02) IOMMU group 13:[8086:2f02] 00:01.0 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 1 (rev 02) IOMMU group 14:[8086:2f04] 00:02.0 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 2 (rev 02) IOMMU group 15:[8086:2f08] 00:03.0 PCI bridge: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 PCI Express Root Port 3 (rev 02) IOMMU group 16:[8086:2f28] 00:05.0 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Address Map, VTd_Misc, System Management (rev 02) [8086:2f29] 00:05.1 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 Hot Plug (rev 02) [8086:2f2a] 00:05.2 System peripheral: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 RAS, Control Status and Global Errors (rev 02) [8086:2f2c] 00:05.4 PIC: Intel Corporation Xeon E7 v3/Xeon E5 v3/Core i7 I/O APIC (rev 02) IOMMU group 17:[8086:8d7c] 00:11.0 Unassigned class [ff00]: Intel Corporation C610/X99 series chipset SPSR (rev 05) IOMMU group 18:[8086:8d31] 00:14.0 USB controller: Intel Corporation C610/X99 series chipset USB xHCI Host Controller (rev 05) IOMMU group 19:[8086:8d3a] 00:16.0 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #1 (rev 05) [8086:8d3b] 00:16.1 Communication controller: Intel Corporation C610/X99 series chipset MEI Controller #2 (rev 05) IOMMU group 20:[8086:8d10] 00:1c.0 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #1 (rev d5) IOMMU group 21:[8086:8d12] 00:1c.1 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #2 (rev d5) IOMMU group 22:[8086:8d14] 00:1c.2 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #3 (rev d5) IOMMU group 23:[8086:8d16] 00:1c.3 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #4 (rev d5) IOMMU group 24:[8086:8d1c] 00:1c.6 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #7 (rev d5) IOMMU group 25:[8086:8d1e] 00:1c.7 PCI bridge: Intel Corporation C610/X99 series chipset PCI Express Root Port #8 (rev d5) IOMMU group 26:[8086:8d44] 00:1f.0 ISA bridge: Intel Corporation C610/X99 series chipset LPC Controller (rev 05) [8086:8d02] 00:1f.2 SATA controller: Intel Corporation C610/X99 series chipset 6-Port SATA Controller [AHCI mode] (rev 05) [8086:8d22] 00:1f.3 SMBus: Intel Corporation C610/X99 series chipset SMBus Controller (rev 05) [8086:8d24] 00:1f.6 Signal processing controller: Intel Corporation C610/X99 series chipset Thermal Subsystem (rev 05) IOMMU group 27:[10de:1401] 01:00.0 VGA compatible controller: NVIDIA Corporation GM206 [GeForce GTX 960] (rev a1) [10de:0fba] 01:00.1 Audio device: NVIDIA Corporation GM206 High Definition Audio Controller (rev a1) IOMMU group 28:[8086:1533] 04:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 29:[8086:1533] 05:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 30:[8086:1533] 06:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 31:[8086:1533] 07:00.0 Ethernet controller: Intel Corporation I210 Gigabit Network Connection (rev 03) IOMMU group 32:[1b6f:7052] 08:00.0 USB controller: Etron Technology, Inc. EJ188/EJ198 USB 3.0 Host Controller IOMMU group 33:[1a03:1150] 09:00.0 PCI bridge: ASPEED Technology, Inc. AST1150 PCI-to-PCI Bridge (rev 03) [1a03:2000] 0a:00.0 VGA compatible controller: ASPEED Technology, Inc. ASPEED Graphics Family (rev 30) CPU Thread Pairings Pair 1:cpu 0 / cpu 6 Pair 2:cpu 1 / cpu 7 Pair 3:cpu 2 / cpu 8 Pair 4:cpu 3 / cpu 9 Pair 5:cpu 4 / cpu 10 Pair 6:cpu 5 / cpu 11 USB Devices Bus 001 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002:ID 0624:0248 Avocent Corp. Virtual Hub Bus 001 Device 003:ID 0781:5571 SanDisk Corp. Cruzer Fit Bus 001 Device 004:ID 0624:0249 Avocent Corp. Virtual Keyboard/Mouse Bus 002 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001:ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 002:ID 0bda:5411 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub Bus 003 Device 003:ID 0bda:5411 Realtek Semiconductor Corp. 4-Port USB 2.0 Hub Bus 003 Device 004:ID 046d:0a04 Logitech, Inc. V20 portable speakers (USB powered) Bus 003 Device 005:ID 04a9:1794 Canon, Inc. G3000 series Bus 003 Device 006:ID 03f0:022a Hewlett-Packard Laserjet CP1525nw Bus 003 Device 007:ID 056a:00c6 Wacom Co., Ltd DTZ-1200W [Cintiq 12WX] Bus 003 Device 008:ID 0bda:5411 Realtek Semiconductor Corp. G3000 series Bus 003 Device 009:ID 413c:2105 Dell Computer Corp. Model L100 Keyboard Bus 003 Device 010:ID 0bda:5411 Realtek Semiconductor Corp. G3000 series Bus 003 Device 011:ID 413c:3016 Dell Computer Corp. Optical 5-Button Wheel Mouse Bus 004 Device 001:ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 004 Device 002:ID 0bda:0411 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub Bus 004 Device 003:ID 0bda:0411 Realtek Semiconductor Corp. 4-Port USB 3.0 Hub Bus 004 Device 004:ID 0bda:0411 Realtek Semiconductor Corp. Bus 004 Device 005:ID 0bda:0411 Realtek Semiconductor Corp. SCSI Devices [0:0:0:0]disk SanDisk' Cruzer Fit 1.00 /dev/sda 63.0GB [2:0:0:0]disk ATA Samsung SSD 860 2B6Q /dev/sdb 1.00TB [5:0:0:0]disk ATA INTEL SSDSC2CW12 400i /dev/sdc 120GB [6:0:0:0]disk ATA WDC WUH721414AL W07G /dev/sdd 14.0TB <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='1'> <name>Windows 10 - Main</name> <uuid>00000000-0000-0040-8000-fcaa14dddf5a</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>57147392</memory> <currentMemory unit='KiB'>57147392</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>10</vcpu> <cputune> <vcpupin vcpu='0' cpuset='1'/> <vcpupin vcpu='1' cpuset='7'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='8'/> <vcpupin vcpu='4' cpuset='3'/> <vcpupin vcpu='5' cpuset='9'/> <vcpupin vcpu='6' cpuset='4'/> <vcpupin vcpu='7' cpuset='10'/> <vcpupin vcpu='8' cpuset='5'/> <vcpupin vcpu='9' cpuset='11'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-4.2'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/00000000-0000-0040-8000-fcaa14dddf5a_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> <hyperv> <relaxed state='on'/> <vapic state='on'/> <spinlocks state='on' retries='8191'/> <vendor_id state='on' value='none'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='5' threads='2'/> <cache mode='passthrough'/> </cpu> <clock offset='localtime'> <timer name='hypervclock' present='yes'/> <timer name='hpet' present='no'/> </clock> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/local/sbin/qemu</emulator> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-Samsung_SSD_860_QVO_1TB_S59HNG0N325722N' index='3'/> <backingStore/> <target dev='hdc' bus='sata'/> <boot order='1'/> <alias name='sata0-0-2'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='block' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source dev='/dev/disk/by-id/ata-WDC_WUH721414ALE6L4_9JGB2P7T' index='2'/> <backingStore/> <target dev='hdd' bus='sata'/> <alias name='sata0-0-3'/> <address type='drive' controller='0' bus='0' target='0' unit='3'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.173-2.iso' index='1'/> <backingStore/> <target dev='hdb' bus='ide'/> <readonly/> <alias name='ide0-0-1'/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='qemu-xhci' ports='15'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='ide' index='0'> <alias name='ide'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='sata' index='0'> <alias name='sata0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <interface type='bridge'> <mac address='52:54:00:8e:7d:32'/> <source bridge='br0'/> <target dev='vnet0'/> <model type='virtio'/> <alias name='net0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <source path='/dev/pts/0'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/0'> <source path='/dev/pts/0'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10 - Main/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='connected'/> <alias name='channel0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'> <alias name='input0'/> </input> <input type='keyboard' bus='ps2'> <alias name='input1'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x01' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x03f0'/> <product id='0x022a'/> <address bus='3' device='6'/> </source> <alias name='hostdev2'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0x0a04'/> <address bus='3' device='4'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='3'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x04a9'/> <product id='0x1794'/> <address bus='3' device='5'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='4'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x056a'/> <product id='0x00c6'/> <address bus='3' device='7'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='5'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x0624'/> <product id='0x0249'/> <address bus='1' device='4'/> </source> <alias name='hostdev6'/> <address type='usb' bus='0' port='6'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x413c'/> <product id='0x2105'/> <address bus='3' device='9'/> </source> <alias name='hostdev7'/> <address type='usb' bus='0' port='7'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x413c'/> <product id='0x3016'/> <address bus='3' device='11'/> </source> <alias name='hostdev8'/> <address type='usb' bus='0' port='8'/> </hostdev> <hub type='usb'> <alias name='hub0'/> <address type='usb' bus='0' port='1'/> </hub> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> ErrorWarningSystemArrayLogin -nodefaults \ -chardev socket,id=charmonitor,fd=31,server,nowait \ -mon chardev=charmonitor,id=monitor,mode=control \ -rtc base=localtime \ -no-hpet \ -no-shutdown \ -boot strict=on \ -device qemu-xhci,p2=15,p3=15,id=usb,bus=pci.0,addr=0x7 \ -device ahci,id=sata0,bus=pci.0,addr=0x3 \ -device virtio-serial-pci,id=virtio-serial0,bus=pci.0,addr=0x4 \ -device usb-hub,id=hub0,bus=usb.0,port=1 \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/ata-Samsung_SSD_860_QVO_1TB_S59HNG0N325722N","node-name":"libvirt-3-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-3-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-3-storage"}' \ -device ide-hd,bus=sata0.2,drive=libvirt-3-format,id=sata0-0-2,bootindex=1,write-cache=on \ -blockdev '{"driver":"host_device","filename":"/dev/disk/by-id/ata-WDC_WUH721414ALE6L4_9JGB2P7T","node-name":"libvirt-2-storage","cache":{"direct":false,"no-flush":false},"auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-2-format","read-only":false,"cache":{"direct":false,"no-flush":false},"driver":"raw","file":"libvirt-2-storage"}' \ -device ide-hd,bus=sata0.3,drive=libvirt-2-format,id=sata0-0-3,write-cache=on \ -blockdev '{"driver":"file","filename":"/mnt/user/isos/virtio-win-0.1.173-2.iso","node-name":"libvirt-1-storage","auto-read-only":true,"discard":"unmap"}' \ -blockdev '{"node-name":"libvirt-1-format","read-only":true,"driver":"raw","file":"libvirt-1-storage"}' \ -device ide-cd,bus=ide.0,unit=1,drive=libvirt-1-format,id=ide0-0-1 \ -netdev tap,fd=34,id=hostnet0,vhost=on,vhostfd=35 \ -device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:8e:7d:32,bus=pci.0,addr=0x2 \ -chardev pty,id=charserial0 \ -device isa-serial,chardev=charserial0,id=serial0 \ -chardev socket,id=charchannel0,fd=37,server,nowait \ -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \ -device vfio-pci,host=0000:01:00.0,id=hostdev0,bus=pci.0,addr=0x5 \ -device vfio-pci,host=0000:01:00.1,id=hostdev1,bus=pci.0,addr=0x6 \ -device usb-host,hostbus=3,hostaddr=6,id=hostdev2,bus=usb.0,port=2 \ -device usb-host,hostbus=3,hostaddr=4,id=hostdev3,bus=usb.0,port=3 \ -device usb-host,hostbus=3,hostaddr=5,id=hostdev4,bus=usb.0,port=4 \ -device usb-host,hostbus=3,hostaddr=7,id=hostdev5,bus=usb.0,port=5 \ -device usb-host,hostbus=1,hostaddr=4,id=hostdev6,bus=usb.0,port=6 \ -device usb-host,hostbus=3,hostaddr=9,id=hostdev7,bus=usb.0,port=7 \ -device usb-host,hostbus=3,hostaddr=11,id=hostdev8,bus=usb.0,port=8 \ -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \ -msg timestamp=on 2020-06-16 15:43:44.276+0000: Domain id=1 is tainted: high-privileges 2020-06-16 15:43:44.276+0000: Domain id=1 is tainted: host-cpu char device redirected to /dev/pts/0 (label charserial0)
  15. Thanks Turl, I'll do that - as soon as I get the array built. 🙂 Hopefully someone knows where to look in these logs to help me out. (I'm looking, but no idea what I'm looking at.) Russell