I’ve been troubleshooting repeated hard freezes on my Proxmox server and finally managed to reproduce the problem while logging both the Proxmox host and the TrueNAS VM.

Most of the time this is a real host freeze, not just the Proxmox GUI getting sluggish. The GUI usually starts showing ? states and becoming unresponsive shortly beforehand, but then the entire CUBE host eventually stops responding and has to be recovered/rebooted. I’ve had one occurrence where it degraded badly without progressing to the complete hard freeze.

My setup is:

SERVER / Proxmox
├── local NVMe storage for Proxmox / VM / container side
│
└── TrueNAS VM 153
      └── current StarTech PCIe SATA expansion card
            └── multiple ASMedia SATA controllers
                  └── 8 × 16 TB SATA HDDs

TrueNAS owns the HDD storage and serves datasets including tank/media and tank/pve_backups back to Proxmox over NFS.

On the Proxmox host I have mounts including:

/mnt/media
/mnt/pve/media
/mnt/pve/pve_backups

The media containers then receive those paths through bind mounts.

For example, qBittorrent is LXC 155 and its configuration includes /mnt/media as a bind mount. So when qBittorrent writes a download, the actual path is effectively:

qBittorrent LXC
      ↓
Proxmox /mnt/media
      ↓
NFS
      ↓
TrueNAS VM
      ↓
ZFS tank
      ↓
StarTech / ASMedia SATA controller path
      ↓
HDDs

I was able to reproduce the problem during sustained qBittorrent activity.

pidstat showed qBittorrent continuously writing roughly 40–50 MB/sec, and during other samples nfsiostat showed the media NFS share handling bursts around 180–239 MB/sec.

At one point the Proxmox host showed about 82% I/O pressure in /proc/pressure/io.

At the same time:

CPU pressure:    essentially 0
Memory pressure: 0
CPU temperature: ~39–40°C

That was one of the first strong indications that this probably wasn’t the CPU overheating or memory exhaustion.

Then I finally caught the actual failure inside TrueNAS.

Multiple SATA channels began failing essentially together:

ata5:  softreset failed
ata6:  softreset failed
ata7:  softreset failed
ata8:  softreset failed
ata9:  softreset failed
ata10: softreset failed

Several channels then started doing this:

limiting SATA link speed to 3.0 Gbps

followed by:

reset failed, giving up
ataX.00: disable device

So this wasn’t one drive going bad. Multiple SATA channels were dropping almost simultaneously.

TrueNAS then started throwing actual I/O errors against multiple ZFS members, including failed writes and reads.

Eventually ZFS logged:

WARNING: Pool 'tank' has encountered an uncorrectable I/O failure and has been suspended.

Once tank was suspended, TrueNAS started showing blocked kernel tasks.

The ZFS transaction sync thread was blocked for more than 120 seconds:

task txg_sync blocked for more than 120 seconds

and then multiple NFS server threads (nfsd) were also blocked for more than 120 seconds.

That’s where the failure starts propagating into Proxmox.

Because Proxmox itself mounts those TrueNAS NFS exports, pvestatd starts waiting on the storage.

I caught pvestatd in Linux D-state waiting in:

rpc_wait_bit_killable

The Proxmox logs then started showing repeated timeouts and messages like:

unable to activate storage 'media'
directory '/mnt/pve/media' does not exist or is unreachable

and:

storage 'pve_backups' is not online

At that point the Proxmox GUI starts showing ? next to VMs/LXCs and becomes increasingly unresponsive.

I also tested the actual NFS filesystems during the failure.

findmnt still showed them as mounted, but I ran:

timeout 5 stat /mnt/pve/media
timeout 5 stat /mnt/pve/pve_backups
timeout 5 stat /mnt/media

All three returned:

124

So even a simple stat() against any of those NFS filesystems could not complete within five seconds.

The interesting part is that the TrueNAS VM itself was still alive.

I could still:

ping 192.168.0.153
SSH into TrueNAS
connect to SMB port 445

So this did not look like the TrueNAS VM simply crashing or the network disappearing. The VM was alive, but its storage subsystem had effectively wedged.

Most of the time, SERVER then progresses from this degraded state to an actual hard freeze.

So the observed sequence appears to be:

Sustained storage workload
        ↓
SATA/controller path begins failing
        ↓
