PsychoWards

This and if you server is not reachable (maintenance, updates, ISP problem, ISP forced disconnecteds and reconnects, power outage, a wrong manipulation on the server, house keeper unplugging the server to plug in the vacuum cleaner etc...), you are not going to get any mails and this becomes problematic with missed invoices and other important mails. Therefore while it certainly is a fun and interesting topic, I would only use it for emails which you don't mind not receiving, but I would not use it for important things, but that's up for everybody to decide themselves.

You need to login into Truenas, go to storage -> Manage Devices -> select your pool and then the first drive. On the right side on the Disk Info part press "Edit" and there you have the possibility to set the HDD Standby and/or Advanced Power Management. Under Advanced Power Management everything from Level 1 to 127 will spin down the drive, from 128 to 254 will not spin down the drive. You have to do this for every HDD. I don't know how Hexos is reacting to this and which side effect it can have, also for other people reading this, spinning down drives is generally not recommended because the spin ups are putting wear on the drives, and drives are vulnerable during spin ups. When drives are spinning there is an air cushion which is keeping the head of the disks, while this is not the case during a spin up and a head crash can occur. Also when leaving a drive sitting without spinning it can have a negative impact on the lubrication of the bearing. Also make sure that the drive doesn't not cool down to much, this is especially import in the winter if the server is sitting in a cellar or basement where the air temperature can drop and this can also cool down your drive significantly, depending on your setup. There have been plenty of perfectly working drives without issues, which did not recover from a spin up. So be warned, that it might shorten the lifespan of a drive. Also you might want to look into enabling the different C-States in the Bios, this can also save a significant amount of energy.

Hey, Concerning the RAM, go with ECC modules. Just a quick heads-up, Hexos is using ZFS, which is different then raid and has a different naming scheme. For example the RAID1 in ZFS is called mirrored, RaidZ1 in ZFS would be similar to Raid5, RaidZ2 would be similar to Raid6. Therefor to not get confused between Raid1 (ZFS mirrored) and ZFS RaidZ1 (Raid5) I will use the ZFS terms. Mirrored boot drive is the way to go with the current version of Hexos. Since pool import is not supported at the moment, if you only have 1 boot drive and if your boot drive bites the dust, there is currently no way to use hexos again without loosing all your data. You would need to install truenas and use truenas until Hexos supports pool import. I am using WD Red Plus and Seagate Ironwolf drives, they are meant for NAS and should last longer in theory. However a lot of people are using desktop grade drives without much issue. My only recommendation would be to make sure you get CMR drives and not SMR drives (meaning don't buy for example normal WD Red drives, either use the Red Plus or Red Pro for those) If you are only using it as a NAS and don't want to host a lot of other things and VMs, 1 CPU would be more than enough, this will save on energy. Additionally, you can also activate some of the C-States in the BIOS to save even more energy on idling and you can disable not used components (audio chip on consumer grad HW, onboard NICs if an external NIC is used etc...) Stopping drives from spinning would also save some energy, however this is generally not recommended since it increases the wear on the drives, spinning drives up is one of the more frequent cases where a drive can die.

No, you cannot change from a RaidZ1 to a RaidZ2, this is defined once during the creation of the pool, but changing it requires to destroy and recreate the pool with RaidZ2, which will wipe all the data from the disks. If you want to have a RaidZ2 you either need to wait until Hexos supports it or create it manually in truenas and live with possible side effects in Hexos or ditch Hexos for the time being and switch to a truenas installation and migrate back to Hexos once pool migration because available some time after version 1.0.

At least for Truenas, you can backup your config and store it wherever you like. In the case of a boot drive failure, you would just reinstall truenas, reimport the config and you are good to go, no need to do an image of the boot drive itself. This will not work with hexos, since hexos will create new pools and wipe the drives. But using Truenas instead would be an option to recover the data from the drives until importing pools is possible in hexos.

I cannot help you with the Immich migration, however currently it's not possible to create a pool in Hexos with 1 single drive, you need at least 2 drives so that Hexos can create at least a mirror. If, however you want to expand your pool in the future you need at least 3 drives during the creation. Those are the current limitations of hexos, this will however change in the future. So your current plan of sacrificing 1 ssd for the pool creation will not work.

Are those WD Red or Red Plus or Red Pro? Simple WD Red are not ideal for a NAS, despite WD marketing them as NAS drives, since they a SMR an not CMR drives, the performance can suffer. Other than that, if you can spare the extra capacity lost go with a RaidZ2, meaning you will have 8TB storage and you can lose 2 drives without losing any data. However, at the moment Hexos will always create a RaidZ1 meaning you can only lose 1 drive but have 10TB storage.

And Vaultwarden if that's possible

How do you want to do this? There is no reliable way to measure the consumption of most of the parts, some parts are not even read be the motherboard (HDD consumption, PSU losses etc.) Your best bet is going to buy a cheap socket power meter, this does it way more reliable, you know how much is actually pulled from the socket and depending on the model you can connect it to Home Assistant for example.

@The Callorhinchus I'm not sure if you got an invite already but @Adster mentioned in one of the categories, which you see after you got the invitation, that the everything is running fine when installing Hexos as a VM in Promox, so at least there's that. I guess most people using proxmox just use truenas directly, the Hexos target audience probably doesn't want or need the increased complexity/possibilities? I'll use proxmox since Hexos currently doesn't support all the applications which I need and I will spin up dockers in a VM in proxmox.

I'm interested in this as well, is it better to use Proxmox for the VM stuff and use Hexos as a NAS only or should we just use Hexos for both the storage and VMs?

Yes please, this should be done rather sooner than later.