gareth_iowc

I like to sleep my array to save energy and extend disk life but I run into an issue when connecting to the network share from my Mac. The Mac and network share experience is shocking and sometimes it hard to tell if there’s an issue or I’m just waiting for the disks to spin up. Is there a command I can call to wake all disks in the array? I’m hoping it’s something I can build on and call remotely from my Mac when the user logs in

I'm after some help with diagnosing my system crashes that have been happening for the last 6 months. It could crash once a month, a week, or 3 days in a row like this week. It could crash in the middle of the night while I'm sleeping or while I'm watching something on Emby. I've taken a look at the logs and the only thing that stands out to me is FFMPEG, and go2rtc-related that my frigate docker container uses Here is part of the log where i think the system crashed lastnight - Oct 17 20:54:58 Shibby-Nas kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=2c568eb912c78d812223dd34b52b55b2b4cbcda1ccf8f929166b80deee2522d1,mems_allowed=0,global_oom,task_memcg=/docker/4127b37ed293a84219ac2f17ff3d9d6149857b597e17c52aa41df9b67e381bf7,task=ffmpeg,pid=8866,uid=0 Oct 17 20:54:58 Shibby-Nas kernel: Out of memory: Killed process 8866 (ffmpeg) total-vm:22441644kB, anon-rss:22063848kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:43376kB oom_score_adj:0 Oct 17 20:55:01 Shibby-Nas kernel: oom_reaper: reaped process 8866 (ffmpeg), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB Oct 17 21:37:23 Shibby-Nas emhttpd: spinning down /dev/sdo Oct 17 21:37:31 Shibby-Nas emhttpd: read SMART /dev/sdo Oct 17 21:37:33 Shibby-Nas emhttpd: spinning down /dev/sdn Oct 17 21:37:41 Shibby-Nas emhttpd: read SMART /dev/sdn Oct 17 22:13:13 Shibby-Nas emhttpd: spinning down /dev/sdb Oct 17 22:37:32 Shibby-Nas emhttpd: spinning down /dev/sdo Oct 17 22:37:41 Shibby-Nas emhttpd: read SMART /dev/sdo Oct 17 22:37:42 Shibby-Nas emhttpd: spinning down /dev/sdn Oct 17 22:37:51 Shibby-Nas emhttpd: read SMART /dev/sdn Oct 17 22:38:40 Shibby-Nas kernel: SPICE Worker invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0 Oct 17 22:38:40 Shibby-Nas kernel: CPU: 0 PID: 14428 Comm: SPICE Worker Tainted: P O 6.1.82-Unraid #1 Oct 17 22:38:40 Shibby-Nas kernel: Hardware name: Dell Inc. PowerEdge T640/0TWW5Y, BIOS 2.20.1 09/14/2023 Oct 17 22:38:40 Shibby-Nas kernel: Call Trace: Oct 17 22:38:40 Shibby-Nas kernel: <TASK> Oct 17 22:38:40 Shibby-Nas kernel: dump_stack_lvl+0x44/0x5c Oct 17 22:38:40 Shibby-Nas kernel: dump_header+0x4a/0x211 Oct 17 22:38:40 Shibby-Nas kernel: oom_kill_process+0x80/0x111 Oct 17 22:38:40 Shibby-Nas kernel: out_of_memory+0x3b3/0x3e5 Oct 17 22:38:40 Shibby-Nas kernel: __alloc_pages_slowpath.constprop.0+0x7cf/0x8de Oct 17 22:38:40 Shibby-Nas kernel: __alloc_pages+0x132/0x1e8 Oct 17 22:38:40 Shibby-Nas kernel: folio_alloc+0x14/0x35 Oct 17 22:38:40 Shibby-Nas kernel: __filemap_get_folio+0x185/0x213 Oct 17 22:38:40 Shibby-Nas kernel: ? preempt_latency_start+0x1e/0x46 Oct 17 22:38:40 Shibby-Nas kernel: filemap_fault+0x317/0x52f Oct 17 22:38:40 Shibby-Nas kernel: __do_fault+0x2a/0x6b Oct 17 22:38:40 Shibby-Nas kernel: __handle_mm_fault+0xa22/0xcf9 Oct 17 22:38:40 Shibby-Nas kernel: ? eventfd_write+0x19e/0x1c7 Oct 17 22:38:40 Shibby-Nas kernel: handle_mm_fault+0x13d/0x20f Oct 17 22:38:40 Shibby-Nas kernel: do_user_addr_fault+0x2c3/0x48d Oct 17 22:38:40 Shibby-Nas kernel: exc_page_fault+0xfb/0x11d Oct 17 22:38:40 Shibby-Nas kernel: asm_exc_page_fault+0x22/0x30 Oct 17 22:38:40 Shibby-Nas kernel: RIP: 0033:0x150ff2a68b30 Oct 17 22:38:40 Shibby-Nas kernel: Code: Unable to access opcode bytes at 0x150ff2a68b06. Oct 17 22:38:40 Shibby-Nas kernel: RSP: 002b:0000150fa2ffdb88 EFLAGS: 00010246 Oct 17 22:38:40 Shibby-Nas kernel: RAX: 0000000000000000 RBX: 0000150fa2866200 RCX: 0000150fabc73540 Oct 17 22:38:40 Shibby-Nas kernel: RDX: 0000000000000000 RSI: 0000000000000010 RDI: 0000150fa2ffdbf0 Oct 17 22:38:40 Shibby-Nas kernel: RBP: 0000150fac67f4a0 R08: 0000000000000000 R09: 0000000000000300 Oct 17 22:38:40 Shibby-Nas kernel: R10: 00007fff99b1c080 R11: 000000002ec48310 R12: 0000150fa2ffdbf0 Oct 17 22:38:40 Shibby-Nas kernel: R13: 0000000000000000 R14: 0000150fabcad038 R15: 0000150fabcad080 Oct 17 22:38:40 Shibby-Nas kernel: </TASK> Oct 17 22:38:40 Shibby-Nas kernel: Mem-Info: Would be great to get some assistance shibby-nas-diagnostics-20241018-2127.zip