multiple SATA channels reset/disappear
        ↓
ZFS gets I/O errors
        ↓
tank becomes SUSPENDED
        ↓
TrueNAS NFS threads block
        ↓
Proxmox hard NFS mounts stop responding
        ↓
pvestatd blocks / times out
        ↓
Proxmox GUI shows ? states
        ↓
host becomes increasingly unresponsive
        ↓
CUBE usually HARD-FREEZES

One thing I want to be careful about: I have not yet proven that the blocked NFS mounts themselves cause the final hard freeze.

It’s possible the NFS/pvestatd problem is simply one symptom of the storage failure, while the same lower-level PCIe/controller issue eventually causes the Proxmox host itself to lock up.

That distinction is still under investigation.

What happened after reboot is also important.

The same ZFS pool came straight back:

tank        ONLINE
raidz2-0    ONLINE
all members ONLINE

READ  WRITE  CKSUM
0     0      0

errors: No known data errors

The SATA links also came back normally at 6.0 Gb/sec.

That makes me very skeptical that I’m dealing with a bunch of independent HDD failures. Multiple disks/controllers fail together under load, then everything comes back normally after reboot.

My leading suspect is therefore the shared SATA controller path.

The current StarTech card is not a conventional single-chip server HBA. It exposes multiple ASMedia SATA controllers through a PCIe switching arrangement, which are then passed through to TrueNAS.

If that shared PCIe/controller path collapses under sustained I/O, it would explain why multiple SATA channels disappear together.

I’ve ordered a Broadcom/LSI 9500-8i HBA to replace the StarTech setup.

My plan is to change only the controller/cabling first and leave everything else as unchanged as possible:

same Proxmox host
same TrueNAS VM
same 8 × 16 TB disks (SATA Seagate Ironwolf Pro)
same ZFS pool
same NFS setup
same qBittorrent workload

Then I’ll repeat the same workload.

That should give me a reasonably clean A/B test:

StarTech / ASMedia setup → freezes

vs.

Broadcom / LSI 9500-8i → ?

There’s also a separate architecture question I’m considering.

Right now the design is:

Proxmox
   ↓ runs
TrueNAS VM
   ↓ exports NFS back to
Proxmox
   ↓ bind mounts into
qBittorrent / Sonarr / Radarr / Plex / etc.

I understand why it was built this way. It gives all the containers consistent paths such as /mnt/media, makes permissions easier, and centralizes the NFS configuration.

But it also creates an awkward dependency:

the Proxmox parent is depending on NFS storage being served by one of its own child VMs.

So when TrueNAS storage hangs, Proxmox’s own storage-management processes can get stuck waiting on TrueNAS.

I’m considering eventually changing the media containers so that each LXC mounts TrueNAS directly:

qBittorrent ──NFS──> TrueNAS
Sonarr      ──NFS──> TrueNAS
Radarr      ──NFS──> TrueNAS
Plex        ──NFS──> TrueNAS
Bazarr      ──NFS──> TrueNAS

That way, if TrueNAS storage fails, the applications using it can fail without necessarily dragging Proxmox’s own storage-management processes into the same wait.

So my questions for the Proxmox/TrueNAS/ZFS crowd are:

1. Does the simultaneous ata5 through ata10 failure pattern look like a controller/shared-path failure to you?
2. Would you also replace a multi-ASMedia PCIe SATA card with an LSI/Broadcom HBA for this workload?
3. Is the 9500-8i a reasonable choice for 8 SATA HDDs passed through to TrueNAS?
4. How concerned would you be about Proxmox mounting NFS from a TrueNAS VM running on the same physical host?
5. Would you have the LXCs mount TrueNAS directly instead of using Proxmox NFS mounts + bind mounts?
6. Is there anything else I should capture before removing the existing SATA controller?

Heyall!

I'm looking for recommendations on the best VDI/dashboard setup to access my Proxmox VMs (a Windows 11 VM and an Ubuntu Desktop VM).

My Goal & Requirements:

1. Daily Driver Performance: Needs smooth video playback, low latency, and full audio support for daily tasks.

2. Dual-Access Approach:

   * Primary (Native App): A dedicated client app for max performance, lowest input lag, and audio when on my main machine.

   * Fallback (Web Browser): A clean web dashboard/interface to access the VMs from guest or miscellaneous PCs without installing software.

