Proxmox is really good with all types of storage and I have used it as a dedicated NAS appliance many times. I have used dedicated NAS devices. I have also used shared SAN storage and NFS, iSCSI, and also ZFS. Ceph is my current shared storage provider in the home lab where I am using local drives aggregated across 5 Proxmox nodes. One of the most popular home lab and self-hosting configurations is to install Proxmox on the server, then create a TrueNAS VM. You then pass your storage controller through and let TrueNAS handle everything with your file storage. That is why a project I saw posted called ANAS, which is short for “A NAS” got my attention. Let’s see what this project is and why it may change how you provision storage in your self-hosted environment.
The storage management gap in Proxmox
Proxmox VE Server itself has really good storage support. You can attach NFS storage, SMB/CIFS, iSCSI, ZFS, LVM, directory storage, Ceph, CephFS, and even other storage backends. So you can take just about any kind of storage and use it in Proxmox to make it available for VMs, containers, ISO images, backups, things like templates, and other storage needs.
So, the point we are trying to make here is that Proxmox is great at consuming storage, but not so great at managing and creating storage natively in Proxmox. So, underneath Proxmox is Debian and it is of course Linux. So it has strong support for the storage types that we have already mentioned. So, the underlying OS can easily provide storage management using native Linux tools, but this isn’t exposed in a really easy way from the Proxmox web UI.
What is ANAS?
That is exactly the gap that the ANAS project is trying to add to the Proxmox VE Server experience. Is this a fork of Proxmox? No. It installs on top of the stock Proxmox VE Server node installation and adds native ExtJS panels to the existing PVE interface.

The developer describes the approach here to the way that Ceph functionality is implemented in Proxmox natively. I like this and I am sure you will too since the installation doesn’t have you navigate to some different web interface to manage the “storage” features that it adds. Instead ANAS is exposed to the existing Proxmox web interface on port 8006 using your same login to Proxmox itself.
I like this aspect a lot since we don’t have to worry about another management plane to have to secure and configure.
Now, I saw some poking fun on Reddit at the name of the project, which I will leave this up to you to decide if there might be a better name for adding storage to your server 😁
I think this changes the usual Proxmox plus TrueNAS setup
One of the first architectures many home lab users discover is Proxmox plus TrueNAS. If you read across various forums, blogs, Reddit, and elsewhere, you will find ones talking about many different ways to build this out. But, one common way to do it looks similar to this:
- Proxmox runs on the bare-metal server
- TrueNAS runs as a VM
- An HBA or storage controller is passed directly through to the TrueNAS VM
- TrueNAS owns the disks and storage pools
- It then exports SMB, NFS, or iSCSI storage back to clients on the network

Many have used this architecture above and it can work just fine. This is good especially if you want the TrueNAS management experience and its ecosystem of tools, integrations, etc. But there are tradeoffs to doing it this way. Now, my storage needs a VM and PCI passthrough becomes part of the design of your storage. Also, this can get you into a potential “chicken and egg” scenario where your storage can’t start due to the VM being down and the VM is down due to storage not starting, etc.
So, again, ANAS makes this possibly a simpler solution. What if you could just use the Proxmox node to manage those disks and provide those NAS services directly. This is a much simpler design and keeps you outside of dependency issues.
Installing ANAS in Proxmox
The process to install ANAS in Proxmox is actually pretty straightforward. The first thing you need to do is visit the GitHub repository for the project and download the tarball. I did this on my Proxmox host with the command below. Just replace the release URL for the current tar.gz file:
wget https://github.com/ccebelenski/anas/releases/download/v0.3.1/anas-0.3.1.tar.gz

Then, the next step is to untar the release file on your Proxmox host which creates the directory. Then we run the installer.
tar xzf anas-<version>.tar.gz
cd anas-<version>
./install.sh --install-deps

Below, we are running the ./install.sh script with the –install-deps flag. What does this install? Some of the ANAS features depend on packages that Proxmox does not normally install. These include things like Samba, nfs-kernel-server, mdadm, Btrfs tools, ACL utilities, and the Linux LIO iSCSI tooling. ANAS also needs to have Node.js 20 or newer installed and ZFS 2.2 or newer.
Also, according to the documentation, the installer does a preflight check before it changes the node. It installs dependencies, creates backups, installs ANAS, performs health checks, and then it integrates with the Proxmox interface. If part of that process fails, the installer is supposed to roll the changes back.

After running the installation, we see the directive that the ANAS package has been successfully installed and directs us to manage just using the normal web UI. Also to note, to uninstall you can run the uninstall.sh script provided in the extracted tarball.

Viewing the ANAS management in Proxmox
Now when I refreshed the Proxmox web UI, I see the ANAS management menu under the Proxmox node, not Datacenter management. Already, I like the looks of this. It definitely feels like a native part of the Proxmox web interface. If I didn’t know, I would say this is a new feature in a new version of Proxmox due to how well it integrates.

Creating Hybrid RAID using ANAS
Since I am testing this inside a nested Proxmox VE Server in Proxmox, I have added (3) 50 GB QEMU virtual disks to the Proxmox VE Server. Let’s now look at the process to create a hybrid RAID array using ANAS in Proxmox. Navigate to ANAS > Hybrid RAID > Create.

