flaggart

Members
  • Posts

    107
  • Joined

  • Last visited

Everything posted by flaggart

  1. Replugged, Unraid-Kernel-Helper Plugin still says no custom loaded modules found. Output of "lsusb -v" attached lsusb.txt
  2. Yes, it is USB. I've rebooted several times and tried all USB ports - I thought I was going mad and not overwriting the boot files properly!! It seems there are a few reports of 5990 not being detected regardless of drivers, so not sure TBS drivers would make any difference, but if it is no hassle for you it would be nice to test The device is listed under lsusb but /dev/dvb does not exist and it does not show up under your plugin.
  3. Ah, I see. I tried LibreELEC but it does not detect my TBS 5990. Thanks anyway.
  4. Hello Sorry if I am being a bit thick here, but all I wan't to do is build 6.8.3 with TBS drivers. There is no mention of how to specify this using env on docker hub or the first post here. Can someone please advise? Thanks
  5. I had the same issue after update. Browser (Vivaldi) would not load the client and had this JS error. It worked fine in Chromium, and was fine after I unpinned the tab in Vivaldi and reloaded the page, ensuring adblock+tracker protection was off.
  6. I am not sure which drive area you mean if you mean the white 4x drive bay directly above the PSU - there should not be any issues with this regardless of cables? if you mean the space with velcro strap to the left of the PSU in the images above, I think I had to orient the drive length ways so that the connectors were pointing towards the cable-management hole through to the other chamber. This matches the more recent image from stuntman83 above.
  7. I retired it towards the end of 2019, so it had a good 4.5 years. I had three fans in the drive chamber using Fan Auto Control to ramp up with drive temp and never had an issue. If anything, the 4 drives in the main chamber were the ones that got the hottest so I'd suggest putting drives there that maybe have less use or fewer platters, whatever makes them less likely to heat up. In terms of vibration / noise, I had the box in the same room I slept in for a few years. I would not describe it as quiet but it wasn't bothersome.
  8. Hello I have been experiencing similar issue when rebooting or shutting down a Windows 10 VM with a RTX 2070 Super and motherboard USB controller passed through. I added pcie_no_flr to my syslinux.cfg as suggested here blindly and noticed no difference. I then took the time to read and understand the thread and realised it was a specific pci-e address and looked up the correct address for my own USB controller which I found from Tools > System Devices. I have reset, hibernated, rebooted and powered offthe VM since and with fingers-crossed no issue so far. Just thought I'd post this here in case anyone else has similar issues on different hardware and is as slow on the uptake as I am.
  9. Same here unfortunately
  10. Hi all Over the past few months I have been experiencing complete hard lockup of Unraid and have to power cycle. Each time it happens as a direct result of attempted to reboot the same Windows 10 VM (via the shutdown menu inside the VM, not using web GUI). Syslog as follows: May 4 11:17:41 SERVER kernel: mdcmd (552): spindown 10 May 4 12:25:40 SERVER kernel: mdcmd (553): spindown 0 May 4 13:22:59 SERVER kernel: mdcmd (554): spindown 10 May 4 13:23:00 SERVER kernel: mdcmd (555): spindown 5 May 4 13:52:18 SERVER kernel: mdcmd (556): spindown 9 May 4 16:04:17 SERVER kernel: rcu: INFO: rcu_sched detected stalls on CPUs/tasks: May 4 16:04:17 SERVER kernel: rcu: 24-...0: (1 GPs behind) idle=a12/1/0x4000000000000000 softirq=109480389/109480389 fqs=14466 May 4 16:04:17 SERVER kernel: rcu: (detected by 25, t=60002 jiffies, g=587531517, q=76713) May 4 16:04:17 SERVER kernel: Sending NMI from CPU 25 to CPUs 24: May 4 16:04:17 SERVER kernel: NMI backtrace for cpu 24 May 4 16:04:17 SERVER kernel: CPU: 24 PID: 307 Comm: CPU 1/KVM Tainted: P O 4.19.107-Unraid #1 May 4 16:04:17 SERVER kernel: Hardware name: ASUSTek Computer INC. TS700-E7-RS8/Z9PE-D16 Series, BIOS 5601 06/11/2015 May 4 16:04:17 SERVER kernel: RIP: 0010:qi_submit_sync+0x154/0x2db May 4 16:04:17 SERVER kernel: Code: 30 02 0f 84 40 01 00 00 4d 8b 96 b0 00 00 00 49 8b 42 10 83 3c 30 03 75 0b 41 bc f5 ff ff ff e9 27 01 00 00 49 8b 06 8b 48 34 <f6> c1 10 74 68 49 8b 06 8b 80 80 00 00 00 c1 f8 04 41 39 c3 75 57 May 4 16:04:17 SERVER kernel: RSP: 0018:ffffc90006a8bb50 EFLAGS: 00000093 May 4 16:04:17 SERVER kernel: RAX: ffffc9000001f000 RBX: 0000000000000100 RCX: 0000000000000000 May 4 16:04:17 SERVER kernel: RDX: 0000000000000001 RSI: 000000000000006c RDI: ffff88903f418a00 May 4 16:04:17 SERVER kernel: RBP: ffffc90006a8bba8 R08: 0000000000640000 R09: 0000000000000000 May 4 16:04:17 SERVER kernel: R10: ffff88903f418a00 R11: 000000000000001a R12: 00000000000001b0 May 4 16:04:17 SERVER kernel: R13: ffff88903f418a00 R14: ffff88903f40f400 R15: 0000000000000086 May 4 16:04:17 SERVER kernel: FS: 000014bc64dff700(0000) GS:ffff88a03fa00000(0000) knlGS:0000000000000000 May 4 16:04:17 SERVER kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 4 16:04:17 SERVER kernel: CR2: ffffe4881907d478 CR3: 000000108a6ba005 CR4: 00000000001626e0 May 4 16:04:17 SERVER kernel: Call Trace: May 4 16:04:17 SERVER kernel: modify_irte+0xf0/0x136 May 4 16:04:17 SERVER kernel: intel_irq_remapping_deactivate+0x2d/0x47 May 4 16:04:17 SERVER kernel: __irq_domain_deactivate_irq+0x27/0x33 May 4 16:04:17 SERVER kernel: irq_domain_deactivate_irq+0x15/0x22 May 4 16:04:17 SERVER kernel: __free_irq+0x1d8/0x238 May 4 16:04:17 SERVER kernel: free_irq+0x5d/0x75 May 4 16:04:17 SERVER kernel: vfio_msi_set_vector_signal+0x84/0x231 May 4 16:04:17 SERVER kernel: ? flush_workqueue+0x2bf/0x2e3 May 4 16:04:17 SERVER kernel: vfio_msi_set_block+0x6c/0xac May 4 16:04:17 SERVER kernel: vfio_msi_disable+0x61/0xa0 May 4 16:04:17 SERVER kernel: vfio_pci_set_msi_trigger+0x44/0x230 May 4 16:04:17 SERVER kernel: ? pci_bus_read_config_word+0x44/0x66 May 4 16:04:17 SERVER kernel: vfio_pci_ioctl+0x52d/0x9a2 May 4 16:04:17 SERVER kernel: ? vfio_pci_config_rw+0x209/0x2a6 May 4 16:04:17 SERVER kernel: ? __seccomp_filter+0x39/0x1ed May 4 16:04:17 SERVER kernel: vfs_ioctl+0x19/0x26 May 4 16:04:17 SERVER kernel: do_vfs_ioctl+0x533/0x55d May 4 16:04:17 SERVER kernel: ksys_ioctl+0x37/0x56 May 4 16:04:17 SERVER kernel: __x64_sys_ioctl+0x11/0x14 May 4 16:04:17 SERVER kernel: do_syscall_64+0x57/0xf2 May 4 16:04:17 SERVER kernel: entry_SYSCALL_64_after_hwframe+0x44/0xa9 May 4 16:04:17 SERVER kernel: RIP: 0033:0x14bc687a54b7 May 4 16:04:17 SERVER kernel: Code: 00 00 90 48 8b 05 d9 29 0d 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 2e 0f 1f 84 00 00 00 00 00 b8 10 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d a9 29 0d 00 f7 d8 64 89 01 48 May 4 16:04:17 SERVER kernel: RSP: 002b:000014bc64dfe2e8 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 May 4 16:04:17 SERVER kernel: RAX: ffffffffffffffda RBX: 000014b84150a200 RCX: 000014bc687a54b7 May 4 16:04:17 SERVER kernel: RDX: 000014bc64dfe2f0 RSI: 0000000000003b6e RDI: 000000000000004b May 4 16:04:17 SERVER kernel: RBP: 000014b84150a200 R08: 000000000000006c R09: 00000000ffffff00 May 4 16:04:17 SERVER kernel: R10: 000014b82cd8406b R11: 0000000000000246 R12: 000000000000006a May 4 16:04:17 SERVER kernel: R13: 0000000000000080 R14: 0000000000000002 R15: 000014b84150a200 The output of the VM at this point is the Windows shutdown sequence saying "Restarting...". If I try to use Virsh to shutdown I get the following, and shortly after a total Unraid lockup: virsh # destroy "Windows 10" error: Failed to destroy domain Windows 10 error: Timed out during operation: cannot acquire state change lock (held by monitor=remoteDispatchDomainReset) General info: Unraid 6.8.3 Platform: Asus Z9PE-D16 with 2x Xeon 2667 v2 RAM: 128GB ECC The VM is pinned to the second physical CPU, which is isolated from Unraid. It has a GTX 2070 Super and NVMe drive passed through to it. <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm' id='2'> <name>Windows 10</name> <uuid>39ac96f3-a777-0c5e-419f-596878b407e9</uuid> <description>Win-10</description> <metadata> <vmtemplate xmlns="unraid" name="Windows 10" icon="windows.png" os="windows10"/> </metadata> <memory unit='KiB'>17301504</memory> <currentMemory unit='KiB'>17301504</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>16</vcpu> <iothreads>2</iothreads> <cputune> <vcpupin vcpu='0' cpuset='8'/> <vcpupin vcpu='1' cpuset='24'/> <vcpupin vcpu='2' cpuset='9'/> <vcpupin vcpu='3' cpuset='25'/> <vcpupin vcpu='4' cpuset='10'/> <vcpupin vcpu='5' cpuset='26'/> <vcpupin vcpu='6' cpuset='11'/> <vcpupin vcpu='7' cpuset='27'/> <vcpupin vcpu='8' cpuset='12'/> <vcpupin vcpu='9' cpuset='28'/> <vcpupin vcpu='10' cpuset='13'/> <vcpupin vcpu='11' cpuset='29'/> <vcpupin vcpu='12' cpuset='14'/> <vcpupin vcpu='13' cpuset='30'/> <vcpupin vcpu='14' cpuset='15'/> <vcpupin vcpu='15' cpuset='31'/> <emulatorpin cpuset='0,16'/> <iothreadpin iothread='1' cpuset='1,17'/> <iothreadpin iothread='2' cpuset='2,18'/> </cputune> <numatune> <memory mode='preferred' nodeset='1'/> </numatune> <resource> <partition>/machine</partition> </resource> <os> <type arch='x86_64' machine='pc-i440fx-3.1'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/39ac96f3-a777-0c5e-419f-596878b407e9_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='1278467890ab'/> </hyperv> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' cores='8' threads='2'/> <cache mode='passthrough'/> <feature policy='require' name='topoext'/> </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> <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> <controller type='usb' index='0' model='ich9-ehci1'> <alias name='usb'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/> </controller> <controller type='usb' index='0' model='ich9-uhci1'> <alias name='usb'/> <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'> <alias name='usb'/> <master startport='2'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/> </controller> <controller type='usb' index='0' model='ich9-uhci3'> <alias name='usb'/> <master startport='4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/> </controller> <interface type='bridge'> <mac address='52:54:00:be:8c:35'/> <source bridge='br0'/> <target dev='vnet1'/> <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/2'/> <target type='isa-serial' port='0'> <model name='isa-serial'/> </target> <alias name='serial0'/> </serial> <console type='pty' tty='/dev/pts/2'> <source path='/dev/pts/2'/> <target type='serial' port='0'/> <alias name='serial0'/> </console> <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-2-Windows 10/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='tablet' bus='usb'> <alias name='input0'/> <address type='usb' bus='0' port='1'/> </input> <input type='mouse' bus='ps2'> <alias name='input1'/> </input> <input type='keyboard' bus='ps2'> <alias name='input2'/> </input> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x83' slot='0x00' function='0x0'/> </source> <alias name='hostdev0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x83' slot='0x00' function='0x1'/> </source> <alias name='hostdev1'/> <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='0x00' slot='0x1d' function='0x0'/> </source> <alias name='hostdev2'/> <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='0x82' slot='0x00' function='0x0'/> </source> <boot order='1'/> <alias name='hostdev3'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x83' slot='0x00' function='0x2'/> </source> <alias name='hostdev4'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x09' function='0x0'/> </hostdev> <hostdev mode='subsystem' type='pci' managed='yes'> <driver name='vfio'/> <source> <address domain='0x0000' bus='0x83' slot='0x00' function='0x3'/> </source> <alias name='hostdev5'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x0a' function='0x0'/> </hostdev> <memballoon model='none'/> </devices> <seclabel type='dynamic' model='dac' relabel='yes'> <label>+0:+100</label> <imagelabel>+0:+100</imagelabel> </seclabel> </domain> Can anyone advise what the issue might be, or at least on a way to deal with this without it taking down the entire system? Thanks
  11. Surprised there is not more activity from others in this thread, it would be amazing to be able to virtualise integrated graphics in the same way as the rest of the cpu and have multiple vms benefit from it. I would ask you for more details to try myself but I didn't think something like this would be possible and now I am running xeons.
  12. I would also like this. In its absence I have been referring to this post which suggests the same information is available without the tool.
  13. Hi all Like many here (I assume), I am planning on a Ryzen 3000 series build in the next couple of months, to replace my existing setup. This brings with it some choices around chipsets, pci-e lanes, etc. My current setup is: Node 804 (limited to Micro ATX or smaller) i7-2600k Supermirco Micro ATX Broadcom 9207-8i 8 port HBA (PCI-e 3.0 8x) TBS dual DVB tuner (PCI-e 2.0 1x) Switching to Ryzen has certain limitations: Lack of integrated graphics - meaning I have to fit a GPU on a mATX board reducing the number of available slots for other cards Only 6 (B450) or 8 (X470) PCI-e 2.0 lanes from chipset. So the best case would be PCI-e 4x 2.0 for the 9201-8i (in a 16x mechanical slot), meaning it will only be running at 2GB/s total instead of 8GB/s. This works out to ~ 2Gbit per drive so it is above SATA1 speed and I assume unlikely to limit performance much for mechanical disks - can anyone confirm? Will the card even function like this? Generally, will Ryzen boards boot (and will unRaid function) if no GPU is present? I am aware that new boards with X570 chipset may solve this problem (12 Gen 4 lanes from chipset), but trying to clarify if it is possible to go with a cheaper chipset.
  14. I just used the velcro straps that were already there - I think they are supposed to be for cable management, it wasn't the greatest arrangement. I just settled for one drive there.
  15. It is a: OWC OWCMM52T35 - OWC Multi-Mount 3.5 to 5.25 Bracket I have also used a "Nexus DoubleTwin" for the same purpose.
  16. Hi, Since unraid v 6.6.1 I have been having issues with auto updating of the system and plugins. This was because wget was unable to verify certificates, due to conflicting versions of openssl. I think this is because your plugin installs libssl1-1.1.0g. Unraid syslog shows "OpenSSL version mismatch. Built against 1010100f, you have 1010007f#015" Uninstalling the plugin resolved the issue. I have started using a tvheadend docker container, but if you still have the will/interest to maintain this, I would prefer the plugin. Thanks.
  17. After updating to 6.4 initially everything is OK, however after a while all disks attached to my SuperMicro AOC-SAS2LP-MV8 slow massively. Disks attached to the motherboard directly are not affected. The worst affected disks slow to 2 MB/sec read. The least affected slow to 40 MB/sec. After rebooting, everything is again OK for a short while before the problem returns. I know this HBA card is listed as potentially having issues - specifically random parity errors upon reboot - but I have not observed this issue and so have continued to use it. I am wondering, has support for this card been removed, or is there an issue? Logs attached. bigbox-diagnostics-20180116-1939.zip
  18. There is a similar deal in the UK for a card with the same chipset. Reduced from £217 to £100 (confirmed by Camelizer which says the previous low was £180 in October). May be of use to some of you - I have just ordered. https://www.amazon.co.uk/gp/product/B0085FT2JC/ref=od_aui_detailpages00?ie=UTF8&psc=1
  19. Hi all, Update went smoothly however syslog is now spammed with the following: Jan 15 07:17:01 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [753ab0] Jan 15 07:17:01 Tower kernel: SQUASHFS error: Unable to read page, block 753ab0, size f38 Jan 15 07:17:01 Tower kernel: SQUASHFS error: Unable to read fragment cache entry [7549e8] Jan 15 07:17:01 Tower kernel: SQUASHFS error: Unable to read page, block 7549e8, size 38fc
  20. Same issue here. I had to roll back to 4.2.3 - I had not updated for a while. Thanks for your efforts, much appreciated.
  21. https://wiki.lime-technology.com/Hardware_Compatibility#PCI_SATA_Controllers
  22. Sounds like Guacamole VNC/RDP web proxy - http://guacamole.incubator.apache.org/
  23. Hi all, I have been unable to get PWM fan control working on a Supermicro C7Q67. This board has a Nuvoton NCT6776F, which is detected when running sensors_detect. However after "modprobe nct6775" the output of "sensors" only shows coretemp. Logfile attached - would be grateful for any support or suggestions. sensors_detect.txt
  24. Parity drive is only needed to recreate data from the missing drive. Perhaps everything that you are doing only needs data from the drives which are present. This is not like RAID5 where the data is striped across all disks, in which case all disks are spun up whenever accessing any data.
  25. I have an issue with tvheadend randomly stopping. Here is what seems to be the relevant log entry: Sep 15 04:32:49 TOWER kernel: Out of memory: Kill process 31524 (tvheadend) score 776 or sacrifice child Sep 15 04:32:49 TOWER kernel: Killed process 31524 (tvheadend) total-vm:14558828kB, anon-rss:13054820kB, file-rss:5664kB Sep 15 04:32:49 TOWER kernel: mc invoked oom-killer: gfp_mask=0x201da, order=0, oom_score_adj=0 Sep 15 04:32:49 TOWER kernel: mc cpuset=/ mems_allowed=0 Sep 15 04:32:49 TOWER kernel: CPU: 5 PID: 6006 Comm: mc Tainted: P W O 4.1.15-unRAID #1 Sep 15 04:32:49 TOWER kernel: Hardware name: To Be Filled By O.E.M. To Be Filled By O.E.M./B75M-ITX, BIOS P1.90 07/17/2013 Sep 15 04:32:49 TOWER kernel: 0000000000000000 ffff880110bb79e8 ffffffff815f8950 0000000000007c48 Sep 15 04:32:49 TOWER kernel: ffff8803d9508000 ffff880110bb7a98 ffffffff815f4ecc ffff880110bb7a48 Sep 15 04:32:49 TOWER kernel: ffffffff810f6ce9 ffff880014007000 01ff880110bb7a08 ffff880110bb7a48 Sep 15 04:32:49 TOWER kernel: Call Trace: Sep 15 04:32:49 TOWER kernel: [<ffffffff815f8950>] dump_stack+0x4c/0x6e Sep 15 04:32:49 TOWER kernel: [<ffffffff815f4ecc>] dump_header+0x7a/0x20b Sep 15 04:32:49 TOWER kernel: [<ffffffff810f6ce9>] ? mem_cgroup_iter+0x2fd/0x3fb Sep 15 04:32:49 TOWER kernel: [<ffffffff810fac63>] ? vmpressure+0x1c/0x6f Sep 15 04:32:49 TOWER kernel: [<ffffffff81355273>] ? ___ratelimit+0xcf/0xe0 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b3c52>] oom_kill_process+0xb7/0x37b Sep 15 04:32:49 TOWER kernel: [<ffffffff810b3957>] ? oom_badness+0xb6/0x100 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b43a7>] __out_of_memory+0x441/0x463 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b4508>] out_of_memory+0x4f/0x66 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b850c>] __alloc_pages_nodemask+0x722/0x7b6 Sep 15 04:32:49 TOWER kernel: [<ffffffff810e4a14>] alloc_pages_current+0xb4/0xd5 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b1a5e>] __page_cache_alloc+0x88/0x95 Sep 15 04:32:49 TOWER kernel: [<ffffffff810b25d5>] generic_file_read_iter+0x32e/0x551 Sep 15 04:32:49 TOWER kernel: [<ffffffff810fd847>] __vfs_read+0x89/0xad Sep 15 04:32:49 TOWER kernel: [<ffffffff810fdd33>] vfs_read+0x84/0x11d Sep 15 04:32:49 TOWER kernel: [<ffffffff810fe543>] SyS_read+0x42/0x86 Sep 15 04:32:49 TOWER kernel: [<ffffffff815fe06e>] system_call_fastpath+0x12/0x71 Sep 15 04:32:49 TOWER kernel: Mem-Info: Sep 15 04:32:49 TOWER kernel: active_anon:3730744 inactive_anon:108262 isolated_anon:0 Sep 15 04:32:49 TOWER kernel: active_file:9983 inactive_file:10619 isolated_file:290 Sep 15 04:32:49 TOWER kernel: unevictable:0 dirty:4528 writeback:831 unstable:0 Sep 15 04:32:49 TOWER kernel: slab_reclaimable:96842 slab_unreclaimable:29449 Sep 15 04:32:49 TOWER kernel: mapped:26683 shmem:205360 pagetables:12848 bounce:0 Sep 15 04:32:49 TOWER kernel: free:20239 free_pcp:0 free_cma:0 Sep 15 04:32:49 TOWER kernel: Node 0 DMA free:15104kB min:12kB low:12kB high:16kB active_anon:64kB inactive_anon:176kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB present:15984kB managed:15360kB mlocked:0kB dirty:0kB writeback:0kB mapped:64kB shmem:240kB slab_reclaimable:16kB slab_unreclaimable:0kB kernel_stack:0kB pagetables:0kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? yes Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 3423 15939 15939 Sep 15 04:32:49 TOWER kernel: Node 0 DMA32 free:53496kB min:3444kB low:4304kB high:5164kB active_anon:3051428kB inactive_anon:102404kB active_file:10344kB inactive_file:11520kB unevictable:0kB isolated(anon):0kB isolated(file):200kB present:3581300kB managed:3506316kB mlocked:0kB dirty:5788kB writeback:680kB mapped:22072kB shmem:182956kB slab_reclaimable:175688kB slab_unreclaimable:28640kB kernel_stack:4208kB pagetables:11936kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:144228 all_unreclaimable? yes Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 0 12516 12516 Sep 15 04:32:49 TOWER kernel: Node 0 Normal free:12356kB min:12600kB low:15748kB high:18900kB active_anon:11871484kB inactive_anon:330468kB active_file:29696kB inactive_file:30816kB unevictable:0kB isolated(anon):0kB isolated(file):832kB present:13080576kB managed:12816552kB mlocked:0kB dirty:12324kB writeback:2644kB mapped:84596kB shmem:638244kB slab_reclaimable:211664kB slab_unreclaimable:89156kB kernel_stack:8048kB pagetables:39456kB unstable:0kB bounce:0kB free_pcp:0kB local_pcp:0kB free_cma:0kB writeback_tmp:0kB pages_scanned:433692 all_unreclaimable? yes Sep 15 04:32:49 TOWER kernel: lowmem_reserve[]: 0 0 0 0 Sep 15 04:32:49 TOWER kernel: Node 0 DMA: 0*4kB 0*8kB 2*16kB (EM) 1*32kB (E) 1*64kB (E) 1*128kB (E) 2*256kB (EM) 2*512kB (EM) 3*1024kB (UEM) 3*2048kB (UEM) 1*4096kB (R) = 15104kB Sep 15 04:32:49 TOWER kernel: Node 0 DMA32: 2868*4kB (UER) 3174*8kB (UEMR) 1000*16kB (UEMR) 5*32kB (R) 2*64kB (R) 3*128kB (R) 1*256kB (R) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 53792kB Sep 15 04:32:49 TOWER kernel: Node 0 Normal: 2815*4kB (UEM) 58*8kB (EM) 32*16kB (R) 8*32kB (R) 2*64kB (R) 3*128kB (R) 2*256kB (R) 0*512kB 0*1024kB 0*2048kB 0*4096kB = 13516kB Sep 15 04:32:49 TOWER kernel: 226405 total pagecache pages Sep 15 04:32:49 TOWER kernel: 0 pages in swap cache Sep 15 04:32:49 TOWER kernel: Swap cache stats: add 0, delete 0, find 0/0 Sep 15 04:32:49 TOWER kernel: Free swap = 0kB Sep 15 04:32:49 TOWER kernel: Total swap = 0kB Sep 15 04:32:49 TOWER kernel: 4169465 pages RAM Sep 15 04:32:49 TOWER kernel: 0 pages HighMem/MovableOnly Sep 15 04:32:49 TOWER kernel: 84908 pages reserved Sep 15 04:32:49 TOWER kernel: [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name Sep 15 04:32:49 TOWER kernel: [ 1045] 0 1045 5395 598 15 3 0 -1000 udevd Sep 15 04:32:49 TOWER kernel: [ 1299] 0 1299 58398 850 25 3 0 0 rsyslogd Sep 15 04:32:49 TOWER kernel: [ 1572] 0 1572 1671 452 8 3 0 0 dhcpcd Sep 15 04:32:49 TOWER kernel: [ 1582] 1 1582 1714 369 9 3 0 0 rpc.portmap Sep 15 04:32:49 TOWER kernel: [ 1586] 32 1586 3209 448 11 3 0 0 rpc.statd Sep 15 04:32:49 TOWER kernel: [ 1596] 0 1596 1615 435 8 3 0 0 inetd <snip> Sep 15 04:32:49 TOWER kernel: [31386] 0 31386 11038 165 25 4 0 0 ssh Sep 15 04:32:49 TOWER kernel: [31395] 0 31395 11038 166 25 3 0 0 ssh Sep 15 04:32:49 TOWER kernel: [32019] 999 32019 243894 25320 123 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [ 3295] 999 3295 297309 20457 123 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [ 3410] 999 3410 242943 20734 117 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [ 4908] 999 4908 261243 19817 117 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [32178] 999 32178 397437 18226 126 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [32181] 999 32181 315003 16144 115 4 0 0 Plex Script Hos Sep 15 04:32:49 TOWER kernel: [ 8082] 0 8082 1091 189 7 3 0 0 sleep Sep 15 04:32:49 TOWER kernel: [ 8129] 0 8129 2159 216 9 3 0 0 timeout Sep 15 04:32:49 TOWER kernel: [ 8130] 0 8130 2974 260 10 3 0 0 find Sep 15 04:32:49 TOWER kernel: [ 8149] 0 8149 1091 158 7 3 0 0 sleep Sep 15 04:32:49 TOWER kernel: Out of memory: Kill process 31526 (linuxdvb_fronte) score 776 or sacrifice child Sep 15 04:32:49 TOWER kernel: Killed process 31572 (mpegts_input_th) total-vm:14558828kB, anon-rss:13055084kB, file-rss:6388kB There is 16gb RAM in the server so with no VMs running so I wouldn't have expected to be out of memory...