Did you run the vm setup script from the user scripts section? If so what was the output

Anyone having what I assume is kernel panic issues? I have other Linux VM’s running without issue but after starting the big sur installer and it's been running for a while the sever crashes as requires a manual reboot. System remains stable until I start this install again

I had an opportunity to move my server into a data centre that benefits me as I'm saving on electricity and the wife doesn't need to listen to the server anymore in the front room. I have a MikroTik CCR1036-8g-2s+ and a CCR1009-8G-1S connected using an EOIP tunnel and encrypted using IPsec. Both ends have a symmetrical 900 Mbps internet connection but due to the IPsec I can only push around 300mbps (full line speed with IPsec disabled) Rather than keep throwing money at routers, I'm thinking of running Mikrotik's cloud-hosted router VM on my unraid server and passing a 10 GB fibre card. I know the main security would come down to my router config inside the VM but would there be any other vulnerabilities? It feels a little scary plugging the internet directly into my server.

I'm not sure if it's part of the visual editor plugin i'm using but can the review process be disabled when edit a page?

Thanks, I have seen this document but I’m a bit confused on how it works. So by creating zones you can set alerts for only the driveway zone but what’s telling the system to ignore the car while parked?

I'm after some help getting frigate to decide when an car/object is stationary and ignore until it moves. The cars highlighted and almost always parked in the same place and i get loads of snap shots and recordings while they are stationary. I want to track the whole picture not just my driveway. My current config - mqtt: host: 10.10.50.8 topic_prefix: frigate client_id: frigate user: admin password: pass cameras: Driveway: ffmpeg: inputs: - path: rtsp://admin://[email protected]:554/Streaming/Channels/101 roles: - detect - rtmp - clips detect: # Optional: width of the frame for the input with the detect role (default: shown below) width: 3840 # Optional: height of the frame for the input with the detect role (default: shown below) height: 2160 # Optional: desired fps for your camera for the input with the detect role (default: shown below) # NOTE: Recommended value of 5. Ideally, try and reduce your FPS on the camera. fps: 5 # Optional: enables detection for the camera (default: True) # This value can be set via MQTT and will be updated in startup based on retained value enabled: True # Optional: Number of frames without a detection before frigate considers an object to be gone. (default: 5x the frame rate) max_disappeared: 25 # Optional: Configuration for stationary object tracking stationary: # Optional: Frequency for confirming stationary objects (default: shown below) # When set to 0, object detection will not confirm stationary objects until movement is detected. # If set to 10, object detection will run to confirm the object still exists on every 10th frame. interval: 0 # Optional: Number of frames without a position change for an object to be considered stationary (default: 10x the frame rate or 10s) threshold: 50 # Optional: Define a maximum number of frames for tracking a stationary object (default: not set, track forever) # This can help with false positives for objects that should only be stationary for a limited amount of time. # It can also be used to disable stationary object tracking. For example, you may want to set a value for person, but leave # car at the default. # WARNING: Setting these values overrides default behavior and disables stationary object tracking. # There are very few situations where you would want it disabled. It is NOT recommended to # copy these values from the example config into your config unless you know they are needed. max_frames: # Optional: Default for all object types (default: not set, track forever) default: 3000 # Optional: Object specific values objects: person: 1000 objects: # Optional: list of objects to track from labelmap.txt (default: shown below) track: - person - car - cat - dog - bird snapshots: # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below) # This value can be set via MQTT and will be updated in startup based on retained value enabled: true # Optional: print a timestamp on the snapshots (default: shown below) timestamp: False # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: False # Optional: crop the snapshot (default: shown below) crop: False # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 10 # Optional: Per object retention days objects: person: 15 record: enabled: True retain: days: 5 mode: all events: retain: default: 5 mode: active_objects detectors: # Required: name of the detector coral: # Required: type of the detector # Valid values are 'edgetpu' (requires device property below) and 'cpu'. type: edgetpu # Optional: device name as defined here: https://coral.ai/docs/edgetpu/multiple-edgetpu/#using-the-tensorflow-lite-python-api device: usb I'm a bit confused on how to add the following config as it stops frigate from loading - Ref- https://docs.frigate.video/configuration/stationary_objects/ detect: stationary: interval: 0 threshold: 50

