Search results

For the sake of completeness, pve8to9 didn't show me the FAILED item prior to update, only after the update. I was worried about the server not rebooting because of the warning, but it still rebooted fine. And I followed the pve8to9 instructions after the reboot. After that i did a final reboot...

so I did : apt install systemd-boot-efi systemd-boot-tools apt remove systemd-boot apt purge systemd-boot It told me systemd-boot-efi and systemd-boot-tools are already installed... Rebooted, all seems fine, `pve8to9` is all green.

I think I'm in the same boat... After performing the update & rebooting here's where I'm at : root@pve:~# pveversion pve-manager/9.0.6/49c767b70aeb6648 (running kernel: 6.14.11-1-pve) root@pve:~# proxmox-boot-tool status Re-executing '/usr/sbin/proxmox-boot-tool' in new private mount...

uidmap doesn't seem to be installed. That would make total sense ! Dankuwel for the insight.

I'm preparing for a migration for Proxmox from a system based on dual Xeon L5640 to a system running a i7-6700T. (don't ask). One of the containers is a Plex media server. The Xeons have no iGPU, but never had any issues with transcoding. 24 cores FTW !!! :cool: The i7 needs the iGPU to lend a...

I'm not in an urgency, was just exploring how to restore from a backup made with proxmox-backup-client. Hopefully I'll never have to, and if I do then the WebUI will be a feature ;)

yup :(

I get an error with proxmox-backup-client catalog shell root@pve:~# proxmox-backup-client catalog shell host/pve/2024-10-21T02:29:46Z testdata.pxar --repository root@pam@192.168.11.98:USB_WD --keyfile /root/testbackup.key Encryption Key Password: ****************************** Error: Unable to...

I just came across a use case. I'm doing automated encrypted backups from a linux machine with the proxmox-backup-client. The backup consists of a few directories. It would be great to be able to browse these backups from the PBS WebUI, instead of having to restore them first with the CLI, and...

Your host isn't resolving smtp.google.com Please post the output of dig smtp.google.com Same for cat /etc/resolv.conf

I've had this symptom on 2 separate fresh installs, that is 2 Intel SR1695 servers with 2 different monitors & 2 different vga cables.

While not crucial, it is bothering me... see screenshot. This is a fresh install on older hardware, display is VGA. On every reboot of the host, the solid background color is a different one. I've had blue, green, yellow, red... you name it. Why is it doing this ?

in 2023 testing with the PVE script should be done with : echo "test" | /usr/bin/proxmox-mail-forward Logging is now handled by systemd's Journal. use the command journalctl to show the system log (including postfix messages) To jump to the end of log, press shift+g

Better safe than sorry . Replaced the drive. Thx for the help !!!!

Team, I've been getting this notification : So...attribute 202 Percent_Lifetime_Remain has changed, good to know. SMARTCTL tells me that the value is now 99%, nothing to worry about imo - right ? For completeness : Thing is, I'm getting notifications every 24h (exactly as the message...

This : smtp.gmail.com[2607:f8b0:4023:c03::6c]:587 indicates that Postfix is using IPv6 to reach the relay. Is your network/isp setup for IPv6 ? If not, add this to main.cf : inet_protocols = ipv4 and remove any other lines starting with inet_protocols Then restart postfix systemctl restart...

There is no zfs log file. The script mentioned above _creates_ a log file, at /root/ZFS/ZFS-LOG.txt, but only if any problems were detected. If you edit the script to include the changes I proposed, then you will also get logging on problems in /var/log/syslog.

what does that mean ? yes

@ozgurerdogan , makes no sense to me because date: invalid date ‘errors on Sun Nov 8’ isn't an error message . Those lines, and in fact the entire script works just fine on a Proxmox system. So, once again, is what you pasted the exact and complete error message ? EDIT : did some more digging...

Are you saying that the exact and complete error message is : date: invalid date ‘errors on Sun Nov 8’ ./zfs_health.sh: line 114: 1606208467 - : syntax error: operand expected (error token is "- ") That would not make any kind of sense...