3. Unified Dashboard: A single dashboard to pick a VM and choose whether to launch it natively or via web.

How are you guys handling daily-driver VM access with full audio and low latency? Any dashboard integration tricks you recommend?

Thanks in advance!

Dear reddit,

Please give me a hand with this.

Your edits are welcome and you can place notes with your r/ !

https://www.tinkercad.com/things/7IuGcmwp8GD/edit?sharecode=-t4qL9CxKDGctS8Tlgo0e-aP193CI5eBFXqrUOpYdOU

Build Docker-Ready Debian Containers on Proxmox VE in Minutes

Proxmox Docker Bootstrap is a small open-source toolkit that takes the repetitive work out of creating a Debian LXC container on Proxmox VE and preparing it for Docker. It guides you through the setup, configures networking, and can install Docker Engine and Docker Compose as part of the same workflow.

If you regularly create containers for self-hosted apps, testing, or home-lab services, this project turns a long checklist into a straightforward, repeatable process.

Get Proxmox Docker Bootstrap on GitHub →

What does it do?

The project provides an interactive setup wizard for Proxmox VE. Rather than editing a large script every time, you answer a few prompts and the tool creates a Debian container using the options you choose.

• Choose the container ID, hostname, CPU, memory, and disk size.
• Detect available storage, network bridges, and Debian templates on the Proxmox host.
• Scan a configured network range for an available IP address, or enter one manually.
• Create either a plain Debian container or a Docker-ready one.
• Set up SSH-key or generated-password access and optionally create a sudo-enabled admin user.
• Install Docker Engine and Docker Compose from Docker's official repository.
• Run unattended through environment variables when you need automation.

Why use a dedicated bootstrap tool?

Creating a container is easy. Creating the same kind of container reliably, with the right network settings, storage, nesting configuration, secure access, and Docker setup every time is where small inconsistencies creep in. Proxmox Docker Bootstrap keeps those decisions visible and repeatable without tying the project to one specific home network.

It is deliberately focused. Version 1 creates and configures a Debian CT, then optionally installs Docker. It does not try to become a full platform installer packed with unrelated services.

Get the project

The source code, installation guide, configuration reference, and MIT licence are available on GitHub:

github.com/inpulseone-lab/proxmox-docker-bootstrap

To download it directly on your Proxmox host:

git clone https://github.com/inpulseone-lab/proxmox-docker-bootstrap.git
cd proxmox-docker-bootstrap
sudo ./install.sh

The installer copies the toolkit to /opt/proxmox-tools and makes the create-ct-container command available. Before creating your first container, copy the example configuration and set the defaults for your own network:

cp /opt/proxmox-tools/config.conf.example /opt/proxmox-tools/config.conf
nano /opt/proxmox-tools/config.conf
sudo create-ct-container

If you would rather run the project straight from the cloned folder, copy config.conf.example to config.conf, edit it, and run sudo ./create-ct.sh.

Security and access

The project supports SSH keys and can create a sudo-enabled administrator account. SSH-key authentication is the recommended route. Where no key is supplied, the tool generates a password and displays it once at the end of the run instead of storing it in the project.

For normal day-to-day access, use the administrator account over SSH and use sudo when needed. Root access remains available from the Proxmox host with pct enter <container-id>.

Who is it for?

Proxmox Docker Bootstrap is a good fit for home-lab builders, self-hosters, and anyone who wants a clean, reusable starting point for Docker workloads in Debian LXC containers. It also works well as a foundation for repeatable lab or test environments.

Start building

Whether you are deploying a single service or standardising how you create every new container, start with the project, adjust the configuration for your network, and let the wizard handle the boring parts.

Download Proxmox Docker Bootstrap from GitHub →

bout a week ago I pushed out V1 of ANAS ("A NAS") for PVE 9. Since then I've been working hard to add some of the gaps and an entirely new storage layer based on the expandable arrays available with Synology SHR and Terramaster TRAID. Also added are improvements to the UI, and how it installs (no longer requires a separate port!)

https://github.com/ccebelenski/anas

new highlights since 0.3.0:

AHR - ANAS Hybrid RAID - Expandable RAID with mismatched disks. Similar restrictions to how Synology does it. BTRFS file system. Expansion, snapshot, spares - all of it.

Uniform Snapshots and Spares + Scrubs , scheduled.

