-
Posts
137 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Squazz
-
-
On 20/5/2016 at 11:02 AM, Fpsware said:
I resorted to running SyncBack Pro in a Windows VM to do just that.
I'd like to see some kind of docker support for this or directly supported within unRaid.
I've looked into this solution myself. How did it go for you? And how about licensing, have you needed to keep the software upgraded in order to keep on using it?
-
Passing through one of the onboard USB controllers has resolved the issue.
I don't know what could have gone wrong, and I'd happily help to provide information if that's something that would be useful for the community
-
On 4/4/2018 at 4:15 AM, ars92 said:
Have you tried using the hot plug USB plugin on CA for this? It should be able to let you pass through just your DAC
Sent from my iPhone using TapatalkI've now tried this for a couple of days, it didn't resolve the problem
-
18 hours ago, ars92 said:
Have you tried using the hot plug USB plugin on CA for this? It should be able to let you pass through just your DAC
Sent from my iPhone using TapatalkHi here, sorry for the late response, I had forgotten to set up notifications.
I'll try out the USB plugin in the next couple of days.
In the meantime, I've just updated the first post with updated informations in configs and XML. Hoping that the updated data might shed some light on what I've done.
I've passed through my onboard audio, that seems to work fine without problems.
After narrowing it down to being the USB DAC I think is the problem, I have changed "USB Controller" hoping this might make a difference.
I'll keep you updated on my findings -
I'm having some problems with sound on my Ryzen platform.
I've been trouble-shooting a lot of things. Everything started out with YouTube videos stopping playing. I found out hat when this happened, I wasn't able to produce any kind of sound on my machine. Spotify and iTunes both won't play music when this happens.
First I thought this was GPU related, but even just playing music via VLC sometimes the music just stops playing and all programs starts acting weird. Spotify "cant play the current song", youtube just sands "buffering" forever.Other times the "counter" in the bottom of Spotify keeps moving, but no sound is produced.
I'm using a USB DAC to transfer sound to my headphones. I've tried to find a way to stub it, but I don't see a way to do this, seems I have to stub the entire USB controller?
When I loose sound, I have tried simply switching audio device from my USB DAC to the HDMI cable that goes to my monitor. Then audio goes through just fine, so I'm pretty sure there's something wrong with the pass-through of the DAC audio.
I don't know what to do now. I never had these problems on my Intel platform, but there I wasn't using unRAID nor KVM either.
Does anyone know what I should try out next? Is there any way I can figure out if there's something wrong with the pass-through (as I suspect)?
System information
OS: unRAID 6.5.1-rc2
Model: Custom M/B: MSI - X370 SLI PLUS (MS-7A33) CPU: AMD Ryzen 7 1700 Eight-Core @ 3000 HVM: Enabled IOMMU: Enabled Cache: 768 kB, 4096 kB, 16384 kB Memory: 16 GB (max. installable capacity 256 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.14.28-unRAID x86_64 OpenSSL: 1.0.2n Uptime:
IOMMU groups
IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 1: [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 3: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 5: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 6: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 8: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 9: [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 10: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 11: [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 12: [1022:43b9] 03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) [1022:43b5] 03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02) [1022:43b0] 03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02) [1022:43b4] 16:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [10ec:8168] 21:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) [1000:0072] 24:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) [1b21:2142] 25:00.0 USB controller: ASMedia Technology Inc. Device 2142 IOMMU group 13: [1002:67b0] 26:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:aac8] 26:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X] IOMMU group 14: [1022:145a] 27:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a IOMMU group 15: [1022:1456] 27:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 16: [1022:145c] 27:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 17: [1022:1455] 28:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 IOMMU group 18: [1022:7901] 28:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 19: [1022:1457] 28:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller
USB devices
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8644:8003 Intenso GmbG Micro Line 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 025: ID 08bb:2704 Texas Instruments PCM2704 16-bit stereo audio DAC Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 002: ID 2516:0021 Bus 005 Device 003: ID 046d:c07d Logitech, Inc. G502 Mouse Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
XML
<domain type='kvm' id='3'> <name>Windows 10</name> <uuid>0eb9574c-5498-57aa-e5c6-4e209652b878</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>14</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='3'/> <vcpupin vcpu='2' cpuset='4'/> <vcpupin vcpu='3' cpuset='5'/> <vcpupin vcpu='4' cpuset='6'/> <vcpupin vcpu='5' cpuset='7'/> <vcpupin vcpu='6' cpuset='8'/> <vcpupin vcpu='7' cpuset='9'/> <vcpupin vcpu='8' cpuset='10'/> <vcpupin vcpu='9' cpuset='11'/> <vcpupin vcpu='10' cpuset='12'/> <vcpupin vcpu='11' cpuset='13'/> <vcpupin vcpu='12' cpuset='14'/> <vcpupin vcpu='13' cpuset='15'/> </cputune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-2.11'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0eb9574c-5498-57aa-e5c6-4e209652b878_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='14' threads='1'/> </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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <backingStore/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <alias name='virtio-disk2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <controller type='usb' index='0' model='nec-xhci'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/> </controller> <controller type='pci' index='0' model='pci-root'> <alias name='pci.0'/> </controller> <controller type='virtio-serial' index='0'> <alias name='virtio-serial0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0c:df:2e'/> <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-3-Windows 10/org.qemu.guest_agent.0'/> <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/> <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='0x26' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <rom file='/mnt/user/appdata/Hawaii.rom'/> <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='0x26' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x28' slot='0x00' function='0x3'/> </source> <alias name='hostdev2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc07d'/> <address bus='5' device='3'/> </source> <alias name='hostdev3'/> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x08bb'/> <product id='0x2704'/> <address bus='3' device='25'/> </source> <alias name='hostdev4'/> <address type='usb' bus='0' port='2'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2516'/> <product id='0x0021'/> <address bus='5' device='2'/> </source> <alias name='hostdev5'/> <address type='usb' bus='0' port='3'/> </hostdev> <memballoon model='virtio'> <alias name='balloon0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain>
Syslinux config:
default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append initrd=/bzroot pci-stub.ids=1002:67b0,1022:1457,1022:145c,1b21:2142 label unRAID OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label unRAID OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label unRAID OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest
-
1 hour ago, DZMM said:
Glad it worked. Unraid OS takes the first GPU - in your case the only one and that's why your VM had a black screen as it technically had no GPU. Stubbing stops unRAID taking devices but allows you to assign them to VMs.
I didn't need to stub my nvidia GT710 that's in my primary slot as I've dumped the ROM, which seems to do away with the need to stub nvidia cards.
I think stubbing sometimes leads to performance improvements, which is why I've stubbed the onboard audio for my VM (other x2 are for the kids) and my dual nic card for my pfsense VM.
Cool, thanks for the explanation I might stub some other hardware too, could very well be that performance might get better by doing so
-
On 21/3/2018 at 7:28 PM, DZMM said:
...
Have you stubbed your GPU? Follow these instructions, but look for your GPU not your USB device
https://lime-technology.com/forum/index.php?topic=36768.msg475897#msg475897
WUU! YOU DA MAN!
Are you able to tell me why this worked?
-
On 21/3/2018 at 7:28 PM, DZMM said:
Did you follow this process?
Edit: whoops just seen you are AMD. Will find another link that helpedHave you stubbed your GPU? Follow these instructions, but look for your GPU not your USB device
https://lime-technology.com/forum/index.php?topic=36768.msg475897#msg475897
Whoa, didn't see this as I didn't get a notification of you editing the answer
I'm pretty sure I haven't subbed my GPU, at least I haven't done anything actively to do that
I'll try to find time tonight to play around with it.
-
10 hours ago, itimpi said:
If you select Edit there is now a button at the top tight to toggle between form and xml views.
Cool, thanks, I'll check up on that when I get to my machine later todayAre those informations critical in order for you guys to help me?Is there anything else I should provide?
Edit: Just updated the first post with more information
-
I've read quite a lot of topics in here with people having trouble setting up passthrough for their GPU if it's the only GPU in the system.
This is my case too. My 290X is the only GPU in the system, and when I try to boot up my VM it just returns a black screen.If I use the VNC as a GPU I can easily boot up the machine. I installed Windows 10 this way.
After updating to UnRaid 6.5.1-rc1, I can't find the "see xml" button anymore, so I'll just list some of the info here. If you need the XML, please do guide me to where I find that part now
Machine: i440fx-2.10 (tried with Q35-2.1.1 too)
Hyper-V: yes
I have tried specifying the ROM directly.
I really hope someone know what I could try out next
System information
Model: Custom M/B: MSI - X370 SLI PLUS (MS-7A33) CPU: AMD Ryzen 7 1700 Eight-Core @ 3000 HVM: Enabled IOMMU: Enabled Cache: 768 kB, 4096 kB, 16384 kB Memory: 16 GB (max. installable capacity 256 GB) Network: bond0: fault-tolerance (active-backup), mtu 1500 eth0: 1000 Mb/s, full duplex, mtu 1500 Kernel: Linux 4.14.28-unRAID x86_64 OpenSSL: 1.0.2n Uptime:
IOMMU groups
IOMMU group 0: [1022:1452] 00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 1: [1022:1453] 00:01.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 2: [1022:1452] 00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 3: [1022:1452] 00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 4: [1022:1453] 00:03.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe GPP Bridge IOMMU group 5: [1022:1452] 00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 6: [1022:1452] 00:07.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 7: [1022:1454] 00:07.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 8: [1022:1452] 00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) PCIe Dummy Host Bridge IOMMU group 9: [1022:1454] 00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Internal PCIe GPP Bridge 0 to Bus B IOMMU group 10: [1022:790b] 00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 59) [1022:790e] 00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51) IOMMU group 11: [1022:1460] 00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 0 [1022:1461] 00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 1 [1022:1462] 00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 2 [1022:1463] 00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 3 [1022:1464] 00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 4 [1022:1465] 00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 5 [1022:1466] 00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 6 [1022:1467] 00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Data Fabric: Device 18h; Function 7 IOMMU group 12: [1022:43b9] 03:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43b9 (rev 02) [1022:43b5] 03:00.1 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43b5 (rev 02) [1022:43b0] 03:00.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43b0 (rev 02) [1022:43b4] 16:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:01.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:02.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:03.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [1022:43b4] 16:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] 300 Series Chipset PCIe Port (rev 02) [10ec:8168] 21:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15) [1000:0072] 24:00.0 Serial Attached SCSI controller: LSI Logic / Symbios Logic SAS2008 PCI-Express Fusion-MPT SAS-2 [Falcon] (rev 03) [1b21:2142] 25:00.0 USB controller: ASMedia Technology Inc. Device 2142 IOMMU group 13: [1002:67b0] 26:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii XT / Grenada XT [Radeon R9 290X/390X] [1002:aac8] 26:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Hawaii HDMI Audio [Radeon R9 290/290X / 390/390X] IOMMU group 14: [1022:145a] 27:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 145a IOMMU group 15: [1022:1456] 27:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) Platform Security Processor IOMMU group 16: [1022:145c] 27:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) USB 3.0 Host Controller IOMMU group 17: [1022:1455] 28:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Device 1455 IOMMU group 18: [1022:7901] 28:00.2 SATA controller: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] (rev 51) IOMMU group 19: [1022:1457] 28:00.3 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h (Models 00h-0fh) HD Audio Controller
Log for the VM
2018-03-21 07:11:45.935+0000: starting up libvirt version: 4.0.0, qemu version: 2.11.1, hostname: NAS LC_ALL=C PATH=/bin:/sbin:/usr/bin:/usr/sbin HOME=/ QEMU_AUDIO_DRV=none /usr/local/sbin/qemu -name 'guest=Windows 10,debug-threads=on' -S -object 'secret,id=masterKey0,format=raw,file=/var/lib/libvirt/qemu/domain-1-Windows 10/master-key.aes' -machine pc-i440fx-2.10,accel=kvm,usb=off,dump-guest-core=off,mem-merge=off -cpu host,hv_time,hv_relaxed,hv_vapic,hv_spinlocks=0x1fff,hv_vendor_id=none -drive file=/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd,if=pflash,format=raw,unit=0,readonly=on -drive file=/etc/libvirt/qemu/nvram/0eb9574c-5498-57aa-e5c6-4e209652b878_VARS-pure-efi.fd,if=pflash,format=raw,unit=1 -m 12288 -realtime mlock=off -smp 16,sockets=1,cores=16,threads=1 -uuid 0eb9574c-5498-57aa-e5c6-4e209652b878 -display none -no-user-config -nodefaults -chardev 'socket,id=charmonitor,path=/var/lib/libvirt/qemu/domain-1-Windows 10/monitor.sock,server,nowait' -mon chardev=charmonitor,id=monitor,mode=control -rtc base=localtime -no-hpet -no-shutdown -boot strict=on -device ial0 -device isa-serial,chardev=charserial0,id=serial0 -chardev 'socket,id=charchannel0,path=/var/lib/libvirt/qemu/channel/target/domain-1-Windows 10/org.qemu.guest_agent.0,server,nowait' -device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 -device vfio-pci,host=26:00.0,id=hostdev0,bus=pci.0,addr=0x5,romfile=/mnt/user/appdata/MSI.R9290X.8192.141029.rom -device vfio-pci,host=26:00.1,id=hostdev1,bus=pci.0,addr=0x6 -device usb-host,hostbus=5,hostaddr=2,id=hostdev2,bus=usb.0,port=1 -device usb-host,hostbus=5,hostaddr=3,id=hostdev3,bus=usb.0,port=2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x8 -msg timestamp=on 2018-03-21 07:11:45.935+0000: Domain id=1 is tainted: high-privileges 2018-03-21 07:11:45.935+0000: Domain id=1 is tainted: host-cpu 2018-03-21T07:11:46.026595Z qemu-system-x86_64: -chardev pty,id=charserial0: char device redirected to /dev/pts/0 (label charserial0)
XML
<domain type='kvm'> <name>Windows 10</name> <uuid>0eb9574c-5498-57aa-e5c6-4e209652b878</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>12582912</memory> <currentMemory unit='KiB'>12582912</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='3'/> <vcpupin vcpu='4' cpuset='4'/> <vcpupin vcpu='5' cpuset='5'/> <vcpupin vcpu='6' cpuset='6'/> <vcpupin vcpu='7' cpuset='7'/> <vcpupin vcpu='8' cpuset='8'/> <vcpupin vcpu='9' cpuset='9'/> <vcpupin vcpu='10' cpuset='10'/> <vcpupin vcpu='11' cpuset='11'/> <vcpupin vcpu='12' cpuset='12'/> <vcpupin vcpu='13' cpuset='13'/> <vcpupin vcpu='14' cpuset='14'/> <vcpupin vcpu='15' cpuset='15'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/0eb9574c-5498-57aa-e5c6-4e209652b878_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='16' threads='1'/> </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='file' device='disk'> <driver name='qemu' type='raw' cache='writeback'/> <source file='/mnt/user/domains/Windows 10/vdisk1.img'/> <target dev='hdc' bus='virtio'/> <boot order='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Windows.iso'/> <target dev='hda' bus='ide'/> <readonly/> <boot order='2'/> <address type='drive' controller='0' bus='0' target='0' unit='0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/virtio-win-0.1.141-1.iso'/> <target dev='hdb' bus='ide'/> <readonly/> <address type='drive' controller='0' bus='0' target='0' unit='1'/> </disk> <controller type='usb' index='0' model='ich9-ehci1'> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <master startport='0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/> </controller> <controller type='usb' index='0' model='ich9-uhci2'> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <controller type='pci' index='0' model='pci-root'/> <controller type='ide' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:0c:df:2e'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </interface> <serial type='pty'> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <channel type='unix'> <target type='virtio' name='org.qemu.guest_agent.0'/> <address type='virtio-serial' controller='0' bus='0' port='1'/> </channel> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x26' slot='0x00' function='0x0'/> </source> <rom file='/mnt/user/appdata/MSI.R9290X.8192.141029.rom'/> <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='0x26' slot='0x00' function='0x1'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x046d'/> <product id='0xc07d'/> </source> <address type='usb' bus='0' port='1'/> </hostdev> <hostdev mode='subsystem' type='usb' managed='no'> <source> <vendor id='0x2516'/> <product id='0x0021'/> </source> <address type='usb' bus='0' port='2'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </memballoon> </devices> </domain>
-
@DZMM how much power does your server draw on idle when no one is using the system?
I'm considering merging my two i7 builds into a single XEON build -
15 minutes ago, trurl said:
Probably some plugin using the linux 'find' command.
I suspect it might have been the ransomware plugin doing that stuff.
Files that seems to have come from the plugin was written too I could see from the plugins recommended by @DZMM.
After killing docker it seems my discs no longer spin up again, so I guess it was Plex keeping my system running.
-
1 minute ago, DZMM said:
if you're confident it was plex and you've closed Plex, just hit the kill button
I was just about to, but then I got a little worried.
After shutting down Plex, and only having "dockerd" running a new program have started up. I now see that the program "find" have started up.
The filename and path for this one is "/mnt/user/appdata/PlexMediaServer/Library/Application Support/Plex Media Server/ ...". This confuses me, how can this program have started up after I have shut down Plex?
-
31 minutes ago, DZMM said:
Try a combo of the open files and file activity plugins
Thanks, that gave quite an insight.
It seems it could be docker running. I recently installed Plex in a docker, that could be it.
But after stopping Plex from running, I still see some docker files being opened. Anything I can do about his?
-
Is there any way to find out what tasks, plugins etc. that interacts with my drives?
Normally my drives would spin down after 15 minutes of inactivity, and after that the server would go to sleep after 30 minutes of inactivity.
But now the server has been up and running for more than a day, and at least it should have went to sleep tonight while I was sleeping and not using the server.I can't seem to figure out why my drives are kept spinning.
Yesterday I tried spinning down all of the drives, but immediately after some of the drives spun up again. Now all of my drives are once again spinning.
-
2 minutes ago, L0rdRaiden said:
Open the shell and type mc
A file browser will appear, the option below are activates pressing alt+number
Navigate in the mnt/user folder and see if your shared are still there
Anyway you should report it as a bug because you are not the only one with this issue, I had it just after deleting a VM with its virtual disk
Rebooting did the trick
I'll see if I can find somewhere to report it as an bug
-
3 minutes ago, L0rdRaiden said:
I had the same issue
1st try to disable adblock or anything similar
2nd check with mc in CLI if the folders are still there
If nothing works try to reboot
How would I verify this via MC?
-
Yesterday I removed an unused drive from the array. To do this, I followed the guide here: https://lime-technology.com/wiki/Shrink_array
Everything seemed to work just well. But now I realise that I havn't got any shares. And I'm not able to create new shares (recreate the old ones)
I have uploaded my diagnostics, hoping someone here is able to tell me what I have done wrong, and if there's any way to rectify my mistake
-
2 hours ago, johnnie.black said:
Not as far as I know.
2 hours ago, bonienl said:No, this is not possible. The alternative is to set "no cache" for a share, which then reports the array size only, but file copies will bypass the cache in this case.
That's too bad, but I guess I'll just have to work with what I've got to work with then
Thank you so much both of you
-
On 12/5/2017 at 4:07 PM, johnnie.black said:
Available space = 8TB array + 2TB cache = 10TB total = 9.09TiB Windows
Used Space = 6.42TB = 5.83TiB
1 hour ago, johnnie.black said:Again it's correct, like the warning says the share (that's the Kasper folder) exists on disk1 even if it's not included, share also has cache enable, so:
Total = 2TB + 500GB + 2TB = 4.5TB = 4.09TiB
Regarding the cache.
Is it possible to leverage the cache as a jump-station for my files, but at the same time not let Windows know this space is available?
The only space I want shown is the space in the array.
-
25 minutes ago, bonienl said:
Personally I use midnight commander (mc) from a telnet session, but if you are not familiar with CLI then likely the Krusader docker can help (I am not using it and can't confirm).
16 minutes ago, johnnie.black said:A share is just a folder on the root of any disk, in this case just delete it from disk1.
Boom! I found out how to boot up MC from PuTTU and have now deleted the folder from disk 1.
Windows responded promptly.
Thank you very much both of you. Now I both understand how space for the shares is calculated, and I know how to use MC
-
5 minutes ago, bonienl said:
Personally I use midnight commander (mc) from a telnet session, but if you are not familiar with CLI then likely the Krusader docker can help (I am not using it and can't confirm).
I should be able to figure out a CLI, but I'm still not sure how I would get around moving the share.
Is there a guide somewhere that I'm not knowing exists?
-
Just now, bonienl said:
unRAID will not move an existing share when you update the include or exclude list afterwards.
You either include disk1 for your share Kasper or move the share Kasper to disk5.
How would I do this?
-
Sync errors keeps coming - how do I read the logs?
in General Support
Posted
My array keeps spitting out sync errors that is getting corrected. Problem is, that when I do a new parity check, it finds new errors.
I'm fearing that one of my drives might have gone bad, but I'm not sure how to determine this.
I have added syslog and diagnostics, hoping this is where we can find such information.
I'd greatly appreciate help to read the logs. If you can see whats wrong in the logs, please do guide me to what it is that I should look for so I'm better equipped next time
nas-diagnostics-20180424-0748.zip
nas-syslog-20180424-0748.zip