thumdinger

joined 2 years ago
[–] thumdinger 2 points 1 week ago (1 children)

First seeing this on my home feed on Jan 7th. Relieved to find the post is 5 days old…

[–] thumdinger 1 points 1 week ago (1 children)
[–] thumdinger 1 points 1 week ago (3 children)

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.

[–] thumdinger 8 points 1 week ago* (last edited 1 week ago) (1 children)

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!

[–] thumdinger 2 points 2 weeks ago

That’s great. Thank you again!

[–] thumdinger 4 points 2 weeks ago (3 children)

Thank you! Something concrete to go on. Is there a specific name these go by? I couldn’t find them by searching.

I think I have two issues to work through. I’m not sure I applied enough pressure to actuate the spring (access may be a limiting factor in-situ), and I was using an extremely fine gauge of wire. I doubt it would have the stiffness to push in.

Would a stalk lug work to provide added stiffness to the conductor, or does this terminal expect something malleable?

[–] thumdinger 1 points 2 weeks ago (1 children)

That was my initial thought, but there’s little to no give in the orange button. If anything it only felt like a little play you get between loosely coupled mechanical pieces. That’s when I tried operating it like a clamp and broke one off.

[–] thumdinger 2 points 3 weeks ago* (last edited 3 weeks ago)

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
[–] thumdinger 2 points 3 weeks ago

Looks like home assistant

[–] thumdinger 2 points 3 weeks ago* (last edited 3 weeks ago)

For storage redundancy RAID 5 is not recommended, particularly as you get to high capacity drives (think >8TB). I think the rating to consider is URE (unrecoverable read error, usually 1 in 10^14 bits read).

Once a drive inevitably fails and you are forced to resilver the array to avoid data loss. During the resilver the healthy disks are running at 100%, reading every bit of data they have to complete the parity calculation and determine what data is missing. The chances of encountering a URE on another drive is a near certainty at high capacities as the total number of bits read exceeds the URE rating. As result the resilver would fail and the array would be lost.

RAID 6 as a minimum (2 drive redundancy), although a popular option now (and the layout I use) is mirrored vdevs.

Edit: Consider TrueNAS for NAS software. I have been using it for 10 years and it is absolutely rock solid. 25TB usable storage across 4x mirrored vdevs. I run it as a VM inside Proxmox with 4 logical cores on a 10 year old Xeon with 16GB RAM for the VM (I run ECC as was recommended at the time, but whether it’s still considered necessary I’m not certain).

I would also recommend getting an LSI HBA (host bus adapter) like the 9207-8i flashed to IT mode (it must not be in raid mode, let TrueNAS manage the disks directly). This simplifies passing through all the disks to a VM.

[–] thumdinger 1 points 4 weeks ago (1 children)

The options I’m looking at have PCIe 4 and seem to be gen 2? Epyc 7282 or 7302.

[–] thumdinger 2 points 4 weeks ago (3 children)

I think this is where I'm headed. Is there anything to consider with Threadripper vs Epyc? I'm seeing lots of CPU/MOBO/RAM combo's on ebay for 2nd gen Epyc's. Many posts on reddit confirming the legitimacy of particular sellers, plus paypal buy protections have me tempted.

 

I'm currently running a Xeon E3-1231v3. It's getting long in the tooth, supports only 32GB RAM, and has only 16 PCIe lanes. I've been butting up against the platform limitations for a couple of years now, and I'm ready to upgrade. I've been running this system for ~10yrs now.

I'm hoping to future proof the next system to also last 8-10 years (where reasonable, considering advancements in tech and improvements in efficiency), but I'm hitting a wall finding CPU candidates.

In a perfect world, I'd like an Intel with iGPU for QuickSync (HWaccel for Frigate/Immich/Jellyfin), AND I would like the 40+ PCIe lanes that the Intel Xeon Scalable CPUs offer.

With only my minimum required PCIe devices I've surpassed the 20 lanes available on desktop CPU's with an iGPU:

  • Dual m.2 for Proxmox ZFS mirror (guest storage) - in addition to boot drive (8 lanes)
  • LSI HBA (8 lanes)
  • Dual SFP+ NIC (8 lanes)

Future proofing:

High priority

  • Dedicated GPU (16 lanes)

Low priority

  • Additional dual m.2 expansion (8 lanes)
  • USB expansions for simplified device passthrough (Coral TPU, Zigbee/Zwave for Home Aassistant, etc) (4 lanes per card) - this assumes the motherboard comes with at least 4-ports
  • Coral TPU PCIe (4 lanes?)

Is there anything that fulfills both requirements? Am I being unreasonable or overthinking it? Is there a solution that adds GPU hardware acceleration to the Xeon Silver line without significantly increasing power draw?

Thanks!

 

Hey all, not a lot of activity here yet, but hopefully someone can offer some advice!

I'm having major regrets following migration from Core to Scale. The migration via update file went smoothly, but immediately apparent on starting up Scale, all of my SMB shares were broken. Both Linux and Windows clients are unable to connect.

I have since tried creating new users/groups (I noticed that my normal user and group with id's 1000 had been changed to 1001 in Scale), stripping ACL's and recreating, and deleting the shares and recreating. Failure to connect on each attempt.

Is there something I'm missing relating to the migration that prevents SMB from working? I'm not well versed in the inner working, or shell command available for troubleshooting, so most of this has been attempted through the GUI.

Also, I realise I have shot myself in the foot. Like an idiot, I saw the feature flag update message when Scale first started. I clicked through and upgraded without even thinking. I realised what I had done when I restored my Core VM from the previous day - the pool was offline, with zpool import showing an unsupported feature message. So any path back to Core is off the cards I think.

Any help is appreciated...

EDIT:

I think I have found the culprit. I downloaded the debug info and had a look at the SMB config (specifically net_config.txt). For some bizarre reason, the SMB interface had bound to an old IP address (two or three home network revisions ago - not used in many years).

[GLOBAL]

interfaces = 127.0.0.1 192.168.0.200

By selecting the systems current IP address in the optional "Bind IP Addresses" field in the global SMB service settings (under advanced), I've been able to rebind it to the correct address, and I have access (tested in Linux only so far)! phew...

view more: next ›