Michael_P

Well whatever it was doing, it ran the host OOM back on the 2nd. FCP will continue to complain about it until you reboot the log is cleared. Since it doesn't look like a re-occurring issue, I'd just reboot and ignore it - and if it happens again, verify the config has the necessary work directories mapped to disk

Do you have jellyfin transcoding to RAM?

The cameras don't connect to the server, the server connects to them - each camera (generally speaking) is like its own video server, the security DVR just connects and downloads its video stream. If you have the cameras IP and port (and it's accessible), the 'DVR' can be anywhere

I don't run it personally, but quite a few users have issues with it running the host OOM

You should start your own thread and add your diagnostics

Looks like back in April it may have been Frigate, along with whatever was spawning all of those Apache processes which killed off whatever VM you were running In may, Apache again spawning a bunch but also appears to be Frigate Again in June, Frigate and a bunch of curl cron jobs? Doesn't appear to be any since June, tho it will keep complaining until you restart and they're no longer in the logs

Anything more than zero.

+1 for kill it with fire

EVGA blew up a couple of their customer's hard drives because they changed the pinout on the SAME MODEL PSU between batches - they only discovered it might be an issue after their customer RMAd a PSU and were told to keep the cables, and received another in return which had the 'newer' pinout. If re-using modular cables, always always always tone out the pins to make sure they match.

This will probably be your issue. 1080p transcodes down to something else, yeah it could probably do it - BMB did 18 smooth 4K transcodes on his 13th gen. And if it's not a 4K HDR file, it's more likely that most if not all will be direct streams not needing transcode at all. Audio will still be CPU bound, but if the clients are all using relatively decent hardware (like the Shield), they'll be direct streams, too. I'd fill it up with RAM, tho

FWIW my Thermaltake 850 did the reboot thing too when it was failing.

+1 for PSU on its way out

Pending sectors are an internal error in the drive and not anything to do with communication. Anything more than zero is a cause for concern.

I will say, don't use the two piece ones (bottom plate and top heatsink), just use the top heatsink and leave the bottom as it is

Doesn't need to be fancy, most anything will do

Random reboots and shutdowns are usually power supply related

What were the temps? Flash memory actually loves heat, but their controllers do not. I could peg tmax on my NVMe in a well ventilated install with little effort, so I always add a heatsink. For a ~4TB low power NAS, I'd just forego parity and rely on backups for uptime, unless you really need uptime and cant afford a few hours downtime.

No, unraid needs a flash drive to boot from as it's also used like a dongle for the key

It was allocated ~12GB when the reaper killed it

