Everything posted by macmanluke
-
[SUPPORT] blakeblackshear - Frigate
Plugged into the back of the server with the little extension it came with Likely USB3.0 as i dont think i even have any 2.0 ports
-
[SUPPORT] blakeblackshear - Frigate
Having an issue with my docker crashing about once a week, looked at the log today but it does not seem to be anything helpful Any suggestions? [2023-03-06 23:12:50] frigate.watchdog INFO : Detection appears to be stuck. Restarting detection process... [2023-03-06 23:12:50] root INFO : Waiting for detection process to exit gracefully... [2023-03-06 23:13:20] root INFO : Detection process didnt exit. Force killing... [2023-03-06 23:13:20] detector.coral INFO : Starting detection process: 8443 [2023-03-06 23:13:20] frigate.edgetpu INFO : Attempting to load TPU as usb Process detector:coral: [2023-03-06 23:13:45] frigate.edgetpu ERROR : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors. Traceback (most recent call last): File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 160, in load_delegate delegate = Delegate(library, options) File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 119, in __init__ raise ValueError(capture.message) ValueError During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/lib/python3.9/multiprocessing/process.py", line 315, in _bootstrap self.run() File "/usr/lib/python3.9/multiprocessing/process.py", line 108, in run self._target(*self._args, **self._kwargs) File "/opt/frigate/frigate/edgetpu.py", line 135, in run_detector object_detector = LocalObjectDetector( File "/opt/frigate/frigate/edgetpu.py", line 43, in __init__ edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config) File "/usr/lib/python3/dist-packages/tflite_runtime/interpreter.py", line 162, in load_delegate raise ValueError('Failed to load delegate from {}\n{}'.format( ValueError: Failed to load delegate from libedgetpu.so.1.0 [2023-03-06 23:13:50] frigate.watchdog INFO : Detection appears to have stopped. Exiting frigate...
-
File Activity Plugin - How can I figure out what keeps spinning up my disks?
ok ill give it a go Seems bit strange as it used to work with stock settings
-
File Activity Plugin - How can I figure out what keeps spinning up my disks?
Here you go https://drive.google.com/file/d/1-xh8h0Kc5AbTuR9YMivtFogaEWS3RiTb/view?usp=sharing
-
File Activity Plugin - How can I figure out what keeps spinning up my disks?
Actually had a bit of a look at it last night and i noticed in the syslog im getting: Sep 15 18:45:05 Vault file.activity: Starting File Activity Sep 15 18:45:05 Vault file.activity: File Activity inotify starting Sep 15 18:45:16 Vault inotifywait[29573]: Failed to watch /mnt/disk3; upper limit on inotify watches reached! Sep 15 18:45:16 Vault inotifywait[29573]: Please increase the amount of inotify watches allowed per user via `/proc/sys/fs/inotify/max_user_watches'. Sep 15 18:45:17 Vault file.activity: File Activity inotify exiting After a bit of searching i ended up increasing the inotify watches, gradually each time it would take longer to exit but eventually when i upped it to just over 4mil i started to get: Sep 13 20:46:47 Vault file.activity: Starting File Activity Sep 13 20:46:47 Vault file.activity: File Activity inotify starting Sep 15 20:49:18 Vault inotifywait[23057]: Couldn't watch /mnt/disk3: No such file or directory Sep 15 20:49:20 Vault file.activity: File Activity inotify exiting After that ran out of time to keep looking into it but /mnt/disk3 is there and is healthy so not sure why id get that error edit: Playing with it tonight again i turned off include cache/pools and how getting Sep 16 18:46:00 Vault inotifywait[28045]: Failed to watch /mnt/disk4; upper limit on inotify watches reached! Seems like just increasing the watches is masking another problem?
-
File Activity Plugin - How can I figure out what keeps spinning up my disks?
Does this still work? iv not had it show any activity on my server in a long while Any suggestions? 6.10.3 but started on 6.9
-
6.10.3: macOS SMB slow and not working with folders contaning hundreds of files/folders
Thanks just upgraded from 6.9.x to 6.10.3 and was having horrible time with SMB shares on mac (slow, crashing etc) This seems to have solved it - seems like something that should be configured out of the box? edit: actually its better (eg working) but still seems slower than it should be especially for a batch of small files
-
No display output after boot
guess you have no solution either? tried everything i can think of and no luck but its definitely working as i can use gvt-g and plex transcoding fine, just no output
-
No display output after boot
Ill give DP a go, been trying HDMI - Previous board i was using VGA haha
-
No display output after boot
Nah no video signal at all once booted 6.9.2 and yea i915 is blacklisted only wanting command line too, not trying to get a GUI loaded. Just strange haha
-
No display output after boot
rebooted, still no output and still reporting as 9th gen with intel_top_gpu
-
No display output after boot
Got that installed, no change but not rebooted yet but i noticed its reporting "intel-gpu-top: Intel Cometlake (Gen9) @ /dev/dri/card0" Does 10th gen report as 9th gen? or is something broken having come from 9th gen?
-
No display output after boot
how would i do that? edit: never mind the plugin intel top, ill give it a go
-
No display output after boot
Hello all Just upgraded my Unraid server from a B365M board + 9400 to z590 + 10400 (needed more expansion and made sense to update platform at the same time) All changed over pretty smoothly but iv got an issue when i boot i get display output right through the boot process to the point it would normally drop you at the login terminal but instead display just switches off. Using the iGPU, had i915 blacklisted but removed that with no change Not a big deal just seems strange and cant think of what might be causing it. any suggestions? thanks
-
Unraid server crashing/rebooting
thanks set that up a few days ago works great (local syslog server) "unfortunately" no crashes since and i had sometime yesterday so swapped the PSU over to another unit i had so hopefully that was it and no more crashes
-
Unraid server crashing/rebooting
Hello All About 2 weeks ago my unraid server crashed/rebooted on its own - first issue iv had in around 2 years normally super stable. Triggered a parity check but all good otherwise It did it 2 days later again That was just before i was due to go on holidays so i just left it running but with slightly reduced load (VM with a 3060 that mines eth while idle etc turned off) Seemed good went a bit over a week with no issue but yesterday it happened again Im not super familiar with unraid to know where to look for logs etc for clues - everything iv managed to find seems to be post reboot - is there any logs that persist over a reboot? Im partially considering that it might be power supply related so considering swapping that with a spare i have but i dont like just replacing stuff if i can help it. Server is an Intel i5 9400, 32GB ram, 5x HDDs, dual 1TB NVMe cache, 3060 GPU passed to a VM and sitting on a UPS thanks Luke
-
[Support] Machinaris - Chia cryptocurrency farming + Plotman plotting + Unraid WebUI
haha just thought of that and came to post - i bet thats it will see how i go
-
[Support] Machinaris - Chia cryptocurrency farming + Plotman plotting + Unraid WebUI
Does not seem to say anything useful, they just end without finishing Had 3 finish yesterday but it failed again last night (looks like right at the start of one last night) Interestingly both nights looks like it stopped just after 3am when i come back in the morning the web browser window has also disconnected and needs a refresh
-
[Support] Machinaris - Chia cryptocurrency farming + Plotman plotting + Unraid WebUI
nah there was plenty of space basically empty 1TB SSD (and when it had failed it still had 550+GB free)
-
[Support] Machinaris - Chia cryptocurrency farming + Plotman plotting + Unraid WebUI
So i set this up last night Started it plotting and was at around 170gb for 2 plots. This morning it had stopped plotting and no sign of the plots. Drive still has a bunch of plot files on it (still on the ssd) how can i find out what went wrong? guess i have to manually remove the files and cant resume? edit: Ran a single plot today and it seemed to complete ok, was also after sync had completed not sure if that made a difference. will just keep them running one at a time i guess for now
-
[Support] lnxd - PhoenixMiner
Yea might be worth a play Believe it would be bound to VFIO (box checked in the VM?) Its a Nvidia 3060 and hashing pretty much same as it was in a dedicated box (48mh) Currently use quicksync for plex but the nvidia would be slightly better id guess Also no monitor connected, just a HDMI dummy Funny enough i searched for a docker before setting up the VM and came up with nothing so went the VM route
-
[Support] lnxd - PhoenixMiner
hmm wonder if i should switch over to this from a windows VM. Windows is working flawless and resource usage is no issue but maybe save a few watts of power....
-
[Support] [Depreciated] FlippinTurt PiHole DoT-DoH
how do you install over previous pihole instance (safely)? Will it keep configs?
-
[Support] Josh.5 Docker Templates
Just set this up and have a strange issue If i use lancache im getting sub 2MB/s downloads in battle.net launcher but if i bypass it i get my usual 15-20MB/s Any suggestions? quick test in steam does not seem to have the same issues thanks! edit: looks like its recommended to change the slice size for blizzard - where is the config files for this docker?
-
[support] digiblur's Docker Template Repository
anyone having issues with the log file growing for this docker?