You will see your virtual disks that are available to the system for creating a new RAID array. Here you can see the (3) 50 GB QEMU disks that I had added.

You simply have to “drag and drop” the disks over to the right for the

Be sure to name the Pool. I didn’t see this at first and couldn’t figure out why the Create Pool button was greyed out.

It will ask you to confirm the creation of the pool and destroy the data on the disks.

Pool is created and it begins synchronizing.

The hybrid array is healthy and the synchronization is complete.

Awesome features for home lab
The more I used this in testing in my home lab, the more excited I got about this project. The capabilities that it gives you as part of the native Proxmox interface are really great I think. Especially for ones that don’t want to mess with the complexity of having to install TrueNAS as a VM and then configure passthrough, etc.
Once you have your RAID array configured, you can do really cool things like create SMB shares on your Proxmox Server for use as a file server perhaps in your environment.

You can also make Proxmox into its own iSCSI target with the ANAS iSCSI target configuration. You can configure a target that fronts your storage that you create in ANAS. Pretty cool!

Replication is a great addition here as well. You can setup replication targets and then setup a replication schedule to replicate your data to another appliance, etc.

Also, snapshotting is built in as well. You can setup schedules when you want to create a snapshot of your data for rollback purposes.

Hybrid RAID with ANAS
One of the cool things about ANAS as well is the ability to implement hybrid RAID arrays. It has its own hybrid RAID called AHR or ANAS Hybrid RAID. The easiest way I can think about it is it is similar to other vendors like Synology or Terramaster, or others that allow you to use mixed size drives.
I think this is great for home lab as we may start out with a couple of 4TB drives and then we purchase an 8TB drive later on. So, you don’t necessarily have to worry about that mismatch there in sizing between your various drives in the hybrid RAID pool. It intelligently handles that as part of building out the RAID array.
It does this by dividing the disks into size-matched “bands” it calls it. Each band uses Linux md RAID5 or RAID6 for redundancy. Then it uses LVM to concatenate those bands and Btrfs provides the filessystem on top of that. It also provides the checksums and scrub capabilities.
PBS integration with ANAS
One of the other VERY cool features here is that ANAS integrates in with Proxmox Backup Server. Normally when we think about PBS we are thinking about backing up virtual machines or LXC containers. ANAS allows you to extend that to the NAS data itself. Backup tasks can protect file data like datasets, shares, and other paths. It can also protect block storage like iSCSI LUNs.
This allows you to have backups and take advantage of all the PBS features like deduplication, encryption, retention, and pruning. I think this integration makes ANAS even more powerful since storing your data is only half of the battle. Backing it up is the other half.

Wrapping up
Many of the community projects that I try out, I brace myself to be disappointed either by a lack of features or features that just aren’t implemented very well. ANAS really blew me away in how well it works and just how easy it makes managing storage inside of Proxmox. I think this is a really great add on for Proxmox in your home lab and arguably may be a better way to manage your storage more efficiently than installing TrueNAS inside a virtual machine and having to configure passthrough etc. How about you? Have you heard about or tried out ANAS as of yet?
Google is updating how articles are shown. Don’t miss our leading home lab and tech content, written by humans, by setting Virtualization Howto as a preferred source.

