Recent content by jsalas424

I recenty upgraded my Debian LXC running DNS and backups have started to fail. Here's a writeup of the investigation. What is the right way to address this? PVE 8.4.13 Issue:Automated backups of LXC container 101 (AdGuard2, Debian 11) started failing after running apt update && apt...

I gave this theory a try. I removed all mount points from the LXC, backed up and restored as unprivileged. I still get tar: ./var/lib/docker/volumes/backingFsBlockDev: Cannot mknod: Operation not permitted tar: ./var/spool/postfix/dev/urandom: Cannot mknod: Operation not permitted tar...

I'm on PVE 8.2.4 w/Kernel Linux 6.8.8-2-pve and am still seeing this issue on my Intel NICs. Is ethtool -K eno1 gso off gro off tso off tx off rx off with a postup in the /etc/network/interfaces file still the prescribed fix? Is there an effort/intent to fix this permanently? I'm seeing this...

Hi Fiona, thanks for the reply. Here are those results. Should I proceed to memtest? root@ServerB:~# debsums -s libperl5.36 perl-base debsums: package libperl5.36 is not installed No output for just debsums -s root@ServerB:~# debsums -s root@ServerB:~# lastly I also checked config files but...

This has recurred and was once more quickly fixed with `systemctl restart pvestatd`. No firewall log issues so I think that was a red herring, but I did find some more enlightening logs: Aug 29 13:04:48 ServerB pvestatd[2470]: lxc console cleanup error: IO::Handle: bad open mode: at...

I rebooted the node and the firewall errors stopped, there was definitely something odd. Although always possible it’s an intrusion, that feels very unlikely given that the only 2 open ports are an SSL port to a 2FA guarded Nextcloud instance and a wireguard VPN. I also only have default...

A single node is grayed out, this has happened before and succesfully cleared with systemctl restart pvestatd but it keeps recurring so I checked my logs: There was an uptick around 13:00 so I honed in on that to find that these error messages suddenly started appearing over and over...

I'm trying to send a VM backup to a S3 bucket that has been mounted to a local file. I have succesfully backed up to this mounted share directly from proxmox with a ~25GB disk, but fails on a ~125GB disk. INFO: starting new backup job: vzdump 900 --notes-template '{{guestname}} baseline...

The "other" mac address that flashes in "c2:c8:66:bb:9e:de" seems to be what gets assigned to both the VLANs and some ethernet connected devices. I don't think this is a duplicate we're hunting down but worth the hunt. So I cleared all DHCP leases, restart the DHCP service, and cleared the...

Here's an interesting something. My ARP monitor sent me a "Arpwatch Notification : flip flop" message: hostname: pveserver01.TracheNet ip address: 192.168.1.10 ethernet address: 18:03:73:32:b6:7c ethernet vendor: Dell Inc. old ethernet address: c2:c8:66:bb:9e:de old...

Yes I can ping other devices, there’s a code chunk in there showing the results of pinging 192.168.1.15 I see the pveserver in the ARP table and no duplicates: But just to be safe, I cleared the ARP table. That didn't help.

I used the =9916e23271e8cf3207741acc7714efa2']latest iso for did a fresh install. I used the network setup options part of the installer with the following parameters: Address: 192.168.1.10/24 Gateway: 192.168.1.1 DNS: 192.168.1.1 I can connect to the web portal with 192.168.1.10:8006: The...

So would the flow be: 1) Repair MBR table/CRCs on healthy disk 2) Copy to New disk 3) convert new disk to gpt with gdisk? 4) Confirm that can boot: repeat to get GPT on old healthy disk? Can I use GPT with legacy bios booting? For context, the dying disk was created with PVE 6.x iso installer...

@leesteken , hopefully last question. I can boot from /dev/sda2 fine, but the gdisk info looks weird, I don't want to clone in the new drive without making sure the partition is okay to begin with. root@Server:~# gdisk /dev/sda2 GPT fdisk (gdisk) version 1.0.6 Warning: Partition table header...

This no longer matters. /dev/sdb2 is the dying disk that needs to be replaced. I was able to boot from /dev/sda alone so problem solved! Thanks for the help.