brandman

Thanks for the reply @PsychoWards Maybe I will remove the two disks for OS from the RAID controller and plug them directly to the MB, maybe then I could passthrough the RAID controller without issues to the VM (may be worth a try sometime in the future) The only thing which would be "not solved" - what do I do with the 4 SSDs running as Proxmox storage for the VMs and the containers? Connect them directly too? I need to count the free SATA ports first 😄 As I remember correctly from another topic in this forum, it should be possible to use SSD cache in HexOS in a upcoming release

All drives are connected to the RAID controller: 2 of the as RAID 1 for the OS (Proxmox) 4 of them as RAID 10 for Storage (for all virtual machines and containers) 2 of them as RAID 1 for testing purposes as "SSD cache" 4 of them as RAID 5 + 1 as hotspare for testing purposes as "fast storage" - all SSDs 4 of them as RAID 5 + 1 as Hotspare for testing purposes as "slow storage" - spinning rust 😉 maybe more to come in the future ... 🙂 Everything which is for testing purposes is directly mounted to the VM (Proxmox does see this virtual disks but is not using it) If I don't configure them in the RAID controller (ether as RAID or as standalone) I am not able to do anything with them - Proxmox does not see them, they don't appear anywhere, like there would be nothing- so I need to configure all my physical drives first to create virtual drives to do anything with them 😄 This is the main reason I am "complaining" about HexOS asking for more drives to create a pool - all redundancy is covered by the RAID controller - no need for HexOS or TrueNAS to create any kind of pool with multiple disks ... There are some free SATA ports on my MB, but to be honest, I don't really want to connect the storage there Due to the fact everything important is running (not yet virtualized) there no rush for me, so I will patiently wait for the upcoming release of Hex. Thanks guys for all the tips and comments on that! This is really very much appreciated, talking to guys like you

@ubergeek I am running all my infrastructure on Proxmox. Adding the RAID controller to the VM directly (as PsychoWards proposed) will cause my server to crash ... Only a reboot will help - I am assuming it's because I am using the RAID to control the disks on which Proxmox is installed.

Hi PsychoWords Thank you for your reply. I am aware that the combination of ZFS and HW-RAID is not the best solution. Passing the RAID controller to the VM did not work for me due to my current setup. I also need to configure every disk first in the Controller, otherwise you can't find it within proxmox as a attached disk. The best way would be to be able to add a single disk to HexOS without using ZFS 🙂

While testing if HexOS could replace most of my current used infrastructure like NAS and so on, I found something, which is bothering me... As by now you can only create a pool with at least two disks, but what if I have only one? I am using HexOS virtualized on a Host with multiple disks, all of them managed by RAID - so I only have "one" disk, even if there are many physical disk behind this one virtual disk. Not sure if this will be "fixed" in the upcoming release in Q2 - see thte "HexOS Q1 Status Update" - https://hexos.com/blog/hexos-q1-status-update As by now my only way to create pools is not to use the HW-RAID, which I would prefer.

Forgot something to add to the list: Use SSD as Cache

Hi all First of all, thank you and good job so far! Just started with the beta and gathered some ideas for features below: NFS Shares Quota for Folders (Backup to external Disk) HexOS Dashboard which can be accessed locally (without a need for using deck) Scheduled Tasks Integration to use HexOS as a Proxmox Backup Server GPU Acceleration That's for now, maybe I'll find some more ideas to include in the software.