There was a bunch of nvidia related errors in the log, too - maybe check with frigate's community to see if it's the issue Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:10 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:11 Home43 kernel: [drm:nv_drm_gem_prime_fence_attach_ioctl [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Padding fields must be zeroed Jun 16 21:54:12 Home43 kernel: x86/PAT: frigate.detecto:4054 map pfn RAM range req uncached-minus for [mem 0x62a3b4000-0x62a3b7fff], got write-back

Check on the containers page, look at the uptime - should be the one(s) with less than a minute uptime

OOMs aren't hardware related, it isn't hard to see what's causing it Jun 16 15:30:58 Home43 kernel: [ 474] 0 474 328006 34440 569344 0 0 frigate.logger Jun 16 15:30:58 Home43 kernel: [ 476] 0 476 553572 46644 995328 0 0 frigate.recordi Jun 16 15:30:58 Home43 kernel: [ 485] 0 485 562259 36658 782336 0 0 frigate.review_ Jun 16 15:30:58 Home43 kernel: [ 507] 0 507 3658 1320 65536 0 0 python3 Jun 16 15:30:58 Home43 kernel: [ 508] 0 508 483514 39732 696320 0 0 frigate.detecto Jun 16 15:30:58 Home43 kernel: [ 510] 0 510 1428766 53321 1404928 0 0 frigate.output Jun 16 15:30:58 Home43 kernel: [ 534] 0 534 31705 1753 155648 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 539] 0 539 31705 1753 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 544] 0 544 31705 1752 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 549] 0 549 31705 2157 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 554] 0 554 31705 1249 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 560] 0 560 31705 1704 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 565] 0 565 31705 1672 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 570] 0 570 31705 1753 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 575] 0 575 31705 1753 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 580] 0 580 31705 1734 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 585] 0 585 31705 1753 167936 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 590] 0 590 31705 1752 163840 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 595] 0 595 46919 16988 315392 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 650] 0 650 629123 75729 1126400 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 654] 0 654 629247 75284 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 664] 0 664 629123 75770 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 674] 0 674 629123 75542 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 683] 0 683 629123 75769 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 691] 0 691 629123 75760 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 699] 0 699 629123 75771 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 707] 0 707 629247 75431 1110016 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 715] 0 715 629247 75410 1110016 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 723] 0 723 629247 75585 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 731] 0 731 629123 75891 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 739] 0 739 629251 76011 1122304 0 0 frigate.process Jun 16 15:30:58 Home43 kernel: [ 745] 0 745 612789 75694 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 748] 0 748 612789 75407 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 751] 0 751 2442947 70314 868352 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 754] 0 754 612789 75626 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 755] 0 755 2442911 70436 864256 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 760] 0 760 612789 75985 1040384 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 761] 0 761 32336 2488 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 762] 0 762 2442927 69623 872448 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 765] 0 765 32991 3603 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 768] 0 768 612789 75653 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 769] 0 769 32317 3406 180224 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 774] 0 774 612789 75632 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 775] 0 775 32339 2887 184320 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 779] 0 779 33047 3988 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 781] 0 781 33042 3370 200704 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 784] 0 784 32811 2929 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 785] 0 785 2442893 69050 856064 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 786] 0 786 612778 75650 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 791] 0 791 32824 2797 184320 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 794] 0 794 612789 75522 1040384 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 795] 0 795 2442932 70520 860160 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 799] 0 799 122241 9344 364544 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 803] 0 803 32748 3441 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 804] 0 804 612789 75369 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 805] 0 805 32979 3766 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 812] 0 812 36614 7777 217088 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 815] 0 815 32341 3390 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 816] 0 816 612789 75666 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 818] 0 818 2442945 70476 864256 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 819] 0 819 33229 4339 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 824] 0 824 33508 4081 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 826] 0 826 612789 75662 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 829] 0 829 37108 7828 221184 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 830] 0 830 2442947 70669 860160 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 834] 0 834 32322 2207 176128 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 835] 0 835 32818 2935 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 841] 0 841 33018 3106 200704 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 842] 0 842 612814 75715 1032192 0 0 frigate.capture Jun 16 15:30:58 Home43 kernel: [ 843] 0 843 2442931 70143 868352 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 848] 0 848 35767 6157 217088 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 849] 0 849 1383268 89979 1748992 0 0 frigate.audio_m Jun 16 15:30:58 Home43 kernel: [ 850] 0 850 2443013 70426 872448 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 851] 0 851 32338 2886 180224 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 859] 0 859 33307 3585 204800 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 860] 0 860 32339 2488 184320 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 861] 0 861 32865 3592 184320 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 870] 0 870 33007 3800 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 874] 0 874 33005 2985 200704 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 877] 0 877 32793 2813 180224 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 879] 0 879 33120 4010 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 885] 0 885 32771 3313 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 887] 0 887 32969 3445 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 897] 0 897 32635 2277 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 906] 0 906 33060 4121 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 916] 0 916 33114 3730 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 932] 0 932 32850 3443 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 933] 0 933 32809 3060 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 942] 0 942 32801 2304 188416 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 955] 0 955 33015 3475 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 964] 0 964 32887 2927 196608 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 23297] 0 23297 2405543 36872 569344 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 23299] 0 23299 32316 2671 192512 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 5484] 0 5484 3624 1892 65536 0 0 python3 Jun 16 15:30:58 Home43 kernel: [ 8979] 0 8979 2405413 65540 827392 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 19516] 0 19516 3247086 879208 7319552 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 19518] 0 19518 32369 2330 180224 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 22768] 0 22768 33053 3515 200704 0 0 ffmpeg Jun 16 15:30:58 Home43 kernel: [ 2587] 0 2587 622 217 40960 0 0 sleep Jun 16 15:30:58 Home43 kernel: [ 3744] 0 3744 622 216 40960 0 0 sleep And it looks like one of your containers is going up and down repeatedly which may be related to any memory limits you've set Jun 17 09:54:52 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered blocking state Jun 17 09:54:52 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered forwarding state Jun 17 09:54:57 Home43 kernel: veth0844f4a: renamed from eth0 Jun 17 09:54:57 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered disabled state Jun 17 09:54:57 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered disabled state Jun 17 09:54:57 Home43 kernel: device veth11b8ae4 left promiscuous mode Jun 17 09:54:57 Home43 kernel: br-191c7978c3a3: port 5(veth11b8ae4) entered disabled state Jun 17 09:55:28 Home43 kernel: device eth0 entered promiscuous mode Jun 17 09:55:39 Home43 kernel: device eth0 left promiscuous mode

Map it in the container settings like you would any other path

Worth testing for a period of time to verify. There's been a few other users of frigate here reporting the same OOM events

Considering it was using ~12GB when it was killed, I'm going to say no