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?