Yes, but it's not garbage, it's the solution to the problem, you can make it pretty as you like, I'm just trying not to make people scroll through 17kb of gobbledigook or force them to login or having handles extra files.
This doesn't have to go...
Replacing ifupdown2 by the quite old ifupdown package is from my point of view a workaround and not a permanent fix. I propose another workaround to this issue: stop using ifupdown2 or ifupdown (and the legacy "networking" service), and use...
You should consider some side effects of using encryption in different ways. Is it ok for all the VMs to share the same key? Is it ok for all the hosts to share the same key? Do you actually need the hosts encrypted too? Is it ok for the...
Yes, in the sense this is a feature that has a procedure to function in a linux system. If you specify By WHOM, you'd know who to ask specifically.
If you mean per the Proxmox zfs on PVE pages, its "experimental" in the sense it is not within...
Looks like a temporary failure in DNS resolution. Try to debug it using : ping, dig, resolvectl, nslookup, host, etc
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
This is the way.
You can do this but it serves no real purpose; the storage is shared.
Curious- what is the friction? adding and removing nodes is straight forward.
Others may chime in, but I think I see three paths forward for this:
- Add the 5050 micros to the existing 5060 tower, migrate the VMs, then remove the 5060
- Set up a new 5050 micro cluster, then use PDM to migrate the VMs from the 5060 to the...
Wie alt ist die Hardware? Lässt sich ein Hardwaredefekt sicher ausschließen? Gibt es auf dem Mainboard sichtbare Auffälligkeiten, zum Beispiel beschädigte oder aufgeblähte Kondensatoren?
Those warnings come from the /lib/modules dirs you deleted. The kernels (6.5, 6.8, 6.14) are still installed per dpkg, so update-initramfs -k all tries to build initrds with no modules.
Your purge plan sounds good - apt removes 9 packages. Also...
Thanks for the info. :)
In any case, I'll not be using apt autoremove to remove kernels anymore, no matter how much it asks me to. :P
EDIT: And that ended up clearing ~5 GB off my boot partition, too. :)
rc are removed packages with old configs. You can remove them all with apt autopurge '~c'. See here for what ~c does.
That also works for stuff like apt list '~c', for example.
Thanks again. I don't remember how or why I tried removing kernels manually (I always just stick to apt autoremove when I'm conscious of what I'm doing), but I clearly didn't know what I was doing at the time. I'm glad it wasn't the most horrible...
With the new firmware the card also get locked up but now with even different error messages:
Oct 09 21:42:11 kvm1 kernel: bnxt_en 0000:10:00.0 enp16s0f0np0: Abandoning msg {0x37 0x7fce} len: 0 due to firmware status: 0xffffffff
Oct 09 21:42:11...
Those warnings come from the /lib/modules dirs you deleted. The kernels (6.5, 6.8, 6.14) are still installed per dpkg, so update-initramfs -k all tries to build initrds with no modules.
Your purge plan sounds good - apt removes 9 packages. Also...
Looks like a temporary failure in DNS resolution. Try to debug it using : ping, dig, resolvectl, nslookup, host, etc
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox