惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Vercel News
Vercel News
F
Fortinet All Blogs
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
GbyAI
GbyAI
MongoDB | Blog
MongoDB | Blog
Jina AI
Jina AI
aimingoo的专栏
aimingoo的专栏
I
InfoQ
IT之家
IT之家
罗磊的独立博客
Blog — PlanetScale
Blog — PlanetScale
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
The Cloudflare Blog
爱范儿
爱范儿
Microsoft Azure Blog
Microsoft Azure Blog
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
美团技术团队
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
B
Blog RSS Feed
G
Google Developers Blog
大猫的无限游戏
大猫的无限游戏
博客园_首页
Engineering at Meta
Engineering at Meta
Martin Fowler
Martin Fowler

Proxmox Support Forum

[SOLVED] - Github Auth for Mirrors-Kernel Repo? [Automation] Mass migration tool for MS Win11/Server Proxmox GUI hang - not response is it possible to reject or quarantine spam based on conditions I set ? The PVENode task list in PVE9 is partially obscured due to the terminal font being too large. About 100% error reporting due to pveproxy.service hooks Kubernetes overlay networking breaks when upgrading from PVE 9.1 to PVE 9.2.3 Zentraler Speicher No space left on device Combine datastore and direct file archival to tape Kernel panic VFS: Unable to mount root fs on unknown-block (0,0) sobald ein 7.x Kernel verwendet wird. How to migrate disk of a VM from one ZFS to another Windows Server 2025 fails to boot after PVE 9.2 / Linux 7.0 Kernel upgrade Cannot Install Proxmox on T610 Poweredge with H700 PERC card sdn Config. gateway not reachable How to safely change domain/FQDN? Welche Filterquote erreicht ihr? NFS Share status unknown on 2 of 5 nodes Can't connect to PVE9 consoles [solved] Can't connect to PVE9 consoles [solved] [SOLVED] - Use secondary network for PVE commands Created cluster, one node storage gone BUG: proxmox mail gateway FROM = null bypass spam filtering Moving existing PBS from VMWare workstation to PVE cluster Does eBGP SDN fabric support external peering? Bug: PDM 1.1 not recognizing valid license status Proxmox GUI hang - not response PVE crashes unexpectedly Proxmox Backup Server 4.2 released! Advice
Proxmox 9.2.3 not sending email notification for degraded...
invalid@exam · 2026-06-13 · via Proxmox Support Forum

Hi team.

I have a server with two ZFS mirror disk arrays: rpool and vmdata, running PM VE 9.2.3 on a supermicro server.

I configured email notifications both in the Proxmox GUI and in console(postfix). I tested them, and they work correctly.

I left the default matcher unchanged. The only thing I modified was the notification target, where I configured it to use the email notification target I added.

I disabled mail-to-root and only kept my Gmail notification email address configured.

Now I performed a simulated pool degradation test. I removed one of the disks from the rpool array, where Proxmox 9.2.3 is installed, and then rebooted the server. The server booted correctly, and my ZFS pool is now degraded. However, I have not received any email notification about the degraded pool.

Is this normal, or is there something else I need to configure so that ZFS or Proxmox sends me a notification when a pool becomes degraded?

The mail test works correctly. I also performed two VM backups, and I received the corresponding email notifications. I also received ZFS scrub event notifications, such as:

ZFS scrub_finish event for rpool on proxmox-srv

If I run ' zpool events -v', I don´t see any degraded event, is like ZFS haven´t detect the status.

root@proxmox-srv:~# zpool status rpool

pool: rpool

state: DEGRADED

status: One or more devices could not be used because the label is missing or

invalid. Sufficient replicas exist for the pool to continue

functioning in a degraded state.

action: Replace the device using 'zpool replace'.

see: https://openzfs.github.io/openzfs-docs/msg/ZFS-8000-4J

scan: scrub repaired 0B in 00:00:53 with 0 errors on Thu Jun 11 22:13:25 2026

config:

NAME STATE READ WRITE CKSUM

rpool DEGRADED 0 0 0

mirror-0 DEGRADED 0 0 0

10646346849731093859 UNAVAIL 0 0 0 was /dev/disk/by-id/ata-Samsung_SSD_850_EVO_250GB_S2R6NX0J622618X-part3

ata-Samsung_SSD_850_EVO_250GB_S3PZNF0JA23975A-part3 ONLINE 0 0 0

errors: No known data errors

Could this be a bug, or am I missing an additional configuration step?

Any advice is welcome. Thank you very much, colleagues.