Search results

It is "obviously" not syncing or the time would be correct. What is the actual output of "chronyc sources"?

If your wg_server is behind a normal ISP router it isn't going to be reachable from the Internet without making some configuration changes there, like enabling a port forward.

According to Intel this chip does theoretically support VT-d but based on this [ 0.056635] DMAR: IOMMU enabled [ 0.417629] pci 0000:00:00.0: DMAR: Disabling IOMMU for graphics on this chipset [ 0.417632] pci 0000:00:00.0: DMAR: Forcing write-buffer flush capability it may not be...

If he removes it he will find out what if anything depends on it. Apt will tell him :)

Interesting. I installed mine via Debian so maybe there is some difference after all. Seems pretty clear that it isn't needed for anything though and it is safe to remove it.

I don't have nmap on my PVE 8.3.3. I don't think it is a dependency of any PVE components. You can use "apt rdepends" to find out what might be depending on it.

The following variation allows you to disable the storage (with pvesm or the GUI) and unmount the drive. Later you can plug it back in and re-enable the storage and it will automatically be mounted. I use a label rather than a UUID so I can rotate my backup drives (they all have the same label)...

It isn't my problem. I was just making a suggestion of a possible reason. So I won't be posting any benchmarks. Thanks.

BTW, PVE does not emulate AMD instructions when running on Intel or vice versa. The CPU flags are really just visibility flags. They can hide features but not create them. The purpose of this is to facilitate live migration between not-identical hardware.

It could be because when you installed Windows on an Intel CPU it decided that certain features were available and said features are not existing or differently implemented on AMD. So it is falling back to a generic version that is slower.

1 TB = 1000 GB. So 2 TB = 2000 GB. Therefore you should write 2000. And maybe learn Si prefixes.

So you plan to put 200 TiB (200,000 * 1 GiB = 200 TiB) on a 5.5 TiB storage? How's that supposed to work?

What kind of storage is "Daten"? Perhaps the limitation comes from there.

Don't shut down active NFS shares. NFS does not play well with unreliable servers.

This is sounding a lot like a duplicate IP somewhere on your network. If that is the case you can get connection reset by peer because you're not connecting to what you think you are.

There already is one. This thread is about making it suitable for longer notes.

Or just install the one from debian-backports. That's what it is for.

Version upgrades on the stable repo only happen when stable is upgraded to the next version. Debian back-ports fixes rather than updating the package because that might break configuration files and such. So not until trixie is released will the packages be updated.

Maybe look in dmesg and the journal to see if there are any related messages. You could also maybe post what's in /etc/network/interfaces and the output of "ip a". Offhand I can't think of any reason why the physical net driver would have anything to do with it.

I think that if you don't want it to use swap then maybe disable the swap. I mean, is it there to be used or is it a decoration? ETA: If you have 28 of 31 GB in use, maybe having swap is why you have free RAM.