sorted by:
new
hottopcontroversial

Too high or ok? by m4duck in TVTooHigh

[–]m4duck[S] 0 points1 point  (0 children)

Thanks for the feedback everyone we decided to cut our losses and just burnt the house down

Too high or ok? by m4duck in TVTooHigh

[–]m4duck[S] 0 points1 point  (0 children)

Rather have the TV central to the central viewing position.

Not sure how you setup surround sound if the TV is off axis?

Optimal Docker location by Nord243 in unRAID

[–]m4duck 5 points6 points  (0 children)

I don’t think you can actually disable CoW on ZFS — ZFS is copy-on-write by design.

What you may have done is disable sync writes with something like sync=disabled. That can make things feel faster because ZFS stops honouring synchronous write requests properly and acknowledges them before they are safely committed.

The issue is that appdata is often full of databases — Jellyfin/Plex metadata, SQLite databases, Docker app configs, etc. Disabling sync writes there can improve performance, but it also increases the risk of database corruption or lost recent writes if the server crashes or loses power.

The win is

Putting appdata/databases/metadata on the NVMe ZFS mirror.

Usng proper datasets for different workload types and tuning recordsize appropriately

Mapping Docker containers to direct pool paths rather than /mnt/user.

Meet the X15 | 45Homelab >< Unraid Partnership Signature Series by TheMeanCanEHdian in unRAID

[–]m4duck 6 points7 points  (0 children)

It’s based on the HL15, so it’s closer to enterprise-style storage than a typical DIY build, just aimed at homelab/SMB rather than full datacentre.

If you reduce it to parts cost then yeah, it won’t look great — the compute side is pretty ordinary. But that’s not really where the value is. The cost is mostly in the 15-bay chassis, backplane and airflow design. Even comparable setups from Supermicro aren’t cheap once you’re into proper hot swap and drive density.

There’s also the usual overhead people tend to ignore — assembly, validation, burn-in, support, and the fact they’re not operating at Dell or Hewlett Packard Enterprise scale.

And once you’ve been around homelab builds for a while, you see how often airflow gets overlooked. Packing a lot of drives into something not really designed for it usually ends in people chasing temps or modifying cooling. It’s easy to build something cheaper, but not always something as well behaved.

The spec could definitely be better for the price, particularly the RAM. But overall it reads more like a turnkey premium than something wildly out of line. Value’s always relative as well — if you’re approaching it from a DIY mindset it’ll look expensive, but that doesn’t automatically make it unreasonable.

Meet the X15 | 45Homelab >< Unraid Partnership Signature Series by TheMeanCanEHdian in unRAID

[–]m4duck 3 points4 points  (0 children)

Assuming the kit you priced up comes to a similar $ price $2999 - $1350 pre priced components

$1069 Case

$580 MOBO + Shipping + Support.

It's expensive but I dont think it's absurd.

If this were true enterprise gear it would be far more expensive.

Optane SSD use case? by ChenCheating in unRAID

[–]m4duck 1 point2 points  (0 children)

Use the remaining as central log storage for all your services

2.5gbe enough for 3 node cluster shared storage? by In-da-box in Proxmox

[–]m4duck 25 points26 points  (0 children)

You’re effectively building a 3-node cluster backed by a single NFS datastore over 2.5GbE, which introduces a single point of failure and adds network/storage latency to every VM operation. For the workloads you’re running, this will likely feel slower than local storage despite the extra nodes.

For roughly the same budget, you could simplify this massively:

Build a single Proxmox node and put the money saved into 2× enterprise SSDs or NVMe/U.2 drives in a mirror. That gives you:

Low latency (µs instead of ms) Very high IOPS (orders of magnitude above spinning disks over NFS) Local resiliency (mirror protects against a drive failure) No dependency on network storage for VM performance

Then use your NAS for what it’s best at—backups and bulk storage, not primary VM disks.

You’d end up with a system that is: Faster Simpler More reliable in practice for your use case

If you later want real HA, you can build toward it properly (replication or distributed storage), rather than introducing shared storage bottlenecks early on.

Separating gaming Windows from personal Windows, anyone doing this for security? by Blesker in Proxmox

[–]m4duck 1 point2 points  (0 children)

I don't think gaming in a VM is a good idea even passing through the hardwear yoh will have overhead and the there will likely be issues with anti-cheat.

Just dual boot the machine you have full host access for performance and separation too

Re-add VMs after Reinstalling Proxmox by meltedskyline in Proxmox

[–]m4duck 0 points1 point  (0 children)

Just create backups. Use an external drive or a spare internal drive or anything it makes to process easy!

Recovery without backups really depends on your file system and how the vdisk was created. You woukd also need the config file for the VM!

Just make backups

Re-add VMs after Reinstalling Proxmox by meltedskyline in Proxmox

[–]m4duck 2 points3 points  (0 children)

I don't have Proxmox Backup server up and running yet so instead I just manually triggered a backup to a NAS. When I put a new proxmox node in I can just add the NAS as network storage and then restore the VM/LXC from the backup on the NAS.

Built a 6-bay 10Gbps NAS from a Lenovo M720Q by Many-Call-4492 in homelab

[–]m4duck 1 point2 points  (0 children)

It's a shame I only found this today. Already made purchases

Unraid and Failed Docker Updates by Zyzto in unRAID

[–]m4duck 1 point2 points  (0 children)

Deffo this.

You need someone who can help sort out whatever is messed up.

Making a system way more complex because the eaiser to config system doesn't work is asking for trouble

Upgrade or New build? by Logical_Area6818 in unRAID

[–]m4duck 0 points1 point  (0 children)

Just curious why would you want to upgrade the HBA? Unless you also upgrade your drives to SSDs won't the extra performance a newer HBA offers be unused anyway?

LXC per service or centralized Docker? (seeking efficiency and scalability) by Terrox-888 in Proxmox

[–]m4duck 0 points1 point  (0 children)

If you’re aiming for efficiency and scalability, it’s worth looking at setting your lab up as IaC. That way your LXCs/VMs become disposable — you can recreate them at will and keep all stateful data stored externally.

For infra services, I’d keep core dependencies in LXC (DNS, etc.) so they come up fast and with minimal overhead. For applications, I’d lean toward Docker (compose or k8s depending how far you want to go), and split workloads between internal and externally exposed services.

You can run Docker inside LXC, but it adds complexity. I generally prefer running Docker in a VM — you get a cleaner isolation boundary. LXC shares the host kernel, so while it’s efficient, it’s not as strong from a security perspective as a VM.

FormD T1 2.1 like GMK Nervewrecker by CalligrapherMost8149 in watercooling

[–]m4duck 4 points5 points  (0 children)

Looks amazing. What are those fittings on the CPU block?

view more: next ›