Nice article! what if i want to use an external DAS like a Terramaster D4-320, would if work well? any depencency or configuration clash that’s not reccomended? Thank you!
Michele,
Thanks for the comment! I don’t think there would be an issue with using a DAS unit and have ANAS manage the storage. The key here would be to make sure the Terramaster could pass through the disks as JBOD (like HBA or IT mode) to ANAS so it could manage it natively. You wouldn’t want the Terramaster to have its own RAID on top. This would be for ANAS to configure on the passed through disks 👍 Let me know if this helps. Thanks Michele.
Brandon
Very interesting project. My biggest concern is the fact that on this software Claude has done 442 commits of code and would you really trust that this has all been checked by an experienced dev before using as important infrastructure with network access etc ?
Mark,
I definitely agree. This is always one of those questions of trust and making sure you do your due diligence with security scans and such. Unfortunately, I think this is the reality of where we are today. I will say that I think the project is definitely polished and I don’t see some of the weird issues with this that I have seen with ones developing who aren’t really developers. So far, it looks good in my testing and haven’t seen any issues that have worried me.
Brandon
I am taking this for a spin. Thanks for passing this along Brandon.
I wish the GUI was a bit more polished. Sure, it’s nice that it’s integrated with the Proxmox UI (I’m loving this). However, would be nice for some more bells and whistles such as a progress indicator for replication tasks.
Chris,
Great feedback here! I think this is definitely a project to watch due to the native integration with the interface and things like you are mentioning will probably come with time. But great to see the feedback and that others are trying it out. It is definitely one that I will be keeping a close watch on myself.
Cheers,
Brandon
What if I export my PVE-Pool and import it to ANAS. Can I then still use the pool as if it would belong to PVE? So that I have all the ANAS-features but also run LXC and VMs in PVE on that same pool like before?
Robert,
I am not sure on those types of operations and the integrations there. I haven’t tested that aspect of the solution, but it definitely sounds like it would be doable. Let me know if you have a chance to try this out in your lab. I may spin up a lab environment to test more of these types of operations with ANAS.
Brandon
I did something similar. I had no issue importing a pool from TrueNAS into ANAS. Gotta assume the same would be true for a PVE-Pool (assuming you’re talking about ZFS).
P.S. Should have read your question in more detail. I would assume to use the ANAS pool with PVE, you’d have to expose it somehow such as through iSCSI or NFS. Now I’m intrigued and am also wondering if PVE will natively see the ANAS pool. I’m guessing not, bit hopefully I’m wrong.
Very interesting as well.
Brandon
Chris,
Really appreciate your insights and testing here. Thanks for sharing!
Brandon
I took a different approach to add NAS to PVE. I just install CasaOS directly onto PVE 9.2. CasaOS is a NAS with Docker support. It comes with an App Store for popular Docker apps. The best feature I get from CasaOS is the File Manager with root access which means I have a GUI file manager that I can see and operate on all files on PVE.
Very cool. That is a unique approach. I haven’t tried doing that but I can see where that has value. I am excited to see what is going to come along for Proxmox in the next few months. There are so many developments and momentum behind the platform. Exciting times!
Brandon
Similar to CasaOS, you might want to look into ZimaOS as well. I tried both and like CasaOS more but that is just a personal choice. Have fun with these NAS apps.
Good morning,
sorry for jumping in …
Did I understand correctly – you installed case OS directly on Proxmox VE, not a VM ?
Were you able to use a LVM or ZFS pool on PVE for defining SMB shares ?
And were you able to successfully use these SMB shares from a Windows PC ?
At the moment, I am trying to find a “good” way of running a NAS directly on the Proxmox VE.
With the ANAS approach, I am running into “connection refused” problems.
So I am looking for an alternative way
Looking forward hearing from your experience
Regards, Gerhard
Yes, I installed CasaOS directly on PVE 9.2. Through CasaOS File Manager, I can create SMB shares for all volumes and directories I can see. Accessing the shared SMB is tricky on PC though. By default. Windows 11 disables insecure guest logon which means you can’t access the PVE shared even you have log into PVE successfully. You must edit local group policy to enable insecured guest logons. Once this is done, accessing PVE share would be straight forward. However, my CasaOS can’t see the PVE logical volume (LVM). I do have a physical PVE volume where I store all iso files. CasaOS sees this physical volume just fine so I can share it with my PC. I found the following regarding CasaOS and LVM. “Yes, CasaOS running on Proxmox VE (PVE) 9.2 can access storage, but direct recognition of LVM (Logical Volume Manager) is often problematic due to how the operating system handles virtual disks.
LVM Recognition Issues: Users report that CasaOS frequently fails to detect storage volumes correctly when the underlying Ubuntu Server or Debian OS uses default LVM configurations, often showing incorrect total storage or failing to mount drives entirely.
Workarounds: To ensure reliable access, it is recommended to either disable LVM during the host OS installation (using standard partitions) or manually expand the logical volume using commands like sudo lvextend -l +100%FREE -r /dev/mapper/ubuntu–vg-ubuntu–lv to allow CasaOS to recognize the full space.
PVE 9.2 Specifics: While PVE 9.2 introduces new snapshot features for LVM thick provisioning, CasaOS typically requires the storage to be presented as a standard mountable filesystem or via direct drive passthrough (ZFS or standard ext4/xfs) rather than relying on the guest OS’s ability to parse complex LVM structures.”
I hope above helps.
Great write up. One thing that comes to my mind – would it be possible to import a btrfs drives created in OMV? OMV is great, it’s set and forget approach is nice but it adds another layer like TrueNAS to simple task like SMB/NFS shares.
Good morning!
Great writing … thanks to you I have found the ANAS project.
Just managed to install it on my new Proxmox VE I want to build my homelab.
Worked fine, great GUI.
It was easy to publish an SMB share on a ZFS pool.
When trying to access the SBM share from a Windows computer, the connection is always refused.
I have tried to add a linux user, a PAM user, tried root, or allowed access without authentication.
No way – connection is always refused.
Have you ever managed to successfully connect to an SMB share from ANAS on a windows computer ?
Keep up with your great writing,
Regards
Gerhard
Gerhard,
That is awesome that you have been trying out ANAS. I think it is a great solution. I didn’t not test out the SMB share unfortunately. But I will try this out in my lab and see what I get there as well.
Brandon
To resolve PC blocking of your Linux Samba share, you must address protocol compatibility and security policy restrictions on the Windows client side.
Enable Insecure Guest Logons
If your Samba share allows guest access, modern Windows versions (10/11) block it by default. You can enable this via the Group Policy Editor (gpedit.msc):
Navigate to Computer Configuration > Administrative Templates > Network > Lanman Workstation.
Enable the policy Enable insecure guest logons.
Alternatively, use the Registry Editor to set AllowInsecureGuestAuth to 1 under HKLM\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters.