dacmcbibs

Members
  • Posts

    10
  • Joined

  • Last visited

Everything posted by dacmcbibs

  1. I had this challenge as well, and wanted to share my experience in case it helps others. My issue turned out to be the extension Ghostery. White listing the unraid server was not enough. The white screens wouldn't stop until I paused or disabled the add-in entirely.
  2. Thanks for the tip.. that would be unfortunate since i already replaced this RAM once (almost exactly a year ago) .. but i guess i will be running a memtest again Thanks for the pointer.
  3. I am starting to see errors on my cache drive pool (sample attached) cachedriveerrors.txt I suspect that one of the drives in the pool is starting to fail , but when i try to run smart tests on the drive nothing seems to happen (no feedback after the button click) The btrfs dev stats are not showing any errors: root@TheBeast:~# btrfs dev stats /mnt/cache [/dev/nvme0n1p1].write_io_errs 0 [/dev/nvme0n1p1].read_io_errs 0 [/dev/nvme0n1p1].flush_io_errs 0 [/dev/nvme0n1p1].corruption_errs 0 [/dev/nvme0n1p1].generation_errs 0 [/dev/nvme1n1p1].write_io_errs 0 [/dev/nvme1n1p1].read_io_errs 0 [/dev/nvme1n1p1].flush_io_errs 0 [/dev/nvme1n1p1].corruption_errs 0 [/dev/nvme1n1p1].generation_errs 0 I also attached the smart log that the system does have Samsung_SSD_960_EVO_250GB_S3ESNX0J930294R-20190524-1033.txt Can anyone recommend how to troubleshoot this?
  4. that was the conclusion I eventually came to as well Thanks for your reply
  5. Thanks for the pointer. It took several 24 hour memtests before it actually occurred but i did finally find a bad memory DIMM I've replaced the faulty memory and ran a clean 24 hour memtest. Hopefully the system will be stable now. I appreciate the help!
  6. FYI - Unraid's build in memtest would not boot, but I created bootable media for memtest and it came back clean
  7. Attached are the diagnostic logs requested.. about to run a memtest unraid-diagnostics-20180325-1541.zip
  8. Thanks for the quick reply, here is the output from the dev stats command: [/dev/nvme1n1p1].write_io_errs 0 [/dev/nvme1n1p1].read_io_errs 0 [/dev/nvme1n1p1].flush_io_errs 0 [/dev/nvme1n1p1].corruption_errs 159 [/dev/nvme1n1p1].generation_errs 0 [/dev/nvme0n1p1].write_io_errs 0 [/dev/nvme0n1p1].read_io_errs 0 [/dev/nvme0n1p1].flush_io_errs 0 [/dev/nvme0n1p1].corruption_errs 159 [/dev/nvme0n1p1].generation_errs 0
  9. every few weeks i run into an issue with my cache drives where it ends up taking the system off line. The disk log shows the following: ar 24 10:21:42 TheBeast kernel: BTRFS error (device nvme1n1p1): unable to find ref byte nr 505982324736 parent 0 root 5 owner 5166944 offset 0 Mar 24 10:21:42 TheBeast kernel: BTRFS: error (device nvme1n1p1) in __btrfs_free_extent:7073: errno=-2 No such entry Mar 24 10:21:42 TheBeast kernel: BTRFS info (device nvme1n1p1): forced readonly Mar 24 10:21:42 TheBeast kernel: BTRFS: error (device nvme1n1p1) in btrfs_run_delayed_refs:3089: errno=-2 No such entry Mar 24 10:21:42 TheBeast kernel: BTRFS error (device nvme1n1p1): pending csums is 8060928 I also see BTRFS errors in the syslog around the same time. I've repaired and even completely re-created the cache. I have 2 drives in the cache pool both Samsung SSD 960 256 GB drives, every few weeks the issue reoccurs. What information can i share to help diagnose why this happens and how to avoid it from occurring again?
  10. I'm looking for a little help with Intel IGD pass-through. Every time i try to enable pass-through the VM refuses to boot and i find the following error in the logs: 2018-03-04T15:30:19.849395Z qemu-system-x86_64: -device vfio-pci,host=00:02.0,id=hostdev0,bus=pci.0,addr=0x2: Failed to mmap 0000:00:02.0 BAR 2. Performance may be slow I have tried the following: Set VNC as the default graphics card. when trying to connect it tells me that the guest has not initialized the display (yet) Turning the Hyper-V setting on and off Different combinations of Bios and machine (mostly SeaBIOS and i440fx 2.10) Setting the primary GPU in the bios (to every option available) Turning Enable PCIe ACS Override on and off Tried using RDP to get to the machine after booting In every case i received the same warning, and cannot get any video from the VM as long as the Intel IGD is enabled, if i go VNC only everything works as expected. All other devices pass-through with no issue (audio, keyboard, mouse, etc) Any advice would be greatly appreciated. Below are my system info , VM configuration , IOMMU groups , and my syslinux configuration. Let me know if any additional information is needed to help diagnose the root cause of this issue. Thank you in advance. System info: Model: Custom M/B: ASUSTeK COMPUTER INC. - PRIME Z370-A CPU: Intel® Core™ i7-8700K CPU @ 3.70GHz HVM: Enabled IOMMU: Enabled VM configuration <domain type='kvm'> <name>Windows 10</name> <uuid>7898cba2-7684-822d-6eac-a7e0e6220cc6</uuid> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>4194304</memory> <currentMemory unit='KiB'>4194304</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='2'/> <vcpupin vcpu='1' cpuset='8'/> <vcpupin vcpu='2' cpuset='3'/> <vcpupin vcpu='3' cpuset='9'/> </cputune> <os> <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='2' threads='2'/> </cpu> <clock offset='localtime'> <timer name='rtc' tickpolicy='catchup'/> <timer name='pit' tickpolicy='delay'/> <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='0x06' function='0x0'/> </disk> <disk type='file' device='cdrom'> <driver name='qemu' type='raw'/> <source file='/mnt/user/isos/Win10_1709_English_x64.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='0x05' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:63:52:6b'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </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='tablet' bus='usb'> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'/> <input type='keyboard' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'> <listen type='address' address='0.0.0.0'/> </graphics> <video> <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </video> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x00' slot='0x1f' function='0x3'/> </source> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </memballoon> </devices> </domain> PCI Devices and IOMMU Groups IOMMU group 0: [8086:3ec2] 00:00.0 Host bridge: Intel Corporation Device 3ec2 (rev 07) IOMMU group 1: [8086:3e92] 00:02.0 VGA compatible controller: Intel Corporation Device 3e92 IOMMU group 2: [8086:a2af] 00:14.0 USB controller: Intel Corporation 200 Series PCH USB 3.0 xHCI Controller IOMMU group 3: [8086:a2ba] 00:16.0 Communication controller: Intel Corporation 200 Series PCH CSME HECI #1 IOMMU group 4: [8086:a282] 00:17.0 SATA controller: Intel Corporation 200 Series PCH SATA controller [AHCI mode] IOMMU group 5: [8086:a2e7] 00:1b.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #17 (rev f0) IOMMU group 6: [8086:a290] 00:1c.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #1 (rev f0) IOMMU group 7: [8086:a294] 00:1c.4 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #5 (rev f0) IOMMU group 8: [8086:a298] 00:1d.0 PCI bridge: Intel Corporation 200 Series PCH PCI Express Root Port #9 (rev f0) IOMMU group 9: [8086:a2c9] 00:1f.0 ISA bridge: Intel Corporation Device a2c9 [8086:a2a1] 00:1f.2 Memory controller: Intel Corporation 200 Series PCH PMC [8086:a2f0] 00:1f.3 Audio device: Intel Corporation 200 Series PCH HD Audio [8086:a2a3] 00:1f.4 SMBus: Intel Corporation 200 Series PCH SMBus Controller IOMMU group 10: [8086:15b8] 00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V IOMMU group 11: [144d:a804] 01:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 IOMMU group 12: [1b21:2142] 03:00.0 USB controller: ASMedia Technology Inc. Device 2142 IOMMU group 13: [144d:a804] 04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM961/PM961 Syslinux configuration: default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label unRAID OS menu default kernel /bzimage append vfio-pci.ids=8086:a2f0 modprobe.blacklist=i2c_i801,i2c_smbus intel_pstate=disable initrd=/bzroot 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