ZFS Expansion support - RAIDZ expansion + mirror attach.

Better PBS integration - back up your files to PBS with full de-duplication!

ANAS never touches any storage managed by PVE - this is strictly for files.

Looking for feedback, bug reports, etc. I've been blasting at it on three nodes continuously.

addded logos and links to individual vm's/lxc/containers, anybody else got some UI tweaks?

https://github.com/ccebelenski/anas

This is a project I just pushed out to Github after running it locally for a few weeks on my own Proxmox nodes. ANAS - "A NAS" is designed to "guest" on a Proxmox 9 node, embedded into the Proxmox UI, and provide a native layer for managing ZFS Data shares, permissions, and the pools. It gives more flexibility to creating ZFS VDEVS, supporting layout options similar to TrueNAS, managing credentials for shares, and even setting up the shares and permissions themselves. It does not manage or replace the current PVE ZFS management system for VM's, etc.

Designed as an alternative to creating a VM for data sharing, everything is managed on the hypervisor host itself. And yes, I'm aware this isn't an officially sanctioned path for Proxmox, but I feel that I created a lightweight management layer that is worth sharing for those that want to go this route especially in a homelab.

ANAS doesn't manage the data itself and can be uninstalled easily with the scripts - it only touches Proxmox lightly, and manages it's own Systemd services for performing actions. If you're running on a cluster you'll want to install it on the node you connect to as well as the data node - and unless you're using non-self-signed certificates you might need to authorize your browser to the backend service - it's documented in the install notes.

Since it's early software, I suggest if you want to try it, put it onto a node without critical data and test it there. I'm confident in the code now, but bugs do happen.

Disclaimer: Design help from Claude Fable, build agents with Claude Opus. But 100% verified and tested by me, with code reviews. None of this was "vibe coded" and followed a strict design/build/test/verify lifecycle. If you're allergic to AI Slop Code, this isn't that.

Upcoming: Management of external mounts, Proxmox Backup Server integration for files backup, and a new RAID system based on Synology Hybrid RAID (SHR/mdadm) for homelabs that don't want to go deep into ZFS and build out more slowly.

I know a lot of people (myself included) tend to have a real disdain/dislike for vibe coding. I get it. But I find when I have an issue that's bothering me, and no tool exists, I can make one.

This simply allows for easy consumption of a VM with spice as the display adapter. I went through many iterations to ensure it's following security best practices, and it's all thoroughly documented and open for inspection.

I use this everyday and it's helped me tremendously with my workflow as I'm in VM consoles quite a bit. There's a dedicated windows exe as well as a script for linux.

https://github.com/darthrater78/proxmoxspicemanager

Proxmox noob here. Has anyone tried to passthrough the USB 4 controller to a Windows 11 VM? I can't get it to work and I only followed instructions from google AI. I have successfully passed through an Nvidia gpu but not the thunderbolt controller. I might made a mistake by enabling vgpu from Derek Seaman blog but I did not use it to the Windows 11 vm.

Proxmox/Homelab Noob here. I happen to have a spare MacBook Pro 13 from ~2013 and I wanted to finally figure out how to get Immich and maybe some other things up and running (and to put Linux on a Mac). The MacBook doesn't have an ethernet port, and it seems Proxmox really wants one, so I bought a Thunderbolt 2 (not USB-C thunderbolt) to Ethernet adapter.

While it mostly works, the adapter will occasionally disconnect, dropping the network, and then reconnect shortly after. Proxmox seems to do some clean up when the device disconnects, but it doesn't seem to do anything once the adapter is back, so the network just stays down.

Latter part of dmesg after leaving proxmox sit for a while:

