TDA

Members
  • Posts

    181
  • Joined

  • Last visited

Recent Profile Visitors

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

TDA's Achievements

Explorer

Explorer (4/14)

7

Reputation

  1. Also noticed that in the syslog: shfs: share cache full But the cache itself has 93Gb free
  2. Hello, I've upgraded Unraid to 6.12.8 since a couple of days, and today all of sudden I saw that I can't the dockers container I used to have. I checked and it seems that the error is: can't create directory '/config/xdg/data/themes/OpenboxTheme': No space left on device I have no clue, what / where the problem could be. I could rollback, but before that - I would like to try to fix the problem. Also the cache was under 10% (and two days ago was almost empty) - so I don't know what's happening. Any help would be appreciated. sekiro-diagnostics-20240301-1952.zip
  3. Ok, fair enough. But then to troubleshoot if the problem is the PSU, I should switch cable with another disk right? Since all other disk don't have problems
  4. Yeah I know, but the power from the PSU is enough - and if it has problems, it should affect the server too (theoretically)
  5. Hello, I will order a new set of cables just to make sure it's not a faulty cable as you suggest (it will need a couple of days I think from Amazon, cause I need mini sas to 8088) I've now removed the disk to the array and readded it - and it's now building the parity again. Thanks again for the tip.
  6. Hello Everyone, I'm having a little trouble with my Parity disk. The disk is almost new (it has a couple of months), but today I saw that it has error on it and that the parity is not guaranteed anymore. Before I pull out the disk and send it back in guarantee - could someone help me to understand if it's really a physical defect? The SMART tells me all is ok... Disk is a Toshiba: TOSHIBA_MG10ACA20TE_Z2E0A0NSF4MJ Also I have enabled automatic Spin down. Could this lead to problems if the parity is spun down automatically? Thank you in advance. sekiro-diagnostics-20240205-1510.zip
  7. Here it is. sekiro-smart-20231219-1818.zip
  8. Hello Everyone, I've a strange behavior on my Unraid. The parity disk shows errors (1025) But I've run the SMART & Extended SMART Tests and it shows no errors at all. Now I saw that the parity disk was sometimes SPUN DOWN - should this happen? How I clear the errors to see if more are produced? Thanks in advice
  9. Hello, thanks for the hint. I'm using the docker you suggest, and now I'm seeing data. Only problem I have the SMART is empty - and I don't know what/how I have to configure it. EDIT: Also, it's possible to monitor Nvidia GPU?
  10. Hello, Thank you for the answer 🙂 I will search for a guide on how to configure go2rtc and try to configure it this way.
  11. My bad, I was sure I had added it, but it was missing. Added now but same error. It blanked out in the printscreen, but it's inside. Is my config.yml correct? Particularly the camera config: preset-nvidia-h264 ? And the detectors are configured correctly? Do I have to set something particular inside neolink? Thanks to all in advance 🙂 EDIT: I outcommented: hwaccel_args: preset-nvidia-h264 And now it's "kind" of working. Not stable at the moment, and the playback of videos don't work. It's better to use GO2RTC in between? neolink --> go2rtc --> frigate with such cameras?
  12. Hello Everyone, Sorry I'm totally newbie with Frigate & NVR so probably my question/problem is really simple. I have Reolink Argus3 Cameras, and I'm tring to configure it with Frigate. I've installed Neolink, which is working without problems. Then I've installed Frigate and tested it with CPU as detector, and is working. Since I have a NVIDIA P4 on my Unraid server, I tried to configure it with NVidia, but I'm failing 🙂 The Frigate Docker is configured as following: And the tensorrt was configured : I modified the config.yml as following: mqtt: enabled: false cameras: Camera: ffmpeg: inputs: - path: rtsp://xxx.xxx.xxx.xxx:8554/xyz/main hwaccel_args: preset-nvidia-h264 roles: - detect - record objects: track: - person - dog - bicycle - car - motorcycle detect: width: 2560 height: 1440 record: enabled: True retain: days: 7 mode: all detectors: tensorrt: type: tensorrt device: 0 #This is the default, select the first GPU model: path: /trt-models/yolov7-tiny-416.trt input_tensor: nchw input_pixel_format: rgb width: 416 height: 416 I don't know what I'm missing here, since with this configuration, no imput is shown in Frigate.
  13. Does work if I have encrypted XFS drives? I wanted to start a fresh installation to configure it as new, since I'm rebuilding the whole network hierarchy. Thanks
  14. Hello, I've just upgraded to Version: 6.12.3. Unfortunately after reboot, the plugin can't see my card anymore (worked just fine before upgrading to Version: 6.12.3). I've tried to download the driver again and to reboot the server and now it's fine. Don't know what break did the Upgrade (lately it seems like Unraid Updates are like Windows Updates... you have to wait or to skip... but for the sake of security...you know...)
  15. I'm still having issue also with 6.12.2. After dockers are updated they aren't able to start anymore. I have to reboot the whole server. Since the popup with the error don't help a lot, is there somewhere I could check logs etc to try to identify the Problem? Also, instead of rebooting the server, I disabled and re enabled Docker. After this, I got another error: I had to restart the whole server again to get it running agian. sekiro-diagnostics-20230704-1722.zip