Search results

Do a tcpdump -ni any port 22 inside your VM and try to SSH into it. Check if you see incoming and or outgoing packets

Your zfs pool is almost full, so the subvolume 100 is almost full, too. Technically pct resize sets the refquota, which limits the space the subvolume can take inside the pool, but your pool is full.

Do a zfs list on your proxmox host and post the result

Then it was created a sparse file, in a sparse file instead of a million zeros being written Linux will write "here come a million 0" You see the difference with ls -l file and du file. ls will show you the nominal size, du the real size on disk. But the raw file will not shrink

You are using a raw file as disk image, even when empty it uses the full space. A raw image is like a bitwise copy of a disk, if it is empty it is basically a big file full of zeros. Unfortunatly on Directory Storage Containers ONLY support raw image files. These also do not offer snapshots...

I would: Remove one of the 2 TB HDDs first, add the new 8 TB HDD, and then mirror the data from the remaining old 2 TB HDD but both should work, if you have the free slot

My recipe: Zpool replace disk ================== Get disk IDs ls -l /dev/disk/by-id/* Get zpool status: zpool status this assumes the following disk layout: Part 1: BIOS Boot Part 2: EFI Part 3: ZFS Copy Partitions from working to new disk, without copying label and UUIDs: sfdisk -d...

If you do not use it (no NFS),just disable rpcbind: systemctl disable --now rpcbind.service rpcbind.socket

Show Output of df -h and vgs and lvs

I am not sure, but I think not, sorry, have never used the built-in firewall

Then use the dnat method

1. You can use hetzners vSwitch feature to get additional official IPs, which you then can use on your VMs/containers. 2. You can set up a vmbrX interface with no physical network interface and a private network, eg 192.268.100.0/24. Now you can enable ip_forward and create firewall rules to...

Erstes Terminal: watch -n 10 xtightvncviewer localhost & ---- Hetzner Webinterface Rescue System starten Zweites Terminal: scp ISO/proxmox-ve_8.1-1.iso RESCUE: ssh RESCUE -L 5900:127.1:5900 altnames der Netzwerkinterfaces ermitteln: ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc...

1. ping 8.8.8.8 from your container 2. on the host check with tcpdump -ni vmbr0 icmp if you see the packets 3. check if you see the packets on your external interface with tcpdump -ni enp1s0 icmp for the outgoing packets, the sender address should be changed to 192.168.178.126 by the masquerade...

Please post your /etc/network/interfaces Bridges in proxmox must be named vmbrX

ok, ipcalc 63.141.251.170/29 Address: 63.141.251.170 00111111.10001101.11111011.10101 010 Netmask: 255.255.255.248 = 29 11111111.11111111.11111111.11111 000 Wildcard: 0.0.0.7 00000000.00000000.00000000.00000 111 => Network: 63.141.251.168/29...

The subnet entry is: Subnet: 63.141.251.170/29 see above

The subnet is the first IP in your range, the broadcast is the last. The subnet mask can either be written /29 (CIDR Notation) or 255.255.255.248

I assume 63.141.251.171 is the gateway, 172 is your proxmox host, so your VM will have to be the next free IP 173: Subnet: 63.141.251.170/29 Address: 63.141.251.173/29 Gateway: 63.141.251.171 Nameserver: 8.8.8.8 or 1.1.1.1 or 9.9.9.9

Do a static IP configuration in your vm