Recent content by Tommmii

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...

EDIT : I went back into syslog, 45 minutes later... all looks as expected... rsyslogd seems to have taken a few minutes before actually using the new conf file. While trying to discard these log messages : Oct 18 12:12:00 pvex systemd[1]: Starting Proxmox VE replication runner... Oct 18...

Yes, also see : https://forum.proxmox.com/threads/how-to-chage-notification-email-address.30241/

just adding, both those drives were brand new, so whatever was on those SSDs came from the original Proxmox installation (which I had to wipe because that was easiest way to get back to a working system).

It is indeed solved (but unexplained), and I've now marked the thread accordingly. Those are another non-boot raidz1 pool. They didn't come into play. Correct, and I fail to understand how the system booted at all, since none of the rpool members had a boot partition. Although they both had a...

I can't any more, system has been re-installed from scratch since yesterday. fdisk showed just 2 partitions, where a fresh install shows 3 partitions on the rpool members, the boot partition being the crucial missing one I believe.