Jump to content

MothyTim

Members
  • Content Count

    93
  • Joined

  • Last visited

Community Reputation

0 Neutral

About MothyTim

  • Rank
    Advanced Member
  • Birthday 12/25/1964

Converted

  • Gender
    Male
  • URL
    http://www.timstephens.co.uk
  • Location
    Plymouth, UK.
  • Personal Text
    MB: Gigabyte Z390 UD | CPU: Intel® Core™ i7-8700K CPU @ 3.70GHz | RAM: 16 GiB DDR4 | Cache: M2 Crucial MX500 250GB SSD | Parity: 3TB | Array: 3x3TB | Nvidia Geforce GTX1050 Graphics as pass-through.

Recent Profile Visitors

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

  1. Ok so I updated yesterday and in 24 hrs docker image has grown 10% from 67% to 77%! So still a problem for me!
  2. Ok thanks guys, I’ll try and work out which slot it’s referring to and then I might be able to workout what’s going on! Cheers, Tim
  3. Hi, I have a recurring error that I have noticed in the logs that I can't track down! All my PCIe cards seem to function correctly. `does anyone know what they are telling me? Thanks, Tim Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:38:22 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Aug 13 16:39:34 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:39:34 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:39:34 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:39:34 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Aug 13 16:39:35 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:39:35 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:39:35 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:39:35 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First) Aug 13 16:39:41 Tower kernel: pcieport 0000:00:1b.4: AER: Corrected error received: 0000:00:1b.4 Aug 13 16:39:41 Tower kernel: pcieport 0000:00:1b.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) Aug 13 16:39:41 Tower kernel: pcieport 0000:00:1b.4: device [8086:a32c] error status/mask=00000001/00002000 Aug 13 16:39:41 Tower kernel: pcieport 0000:00:1b.4: [ 0] RxErr (First)
  4. I believe this is because Plex have stopped using Gracenote, so there will be problems with the music library until the transition is complete! Plex never give a time frame so I guess we wait!
  5. Hi, I’ve noticed very high RAM usage all of a sudden! Anyone else noticed this? Was there an update recently? cheers, Tim
  6. I have tried booting Unraid legacy and that has made no difference. I don’t think it going to work, it’s a shame but not the end of the world just would have been nice for a couple of things! It is strange the a card from 2005 works happily in OVMF as it doesn’t support UEFI! I also tried booting into Windows baremetal and dumping the BIOS with GPU-Z but that says that the card doesn’t support reading bios! Anyone know anything else I can try? cheers, Tim
  7. This is the part of the log relating to the failed start of the VM! Jun 19 14:59:58 Tower kernel: vfio-pci 0000:08:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none Jun 19 14:59:58 Tower kernel: br0: port 3(vnet1) entered blocking state Jun 19 14:59:58 Tower kernel: br0: port 3(vnet1) entered disabled state Jun 19 14:59:58 Tower kernel: device vnet1 entered promiscuous mode Jun 19 14:59:58 Tower kernel: br0: port 3(vnet1) entered blocking state Jun 19 14:59:58 Tower kernel: br0: port 3(vnet1) entered forwarding state Jun 19 14:59:59 Tower kernel: vfio-pci 0000:08:00.0: enabling device (0000 -> 0003) Jun 19 14:59:59 Tower kernel: qemu-system-x86[24486]: segfault at a8 ip 0000563b04d4a9ea sp 00007ffdb3bcb010 error 4 in qemu-system-x86_64[563b04ce2000+4cc000] Jun 19 14:59:59 Tower kernel: Code: f9 ff 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 53 48 89 fb 48 83 ec 08 48 8b 6f 58 e8 1e dd ff ff 48 89 df e8 76 e9 ff ff <48> 8b 85 a8 00 00 00 48 85 c0 74 2e 8b 93 a0 00 00 00 39 90 a0 00 Jun 19 14:59:59 Tower kernel: br0: port 3(vnet1) entered disabled state Jun 19 14:59:59 Tower kernel: device vnet1 left promiscuous mode Jun 19 14:59:59 Tower kernel: br0: port 3(vnet1) entered disabled state Jun 19 14:59:59 Tower kernel: vfio-pci 0000:08:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=none
  8. I've attached my log file, there are loads of errors in there! Not sure if they're related to this or something else? tower-syslog-20190619-1324.zip
  9. Ok tried dumping the GPU BIOS but got an input/output error! So tried downloading from Techpowerup.com but still get the same error! Here's my syslinux in case that helps.
  10. Hi, I have set-up a Win XP VM and I’m getting this error “internal error: qemu unexpectedly closed the monitor” whenever I try and pass through an old ATI AIW X600 PCIe graphics card, the card will pass through fine using OVMF to an Ubuntu VM! It seems to be an issue with Seabios pass through only! The ATI card shows as 2 graphics cards as it has capture and a TV card built in. Here’s my XML 79 <model type='virtio'/> 80 <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> 81 </interface> 82 <serial type='pty'> 83 <target type='isa-serial' port='0'> 84 <model name='isa-serial'/> 85 </target> 86 </serial> 87 <console type='pty'> 88 <target type='serial' port='0'/> 89 </console> 90 <channel type='unix'> 91 <target type='virtio' name='org.qemu.guest_agent.0'/> 92 <address type='virtio-serial' controller='0' bus='0' port='1'/> 93 </channel> 94 <input type='tablet' bus='usb'> 95 <address type='usb' bus='0' port='1'/> 96 </input> 97 <input type='mouse' bus='ps2'/> 98 <input type='keyboard' bus='ps2'/> 99 <hostdev mode='subsystem' type='pci' managed='yes' xvga='yes'> 100 <driver name='vfio'/> 101 <source> 102 <address domain='0x0000' bus='0x08' slot='0x00' function='0x0'/> 103 </source> 104 <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> 105 </hostdev> 106 <hostdev mode='subsystem' type='pci' managed='yes'> 107 <driver name='vfio'/> 108 <source> 109 <address domain='0x0000' bus='0x07' slot='0x00' function='0x0'/> 110 </source> 111 <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> 112 </hostdev> 113 <hostdev mode='subsystem' type='usb' managed='no'> 114 <source> 115 <vendor id='0x046d'/> 116 <product id='0xc05b'/> 117 </source> 118 <address type='usb' bus='0' port='2'/> 119 </hostdev> 120 <hostdev mode='subsystem' type='usb' managed='no'> 121 <source> 122 <vendor id='0x1a2c'/> 123 <product id='0x0c21'/> 124 </source> 125 <address type='usb' bus='0' port='3'/> 126 </hostdev> 127 <memballoon model='none'/> 128 </devices> 129 </domain> 130 IOMMU groups acs overrides enabled! IOMMU group 0: [8086:3ec2] 00:00.0 Host bridge: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers (rev 07) IOMMU group 1: [8086:1901] 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) (rev 07) IOMMU group 2: [8086:3e92] 00:02.0 VGA compatible controller: Intel Corporation UHD Graphics 630 (Desktop) IOMMU group 3: [8086:a379] 00:12.0 Signal processing controller: Intel Corporation Cannon Lake PCH Thermal Controller (rev 10) IOMMU group 4: [8086:a36d] 00:14.0 USB controller: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller (rev 10) [8086:a36f] 00:14.2 RAM memory: Intel Corporation Cannon Lake PCH Shared SRAM (rev 10) IOMMU group 5: [8086:a360] 00:16.0 Communication controller: Intel Corporation Cannon Lake PCH HECI Controller (rev 10) IOMMU group 6: [8086:a352] 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) IOMMU group 7: [8086:a340] 00:1b.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 (rev f0) IOMMU group 8: [8086:a342] 00:1b.2 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #19 (rev f0) IOMMU group 9: [8086:a343] 00:1b.3 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #20 (rev f0) IOMMU group 10: [8086:a338] 00:1c.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 (rev f0) IOMMU group 11: [8086:a33a] 00:1c.2 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #3 (rev f0) IOMMU group 12: [8086:a33b] 00:1c.3 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #4 (rev f0) IOMMU group 13: [8086:a33c] 00:1c.4 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #5 (rev f0) IOMMU group 14: [8086:a330] 00:1d.0 PCI bridge: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 (rev f0) IOMMU group 15: [8086:a305] 00:1f.0 ISA bridge: Intel Corporation Z390 Chipset LPC/eSPI Controller (rev 10) [8086:a348] 00:1f.3 Audio device: Intel Corporation Cannon Lake PCH cAVS (rev 10) [8086:a323] 00:1f.4 SMBus: Intel Corporation Cannon Lake PCH SMBus Controller (rev 10) [8086:a324] 00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller (rev 10) IOMMU group 16: [10de:1c81] 01:00.0 VGA compatible controller: NVIDIA Corporation GP107 [GeForce GTX 1050] (rev a1) [10de:0fb9] 01:00.1 Audio device: NVIDIA Corporation GP107GL High Definition Audio Controller (rev a1) IOMMU group 17: [1106:3403] 03:00.0 FireWire (IEEE 1394): VIA Technologies, Inc. VT6315 Series Firewire Controller IOMMU group 18: [10ec:8168] 04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) IOMMU group 19: [10ec:8168] 06:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 16) IOMMU group 20: [1095:3132] 07:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132 Serial ATA Raid II Controller (rev 01) IOMMU group 21: [1002:5b62] 08:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV370 [Radeon X600/X600 SE] [1002:5b72] 08:00.1 Display controller: Advanced Micro Devices, Inc. [AMD/ATI] RV380 [Radeon X300/X550/X1050 Series] (Secondary) The Win XP VM boots fine using VNC. Hoping someone has some ideas? cheers, Tim
  11. The drive is a bare metal install of Windows 10 that I use as my Win 10 VM. I did it this way as I was having out of memory problems and so wanted to be able to boot directly into windows, I've now solved the out of memory issue (turned out to be a dodgy SATA card!!) but would like to retain the ability to boot straight into Windows for the occasional time that I need all the horsepower the machine can provide! The partition that I want to mount at boot is for the swap file, this really helped with the issues I was having so want to keep it! So will it cause me issues if I just leave the whole drive mounted? Cheers, Tim
  12. I thought, maybe wrongly, that it would cause problems if the drive is mounted and then used as a VM?
  13. I had a feeling you'd say that! 😂 Thanks for the example, I'll give it a go!
  14. @jonp @testdasi So I've found the problem! It seems it was the SATA card! Very hard to work out as it was only a problem when moving or dealing with large files! I realized that it only happened when I was accessing the 500gb hard drive (D drive in windows) that I use for capturing video and other large files that I don't need on the array or where I want speed of access. It is connected to a SATA card that I have passed through to the VM's. I was again trying to make a USB stick installer and it kept failing, crashing the whole system. I realised that the downloads folder was on the D drive so I tried it on the C drive and it worked fine! So I've swapped out the card and works fine from the D drive as well now! I've also added a swap file, which also seems to have made a difference! I have a stable system at last! Thanks for everyone's help and sorry for all my rants of frustration!!