Recent content by orosmannaro

My fault! I made a mistake configuring the PMG repository (buster instead bullseye). Sorry ...

Thank for your answer @t.lamprecht. I have already run apt update && apt dist-upgrade && apt full-upgrade (as described in the FAQ) but the PMG version is still 7.0 (pmgupgrade also returns Your System is up-to-date): pmgversion pmg-api/7.0-8/36f2537c (running kernel: 5.13.19-2-pve)

I am running PVE 7.1 and would like to create a CT with PMG 7.1 but I cannot find it in the template list (as shown in the attached screenshot).

Ok. I this case the most important thing will be to correctly set the Outgoing NAT, to be sure that email comes out from one of the two IP configured in the DNS ... Thanks!

Scenario: Zimbra mail server behind Proxmox Mail Gateway in a LAN with two Internet connections in load balancing mode. In this case the VM running the Proxmox Mail Gateway must have two NICs, one with public IP from the first ISP and one with public IP from the second ISP. And these IP must be...

Thanks a lot LnxBil

Maybe I'm wrong, but I struggle to trust the documentation as it contains gross errors like the one shown in the attached screenshot, because I have the feeling that things have been written with little care ... Also the zpool replace command uses the entire path of the devices...

ls -l /dev/disk/by-id/ total 0 lrwxrwxrwx 1 root root 9 Nov 10 17:52 ata-ATP_SATA_III_2.5_inch_SSD_005212000983 -> ../../sda lrwxrwxrwx 1 root root 10 Nov 10 17:52 ata-ATP_SATA_III_2.5_inch_SSD_005212000983-part1 -> ../../sda1 lrwxrwxrwx 1 root root 10 Nov 10 17:52...

Yes: /dev/sda is the good disk and /dev/sdb is the new installed disk. I have already do this (copy partitioning layout and assign a new GUID): sgdisk /dev/sda -R /dev/sdb sgdisk -G /dev/sdb Now I'm checking the correct way to run zpool replace command (I have some doubts about the correct...

I have read some posts on how to replace a bad disk of a ZFS mirror. But I have to work on an up and running production system, so I can't make any mistakes. This is my first time doing this, so I'm asking for help. The damaged disk has already been replaced and the current state of Proxmox's...

But in this case we would expect the same "errors" also for the second disc ... right?

The PVE server is sending these emails: The following warning/error was logged by the smartd daemon: Device: /dev/sda [SAT], 1 Currently unreadable (pending) sectors Device info: ATP SATA III 2.5 inch SSD, S/N:005212000983, WWN:5-141357-010019399, FW:T0205B, 120 GB SMART values (attached)...

Thanks again!

Thanks daniel! Can I trust this message even if smartctl says that SMART support is not available?

From a PVE 5.3-12 server with 2 RAID1 disks sda, sdb I'm receving this emai from smartd. This message was generated by the smartd daemon ... The following warning/error was logged by the smartd daemon: Device: /dev/bus/0 [megaraid_disk_05] [SAT], 1 Currently unreadable (pending) sectors ...