Hellomynameisleo

Members
  • Posts

    86
  • Joined

  • Last visited

Everything posted by Hellomynameisleo

  1. Thanks I given it a try and extracted the storcli64 from \Linux-PPC\LittleEndian\ to the tmp folder and did the "chmod 777 storcli64", then "./storcli64 /c0 show temperature" but get an error saying "bash: ./storcli64: cannot execute binary file: Exec format error" any ideas?
  2. In unraid how do I get the temperature sensor data for the HBA 9300-16I? It has 2 SAS3008 controllers in it and when I touch the heatsink is it really hot even though I only got 2 HDD connected
  3. updated to latest version of unraid and nvidia drivers, still doesn't trigger events even though I can see it working on the GPU load for the detector. Might be a frigate bug in this version. edit: Got it working now, had to add input_tensor and input_pixel_format model: path: /config/model_cache/tensorrt/yolov7x-640.trt input_tensor: nchw input_pixel_format: rgb width: 640 height: 640
  4. thinking its my unraid gpu driver version v530.41.03, that I need to update, but can't because I need to update my unraid which is still on 6.12.0-rc3. Feel like unraid will brick itself and the docker containers if I update the OS
  5. okay got my gpu working in frigate but for some reason the event detection is not working with the tensorrt, I see no events being triggered any ideas why? My config below mqtt: enabled: False detectors: tensorrt: type: tensorrt device: 0 model: path: /config/model_cache/tensorrt/yolov7x-640.trt width: 640 height: 640 go2rtc: streams: bedroom: - http://192.168.4.183/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password={FRIGATE_RTSP_PASSWORD} cameras: bedroom: enabled: True ffmpeg: inputs: - path: http://192.168.4.183/flv?port=1935&app=bcs&stream=channel0_main.bcs&user=admin&password={FRIGATE_RTSP_PASSWORD} input_args: preset-http-reolink roles: - record - path: http://192.168.4.183/flv?port=1935&app=bcs&stream=channel0_sub.bcs&user=admin&password={FRIGATE_RTSP_PASSWORD} input_args: preset-http-reolink roles: - detect detect: enabled: True width: 640 height: 480 fps: 7 record: enabled: True retain: days: 10 mode: all events: retain: mode: motion default: 20 birdseye: enabled: True mode: continuous restream: False width: 640 height: 480 quality: 12 ffmpeg: hwaccel_args: preset-nvidia-h264 output_args: record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -g 300 -c:v hevc_nvenc -preset p7 -tune hq -level 6.2 -tier high -c:a copy and the logs doesn't show any errors: 2024-02-10 13:41:15.567309349 [INFO] Preparing Frigate... 2024-02-10 13:41:15.579936723 [INFO] Starting Frigate... 2024-02-10 13:41:17.224436812 [2024-02-10 13:41:17] frigate.app INFO : Starting Frigate (0.13.1-34fb1c2) 2024-02-10 13:41:18.796348475 [2024-02-10 13:41:18] peewee_migrate.logs INFO : Starting migrations 2024-02-10 13:41:18.805579722 [2024-02-10 13:41:18] peewee_migrate.logs INFO : There is nothing to migrate 2024-02-10 13:41:18.813163234 [2024-02-10 13:41:18] frigate.app INFO : Recording process started: 742 2024-02-10 13:41:18.816235491 [2024-02-10 13:41:18] frigate.app INFO : go2rtc process pid: 99 2024-02-10 13:41:18.841004447 [2024-02-10 13:41:18] frigate.app INFO : Output process started: 753 2024-02-10 13:41:18.862050587 [2024-02-10 13:41:18] detector.tensorrt INFO : Starting detection process: 751 2024-02-10 13:41:18.941615303 [2024-02-10 13:41:18] frigate.app INFO : Camera processor started for bedroom: 766 2024-02-10 13:41:18.943448568 [2024-02-10 13:41:18] frigate.app INFO : Capture process started for bedroom: 768 2024-02-10 13:41:20.430493881 [2024-02-10 13:41:20] frigate.detectors.plugins.tensorrt INFO : Loaded engine size: 317 MiB 2024-02-10 13:41:24.024620445 [2024-02-10 13:41:24] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +772, GPU +192, now: CPU 1731, GPU 1287 (MiB) 2024-02-10 13:41:24.407048625 [2024-02-10 13:41:24] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] Init cuDNN: CPU +235, GPU +52, now: CPU 1966, GPU 1339 (MiB) 2024-02-10 13:41:24.409465278 [2024-02-10 13:41:24] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] TensorRT-managed allocation in engine deserialization: CPU +0, GPU +320, now: CPU 0, GPU 320 (MiB) 2024-02-10 13:41:24.422489353 [2024-02-10 13:41:24] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] Init cuBLAS/cuBLASLt: CPU +0, GPU +8, now: CPU 1649, GPU 1335 (MiB) 2024-02-10 13:41:24.422599790 [2024-02-10 13:41:24] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] Init cuDNN: CPU +0, GPU +8, now: CPU 1649, GPU 1343 (MiB) 2024-02-10 13:41:24.426641410 [2024-02-10 13:41:24] frigate.detectors.plugins.tensorrt INFO : [MemUsageChange] TensorRT-managed allocation in IExecutionContext creation: CPU +0, GPU +222, now: CPU 0, GPU 542 (MiB) 2024-02-10 13:41:24.426747591 [2024-02-10 13:41:24] frigate.detectors.plugins.tensorrt WARNING : CUDA lazy loading is not enabled. Enabling it can significantly reduce device memory usage. See `CUDA_MODULE_LOADING` in https://docs.nvidia.com/cuda/cuda-c-programming-guide/index.html#env-vars
  6. No its not being used for anything, my GPU settings was working before the frigate docker update so not sure why its not working now
  7. any idea why my frigate container won't start? I'm trying to add my RTX 2060 GPU with the drivers already installed, and --runtime=nvidia set in extra paramaters with gpu id set too, I get the error docker: Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #1: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: initialization error: open failed: /proc/sys/kernel/overflowuid: permission denied: unknown.
  8. So I have my wireguard set up as NAT = yes, host access to custom network = no, so I can't use my vpn peer client to access any docker containers on custom network br0. I need to set host access to custom network to yes but then the wireguard peer won't have access to LAN devices without static routes set on router. My router doesn't have the setting for it, what are my options to make this work? would hosting wireguard on another LAN device instead work?
  9. I have seen many reverse proxy guides, but it seems they all cover for remoting into your docker containers exposed to the internet then securing them with reverse proxy authentication. This seems insecure since if someone got access to your LAN they can bypass your reverse proxy authentication and directly access the docker containers using their IP:port as your docker containers are exposed to the host's LAN network. Is there guides for when you already have home VPN access to your LAN remotely using unraid's own wireguard, and then securing your docker containers behind a reverse proxy authentication? But having your docker containers not exposed to your LAN network, only an internal docker network. This would be suitable for when you are sharing internet connection with other untrust users on the LAN.
  10. any idea why I am getting this error when trying to query the log dates? I have setup a new pihole, just modified the http and https ports to 6000
  11. I have a 10GBe network card that is ETH1 (192.168.11.1) and have enabled bridging as BR1, and have ticked the checkbox in the docker settings for BR1 to be enabled but it is not shown as an option for docker containers. The 10GBe network card is directly attached to my windows pc (192.168.11.2) using a DAC which also has the same network card. Any ideas what I could be doing wrong? I accidentially changed something and now its no longer showing up as an option but it was before I changed a setting. network settings docker settings container settings
  12. Yes its mapped to frigate, I've stopped the frigate container and started the Tensorrt-models docker and it the same error that pops up. Is there something else I am missing?
  13. I am trying to get started with the Tensorrt-models docker container and have set it up as below with the script, have did the "chmod +x /mnt/user/appdata/trt-models/tensorrt_models.sh" and when running the container I get the error below: /opt/nvidia/nvidia_entrypoint.sh: /tensorrt_models.sh: /bin/bash^M: bad interpreter: No such file or directory /opt/nvidia/nvidia_entrypoint.sh: line 49: /tensorrt_models.sh: Success any ideas what I am doing wrong?
  14. unraid uses fuse for user shares on the array and its very slow espcially at listing directories in windows with 1000s of small files. Would it be a good or bad idea to instead smb all my unraid disk shares to my Windows pc which bypasses fuse then use rclone's union on my windows pc to merge all the mapped disk shares? It will be like doing what fuse does but instead on the windows computer for improved performance gains. Any thoughts on doing this?
  15. I have ran the command "ip address add 192.168.4.110/24 dev br0" as my cctv camera ip is 192.168.4.183 so I have made it so my unraid can communicate on the same subnet as the cctv camera. How do I run my docker container on 192.168.4.110/24 so I can use it to communicate with the cctv camera as well? I have setup a layer 2 LAN on my managed switch and set both the cctv camera and unraid ports to PVID 4
  16. I have my unraid server on a local network where there are many other people using it as well and it seems anyone connected to my internet can access my docker containers like frigate and Krusader containing my personal stuff. How do I setup so all my docker containers will request for a password like unraids webui does or outright block any local ip address except the whitelisted ones? I don't remote connection to unraid so won't want to use a reverse proxy
  17. Would it be possible to have the parity drive instead store the series of 1 and 0 data inside a text file instead of pysically on the blocks of the hard disks which would allow for massively reduced size and no longer need the requirement of having the parity drive as large as the biggest drive in the array? It would function the same but instead read the series of 1 and 0s from a text file instead of the sector blocks on the hard drive.
  18. I am trying to mount a NFS share from my TrueNAS computer, but it shows the mount point directory empty. How do I put in the credentials for the mount point?
  19. I have used it but find it less ease of use for drag drop moving and browsing which krusader does better similar to a windows file explorer experience, though I am using it a temperary measure. Would it be possible to instead present my whole UNRAID array using iSCSI instead of SMB to my windows pc or does it only work on single disks?
  20. I wanted the array without dedicating storage to a pool, I went for unraid because I didn't need to go for a pool and have good amount of usable storage unlike something like trueNAS. The array is starting to become unusable as I add more stuff and becoming hard to move 1000s of files in the array around since it takes so long. though I've gone to use krusader on unraid instead to do any file/folder modifications instead of using my windows pc over smb and its really that much faster.
  21. Trying to to run UNRAID to work in windows hyper-v VM for testing/playing with configs etc. I have gotten as far as booting but it gets stuck on detecing the label UNRAID. I've tried creating a VHDX file in windows volume labeled UNRAID with EFI and MBR, the VM is Gen 2 to enable EFI support. I did the manual install steps by copying and pasting the zip file contents to the created VHDX then windows.bat as admin, efi- folder renamed to efi. Booted off the VHDX in the VM but now I am stuck with the below picture. Is there something I am missing or anyone know how to get this working if possible?
  22. is disk shares really the only way for this issue? its going to be even harder and pain to manage 5 seperate disks and its one of the many reason I came to use unraid so I wouldn't need to do that.
  23. Is this only a setting you can set if you have a cache pool? I only have an existing array with no set cache
  24. I have been using UNRAID and TrueNAS both on diffrent machines and through SMB. I find for UNRAID is so much slower access time when opening directories/files it takes much longer to list files compared to my trueNAS computer. Any ideas if this is normal behaviour with UNRAID's performance? In general this is most noticeable on directories with 1000+ files in them, trueNAS handles it very well while unraid is just sluggish in comparision.
  25. It just started happening recently and was working as usual on the version I am using until it started crashing. I have the syslog already enabled with the logs below: