First seeing this on my home feed on Jan 7th. Relieved to find the post is 5 days old…
Clocking in at 37 minutes. Don’t judge prog by the number of tracks… pretty typical album runtime for anything released in the vinyl era.
Also, it’s fantastic.
You mention frigate specifically. Were you running this on the system when the drive failed, or is this a future endeavour?
I bring this up because I also use frigate, and for some time I was running with a misconfigured docker compose that drove my SSD wearout to 40% in a matter of months.
Make sure that the tmpfs is configured per the frigate documentation and example config. If misconfigured like mine was, all of that IO is on disk. I believe the ramdisk is used for temp storage of camera streams, until an event occurs and the corresponding clip is committed to disk.
Good luck!
Pulling around 200W on average.
- 100W for the server. Xeon E3-1231v3 with 8 spinning disks + HBA, couple of sata SSD’s
- ~80W for the unifi PoE 48 Pro switch. Most of this is PoE power for half a dozen cameras, downstream switches and AP’s, and a couple of raspberry pi’s
- ~20W for protectli vault running Opnsense
- Total usage measured via Eaton UPS
- Subsidised during the day with solar power (Enphase)
- Tracked in home assistant
Looks like home assistant
This is what I do as well. I have a public DNS record for my internal reverse proxy IP (no need to expose my public IP and associate it with my domain). I let NPM reach out to the DNS provider to complete verification challenge using an account token, NPM can then get a valid cert from Let’s Encrypt and nothing is exposed. All inbound traffic on 80/443 remains blocked as normal.
Just on point A. You can configure the maximum number of conflicts allowed for each folder.
I was running into conflicts with obsidian notes. Reduced the max conflicts on those folder to zero, problem gone.
It’s in the folder specific advanced settings.