Search results

ok, so your nic is not started properly. Please post output of 1. systemctl status networking (while it is broken) then do a systemctl restart networking and systemctl status networking again

With not visible on the network I assume you mea you cannot ping the address of your proxmox Host, correct? So while you ping the proxmox Host IP from your client check with tcpdump -i eno1 icmp and tcpdump -i vmbr0 icmp on your proxmox if it is receiving the ping packages. Try to ping your...

Installiere den qemu-guest-agent. Gibt es im Log oom Killer einträge?

Du kannst die files als älter 24h markieren, dann sollte es klappen find /path/to/datastore -type f -mtime -1 -exec touch '1 June 2018 11:02' {} \;

Just found this https://youtu.be/oe1_JVl63a0?si=vyXpkWsChoqwWVSn

You can of course run multiple Services on one container, but i would recomment to use one container per service. You can do upgrades independently, so if pihole has an upgrade to the next debian release but eg paperless does not you can do that upgrade without breaking your other software...

If I change a card I know I changed a card AND I am physically present, so no problems at all. If I know the MAC I can adjust the settings even before swapping the card

In my estimation this is a BUG, not specifically in Proxmox but in linux in general, the (un)predictable Network Interface Names are a stupid idea

I would like a --hosts-only and --guests-only switch

I suggest something like "updater for pve"

Trying it right now, like it so far. I might be interesting to look at topgrade, which also upgrade flatpack snap cargo pip ... packages

You can also do a vgscan

And testdisk on sdb, there should be a second partition as a Physical Volume for your Volume Group Speicher on sdb

Do a pvscan /dev/sdb

At lvdisplay you posted the output of vgdisplay

For LXC Containers on arm you NEED arm container templates, the x86 container templates from proxmox will NOT work

Short intro to LVM: 3 Layers: - Physical Volumes - Volume Groups - Logical Volumes pvs shows the physical volumes (physical disks or partitions) vgs shows the volume group(s), VGs consists of one or more PVs (so if you run out of space you can add a new disk to your VG) lvs show your logical...

you cannot load kernel modules inside a container, you can mount it on the host and do a bindmount into the container

fdisk shows only a 16Mb Partition on your sdb and nvme. Maybe the partition table was lost / overwritten? Do you remember how it was partitioned? What kind of storage had you configured? LVM like on sda? zfs? Show output of cat /etc/pve/storage.cfg Show output of pvdisplay, vgdisplay...

Great, have fun