Search results

Yes. But above still applies - pointless to apply twice.

I can’t remember the details and don’t have it in front of me but I thought Nut could be configured to continue with shutdown of the UPS (and therefore cut power to the server) once beyond a point of “no return” and even if power then comes back again? In order to avoid exactly this problem...

It's possible to do shared storage over iSCSI - i.e. multiple Promox nodes on top of one big iSCSI LUN on your NAS - but it requires faffing around with LVM on top of iSCSI and you lose snapshots and other features. NFS is much more straightforward, I would recommend this instead. Do you have...

Agreed, iSCSI provides the best results (vs NFS) in my own experience and I think that’s also common wisdom here and on other forums. Probably for a multitude of reasons, including that NFS invariably leads to sync writes which then requires a very fast slog to approach async performance...

As mentioned already, as awesome as ZFS is, those features come at a cost, including write amplification and hardware requirements if you’re going to make it fly. And some of those features, for example checksumming and compression, are even pointless if applied twice on top of each other, while...

PS. I used to but don't use OpnSense any more - but check if you're logging stats with netflow (heavy writes), you can also configure OpnSense to keep /var in RAM which of course means log files won't survive reboot, but should reduce writes significantly, particularly if something is...

Ok good that you found the smoking gun. Just need to keep narrowing it.

You want ashift 12 (4096 byte sectors): root@pve01:~# zdb -C | grep ashift ashift: 12 Recordsize: root@pve01:~# zfs get recordsize rpool NAME PROPERTY VALUE SOURCE rpool recordsize 128K default Volblocksize: Proxmox GUI: Datacenter -> Storage -> [your pool] -> Block...

I can add another data point. Am running a 2 node cluster and with all the above-mentioned services enabled, with default settings. ~7TB written in approx 2.5 years 24/7. That’s ZFS on single disk (enterprise SSD). All VMs on separate storage, so provides some clues therefore on roughly what to...

Interesting, and doing some simple maths - 774TB in 16 months becomes approx 1.6TB per day, nearly 70GB per hour, roughly 1GB per minute, nearly 20MB/s… IF it is evenly distributed like that, you should be able to run some diagnostics and try to figure out where the write pressure comes from...

LSI 9300-8i (based on SAS3008) are popular in the TrueNAS community. You could buy new or cheap second hand on eBay. Make sure it has the most recent "IT" firmware, tools are available on the Broadcom website.

My recommendation would be to start with the motherboard, and look for a server board if possible. SuperMicro and ASRock Rack are both highly reputable brands, Gigabyte does server boards too but I have no experience of them myself. Server grade motherboards are designed to run 24/7, typically...

ASRock Rack X570D4U is a server motherboard with remote IPMI management and ECC support, but takes a regular Ryzen AM4 CPU. Good compromise. They’ve also more recently released B650D4U for latest gen AM5 Ryzen CPUs. Edit: to add, if you go down that route, check recommended RAM on ASRock Racks...

Thanks for your suggestions. Any recommendation where I would start looking in order to get started with such a setup? Haven’t used Ansible or Puppet before.

Hi @BobhWasatch and thanks for your answer! You misunderstand my question though. Maybe I wasn't clear. I have no problems at the gateway side of things. All devices on my network have a link-local address (generated by the device itself) in the fe80::/10 block, a ULA (unique local address) in...

PS. note to mods - apologies if posted in the wrong forum, feel free to move to networking if that’s where it belongs..!

Hi, I'm running Proxmox 8.0.4 on a two node cluster plus a qdevice (RPi). Works well. My ISP recently enabled ipv6 with a dynamic /56 prefix which also works well. The wan gw acquires the prefix from ISP using WIDE-DHCPv6, and uses dnsmasq as DHCPv4 server as well as SLAAC for ipv6. Dual-stack...

Interesting. I’m speculating here but thinking it could boil down to the classic scenarios of latency vs throughput. If your write operations are sync and therefore inherently dependant in the SSD completing the write, this always comes with a certain overhead irrespective of the amount of data...

1) how does your VM connect to the network? Generally Truenas doesn’t know or care whether the client is a VM in a hypervisor or something running on bare metal. Check permission in truenas and ensure you’ve installed all the NFS client libraries in your VM. 2) connect direct from the VM i.e...

Minor correction. I don't think Emby will re-encode the file if the client is able to support it in its original format. In that case the file will just be streamed as-is. In other cases, the server will re-encode the file into something that the client can support (and this can be a killer...