I'm trying to get the home assustant frigate plugin to work but it's not connecting Log Details (ERROR) This error originated from a custom integration. Logger: custom_components.frigate.api Source: custom_components/frigate/api.py:51 Integration: frigate (documentation, issues) First occurred: 17:24:59 (1 occurrences) Last logged: 17:24:59 Timeout error fetching information from http://10.10.10.14:5000/api/stats: The ip is reachable from home assistant - any ideas?

Thanks that worked I would like to review short videos clips of the events and have added clips: enabled: true retain: defualt: 15 but frigate wont start with that added mqtt: host: 10.10.50.8 cameras: back: ffmpeg: inputs: - path: rtsp://user:[email protected]:554/Streaming/Channels/101 roles: - detect - rtmp - clips objects: # Optional: list of objects to track from labelmap.txt (default: shown below) track: - person - car - cat - dog - bird snapshots: # Optional: Enable writing jpg snapshot to /media/frigate/clips (default: shown below) # This value can be set via MQTT and will be updated in startup based on retained value enabled: true # Optional: print a timestamp on the snapshots (default: shown below) timestamp: False # Optional: draw bounding box on the snapshots (default: shown below) bounding_box: False # Optional: crop the snapshot (default: shown below) crop: False # Optional: Restrict snapshots to objects that entered any of the listed zones (default: no required zones) required_zones: [] # Optional: Camera override for retention settings (default: global values) retain: # Required: Default retention days (default: shown below) default: 10 # Optional: Per object retention days objects: person: 15 clips: enabled: true retain: defualt: 15 # Optional: Detectors configuration. Defaults to a single CPU detector detectors: # Required: name of the detector coral: # Required: type of the detector # Valid values are 'edgetpu' (requires device property below) and 'cpu'. type: edgetpu # Optional: device name as defined here: https://coral.ai/docs/edgetpu/multiple-edgetpu/#using-the-tensorflow-lite-python-api device: usb

How do i get the show options button to enable bounding box etc? mqtt: host: 10.10.50.8 cameras: back: ffmpeg: inputs: - path: rtsp://user:[email protected]:554/Streaming/Channels/101 roles: - detect - rtmp # Optional: Detectors configuration. Defaults to a single CPU detector detectors: # Required: name of the detector coral: # Required: type of the detector # Valid values are 'edgetpu' (requires device property below) and 'cpu'. type: edgetpu # Optional: device name as defined here: https://coral.ai/docs/edgetpu/multiple-edgetpu/#using-the-tensorflow-lite-python-api device: usb

Any suggestions with this error?

bugs attracted to the IR light of my camera trigger the motion recording all the time. can anyone recommend what setting i should be changing?

i have this same error when adding a second gfx card

have the same problem on 6.9.0-beta1