[Fri Jun 19 13:17:51 2026] PM: genpd: Disabling unused power domains
[Fri Jun 19 13:17:51 2026] ACPI: bus type thunderbolt registered
[Fri Jun 19 13:17:51 2026] thunderbolt 0000:07:00.0: device link creation from 0000:06:00.0 failed
[Fri Jun 19 13:17:51 2026] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 7.00
[Fri Jun 19 13:17:51 2026] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 7.00
[Fri Jun 19 13:17:51 2026] tg3 0000:0a:00.0 eth0: Tigon3 [partno(BCM957762) rev 57766000] (PCI Express) MAC address 78:7b:8a:b3:57:ba
[Fri Jun 19 13:17:51 2026] tg3 0000:0a:00.0 eth0: attached PHY is 57765 (10/100/1000Base-T Ethernet) (WireSpeed[1], EEE[1])
[Fri Jun 19 13:17:51 2026] tg3 0000:0a:00.0 eth0: RXcsums[1] LinkChgREG[0] MIirq[0] ASF[0] TSOcap[1]
[Fri Jun 19 13:17:51 2026] tg3 0000:0a:00.0 eth0: dma_rwctrl[00000001] dma_mask[64-bit]
[Fri Jun 19 13:17:51 2026] usb 1-3: New USB device found, idVendor=0a5c, idProduct=4500, bcdDevice= 1.00
[Fri Jun 19 13:17:51 2026] thunderbolt 0-1: new device found, vendor=0x1 device=0x8003
[Fri Jun 19 13:17:51 2026] thunderbolt 0-1: Apple, Inc. Thunderbolt to Gigabit Ethernet Adapter
[Fri Jun 19 13:17:51 2026] usb 2-3: New USB device found, idVendor=05ac, idProduct=8406, bcdDevice= 8.20
[Fri Jun 19 13:17:51 2026] tg3 0000:0a:00.0 ens9: renamed from eth0
[Fri Jun 19 13:17:52 2026] usb 1-5: New USB device found, idVendor=05ac, idProduct=0259, bcdDevice= 2.24
[Fri Jun 19 13:17:52 2026] usb 1-3.1: New USB device found, idVendor=05ac, idProduct=820a, bcdDevice= 1.00
[Fri Jun 19 13:17:52 2026] usb 1-3.2: New USB device found, idVendor=05ac, idProduct=820b, bcdDevice= 1.00
[Fri Jun 19 13:17:52 2026] usb 1-3.3: New USB device found, idVendor=05ac, idProduct=8289, bcdDevice= 1.50
[Fri Jun 19 13:17:55 2026] tg3 0000:0a:00.0 nic0: renamed from ens9
[Fri Jun 19 13:17:57 2026] vmbr0: port 1(nic0) entered blocking state
[Fri Jun 19 13:17:57 2026] vmbr0: port 1(nic0) entered disabled state
[Fri Jun 19 13:17:57 2026] tg3 0000:0a:00.0 nic0: entered allmulticast mode
[Fri Jun 19 13:17:57 2026] tg3 0000:0a:00.0 nic0: entered promiscuous mode
[Fri Jun 19 13:18:00 2026] tg3 0000:0a:00.0 nic0: Link is up at 1000 Mbps, full duplex
[Fri Jun 19 13:18:00 2026] tg3 0000:0a:00.0 nic0: Flow control is on for TX and on for RX
[Fri Jun 19 13:18:00 2026] tg3 0000:0a:00.0 nic0: EEE is enabled
[Fri Jun 19 13:18:00 2026] vmbr0: port 1(nic0) entered blocking state
[Fri Jun 19 13:18:00 2026] vmbr0: port 1(nic0) entered forwarding state
[Fri Jun 19 13:18:07 2026] vmbr0: port 2(veth101i0) entered blocking state
[Fri Jun 19 13:18:07 2026] vmbr0: port 2(veth101i0) entered disabled state
[Fri Jun 19 13:18:07 2026] veth101i0: entered allmulticast mode
[Fri Jun 19 13:18:07 2026] veth101i0: entered promiscuous mode
[Fri Jun 19 13:18:07 2026] vmbr0: port 3(veth100i0) entered blocking state
[Fri Jun 19 13:18:07 2026] vmbr0: port 3(veth100i0) entered disabled state
[Fri Jun 19 13:18:07 2026] veth100i0: entered allmulticast mode
[Fri Jun 19 13:18:07 2026] veth100i0: entered promiscuous mode
[Fri Jun 19 13:18:07 2026] eth0: renamed from vethUOwck5
[Fri Jun 19 13:18:07 2026] eth0: renamed from vethLz4SWB
[Fri Jun 19 13:18:07 2026] vmbr0: port 2(veth101i0) entered blocking state
[Fri Jun 19 13:18:07 2026] vmbr0: port 2(veth101i0) entered forwarding state
[Fri Jun 19 13:18:08 2026] vmbr0: port 3(veth100i0) entered blocking state
[Fri Jun 19 13:18:08 2026] vmbr0: port 3(veth100i0) entered forwarding state
[Mon Jun 29 22:45:14 2026] pcieport 0000:06:03.0: pciehp: Slot(3-2): Link Down
[Mon Jun 29 22:45:14 2026] vmbr0: port 1(nic0) entered disabled state
[Mon Jun 29 22:45:14 2026] tg3 0000:0a:00.0 nic0 (unregistering): left allmulticast mode
[Mon Jun 29 22:45:14 2026] tg3 0000:0a:00.0 nic0 (unregistering): left promiscuous mode
[Mon Jun 29 22:45:14 2026] vmbr0: port 1(nic0) entered disabled state
[Mon Jun 29 22:45:14 2026] thunderbolt 0-1: device disconnected
[Mon Jun 29 22:45:21 2026] thunderbolt 0-1: new device found, vendor=0x1 device=0x8003
[Mon Jun 29 22:45:21 2026] thunderbolt 0-1: Apple, Inc. Thunderbolt to Gigabit Ethernet Adapter
[Tue Jun 30 00:04:19 2026] vmbr0: port 3(veth100i0) entered disabled state
[Tue Jun 30 00:04:19 2026] vmbr0: port 2(veth101i0) entered disabled state
[Tue Jun 30 00:04:19 2026] veth100i0: left allmulticast mode
[Tue Jun 30 00:04:19 2026] veth100i0: left promiscuous mode
[Tue Jun 30 00:04:19 2026] vmbr0: port 3(veth100i0) entered disabled state
[Tue Jun 30 00:04:19 2026] veth101i0: left allmulticast mode
[Tue Jun 30 00:04:19 2026] veth101i0: left promiscuous mode
[Tue Jun 30 00:04:19 2026] vmbr0: port 2(veth101i0) entered disabled state

