Search results

I've just set up the SMTP notifications on PVE - and the test email works fine. When the system itself starts to send notifcations via the SMTP path, the mail server replies with: <email@host.com: host mail.server[<mail server ip>] said: 530 5.7.0 Must issue a STARTTLS command first (in...

@t.lamprecht - I'm just wondering if anything became of this.... I'm just looking through all this again because PBS and PDM both need the same 'hack' for me to get the nsupdate DNS method working for ACME. It's been a bit of silence for quite some time - and its getting more difficult to keep...

I have a feeling that its the way PVE has snapshotted / backed up the VM... ie when the filesystem is still in use. It's obviously mostly in tact, as I can browse the files in PVE's "File Restore" - but likely because it isn't cleanly unmounted. XFS would normally check the fs on mounting next...

I guess it depends on the filesystem that the VM guest is using. In this case, something about how the backup functions causes the mount to fail. The block device is still there and available, but the filesystem can't be mounted.

Yeah - I mean, it makes sense that it would be read-only image - however if we can't mount it at all, then it means recovering an individual file via the PBS client isn't really possible. I did note that the "File Restore" function in PVE seems to allow me to browse the image though: This...

Interestingly, I'm trying this out with the PVE integration... When I'm trying to mount a snapshot of a VM on the PBS server to browse the backup, I'm getting: root@pbs:/mnt# mount -o ro /dev/loop0p2 /mnt/tmp/ mount: /mnt/tmp: cannot mount /dev/loop0p2 read-only. dmesg(1) may have more...

Done: https://bugzilla.proxmox.com/show_bug.cgi?id=6473

So, here's what I've come up with so far...... I hooked into udev via /etc/udev/rules.d/local.rules as: KERNEL=="sda", ACTION=="add", ENV{SYSTEMD_WANTS}+="backup_to_usb.service" KERNEL=="sdb", ACTION=="add", ENV{SYSTEMD_WANTS}+="backup_to_usb.service" That fires off the following systemd...

Interestingly, I came across this thread hunting for this type of feature. I currently use a backup system that I've built over 20+ years of use that uses rsync + snapshots + btrfs that also backs up the latest VM contents to an external disk when inserted / hotplugged. This uses LUKS etc as...

Have you configured things to use amd_pstate_epp? I had to add `amd_pstate=active` to the proxmox hosts kernel command line, and I use the amd-epp-tool to get the current configs:

PVE is my gateway - it has a WAN subnet (a public /29), and the VMs all hang out on vmbrX which isn't bound to any network adapter.

Oh, I should say that downloading from the VM to that host is ~270-300MB/sec - doesn't matter if its IPv4 or IPv6.

Hmmmm - not sure - they mention specifically pci id 14e4:1752 - mine shows: $ lspci -nnd ::200 01:00.0 Ethernet controller [0200]: Broadcom Inc. and subsidiaries NetXtreme II BCM57800 1/10 Gigabit Ethernet [14e4:168a] (rev 10) 01:00.1 Ethernet controller [0200]: Broadcom Inc. and subsidiaries...

Looking at the iDRAC, its this: Server is a Dell PowerEdge R730.

I've stumbled across this trying to debug a weird network problem. Running the Ookla speedtest cli program on the host itself, I see: $ ./speedtest Speedtest by Ookla Server: Spintel - Sydney (id: 58437) ISP: Spintel Idle Latency: 0.45 ms (jitter: 0.09ms, low...

I use Home Assistant and log power consumption via a Zigbee based power switch. Lets me measure the actual consumption being drawn from the socket and not calculated via other methods.

Do you have details on what this is? As I posted, I saw it on an N100 CPU embedded board - which in my case has no proxmox or ubuntu on it - so would like to investigate. EDIT: Ah - just updating to kernel 6.14.2 did the trick.

I tried to report a bug to the `linux-edac` mailing list, but I'm not sure the post made it through. I've got an UP7000 embedded board, and kernel 6.13.x doesn't show this behaviour, but 6.14.1 does. This is using Fedora 41 as the distro - so this certainly isn't a proxmox issue. EDIT: Link to...

Some good news, updating to kernel 6.14 dropped the power usage in my rack by ~15 watts. Two proxmox systems, a 3700x and 5700g CPU. You can see when I rebooted both of them into the 6.14 kernel.

If you read the information on how to use DNSBL's, they *ALL* state not to use public DNS servers to query their services. That's why you have a problem. For further: https://pmg.proxmox.com/wiki/index.php/DNS_server_on_Proxmox_Mail_Gateway