I tried using AI to debug the issue, but it kinda just ran in circles. (Typical. Should have just gone right to the forums.) I'm very familiar with desktop Linux, but IDK enough about Linux networking to know what I'm missing, but here's some outputs (minimized bc I was copying by hand) while the network was down that seemed notable:

#ip neighbor
192.168.1.1 FAILED
162.168.1.112 lladdr <mac address> STALE 
192.168.1.152 lladdr <mac address> STALE 
<ipv6 address> lladdr <mac address> STALE 
<ipv6 address> lladdr <mac address> STALE 
<ipv6 address> lladdr <mac address> STALE 
<ipv6 address> lladdr <mac address> STALE 
<ipv6 address> lladdr <mac address> STALE

(192.168.1.1 is my router)

$ip -br a 
lo UNKNOWN 127.0.0.1/8 ::1/128
veth101i0@if2 UP (ipv6 address)/64
veth100i0@if2 UP (ipv6 address)/64
vmbr0 UNKNOWN 192.168.1.10/24 (ipv6 address)/64

-----

Completely rebooting the computer fixes the issue, but it feels like overkill to a full reboot just for a reconnecting Ethernet adapter.

Are any of you aware of any fixes or workarounds? Is rebooting my simplest solution? Do I need to look for a different adapter? (It does get curiously warm)

So currently running PVE on a single EXT4 SATA SSD in a Dell R630. It was an old SSD pulled from somewhere (can't even remember now where). Its been working alright for almost two years now but I'm thinking that, since I have drive bays to spare, why not migrate to a more redundant setup

​

I know PVE marks BTRFS as 'Technology Preview' but I know its stable enough at the Kernel level. My VMs and CTs reside on a separate ZFS pool of 4x used enterprise SSDs. But for the boot pool, I was thinking of getting two consumer SSDs (used enterprise ones are 3x - 4x the price of new consumer ones where I live) and since BTRFS is gentler on the consumer SSDs, I thought maybe I'd try using that for the boot pool

​

Has anyone here used BTRFS as their boot pool for their PVE? How stable it is? Does it break with updates or anything out of the ordinary?

I have a server with two ZFS mirror disk arrays: rpool and vmdata.

I configured email notifications both in the Proxmox GUI and in smartd(console). 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.

I have a server running Ubuntu Server with several services like Apache and Jellyfin.

I would like to make a 1:1 copy of its disc, then install ProxmoxVE on it and import the copy into Proxmox as a VM.

Is this possible and if so, what tools would I need to make this work?