Update on power use . OMV 7. At idle after a boot, 22 to 33 watts. I used mergerfs with the 2 drives. During my backup tests, all the data went to one of the drives. (As expected.) I told OMV to balance the volume, which got both drives going. I saw around 44 watts at peak. (Measure with a Fluke clamp meter so maybe not the most accurate measurements. Consider them a ballpark.) Here's the top of the Jonsbo case:

I was able to update the OMV 7 image without a problem this time. Not sure why I had a hiccup the first time thtough, So I decide to proceed. I installed a 14TB drive. I securely wiped the drive twice to exercise it and make sure things were working. No problem. I put a EXT4 on the drive. Next I mounted the drive. At this point OMV wanted me to commit pending configuration changes. When I did this, a red splash appeared with a very long message that was longer than the box. Started with "openmediavault 500 internal server error failed to execute command 'export". I attempted this a few times with the same result. Same after a reboot. Apparently unable to update the configuration to mount my single drive. I'm not a deep Linux person obviously. I'm runnign an Unraid server, a Ubuntu Plex server, & I've built some Raspbery Pi projects that do different things. Maybe this small NAS path I've chosen with a CM4 isn't for me. I don't think it's the board - it's fine. I had not planned to use OMV 7 anyway, but it was an easy way to get started. Now I want to install the Desktop image. Apparently this isn't easy with a bootable system on the CM4 eMMC. I've ordered a CM4 carrier board but not here yet. So I booted in live mode, then used dd to erase the eMMC. I was then able to install the Desktop image on the eMMC. apt update and apt upgrade go without any issues. Installed nano without issue. Installed gparted. The installation seemed to work, but I lost control of the desktop. Rebooted and it was back, with a new gparted icon in the menu. Doesn't run. No messages. Puzzling for this linux nube. I've paused for now so I can think about this project. I have to decide if it would be wiser to get an N100 motherboard and go that route.

Does the same apply to the OMV 7 image? This is what I tried to update first and didn't have much luck. I do see that the number of update packages available has changed. Seems like it was 60 or more after the initial installation. Today it shows 50.

The hardware FAQ could use an update, because it indicates RPIBOOT can be used: Q. Is there a minimum CM4 bootloader version required by the Axzez Interceptor Carrier Board? A. The only requirement is that you have the ability to boot via USB. This capability was released with the RPi4 bootloader eeprom version 2020-12-14. To install this (or newer) bootloader, please follow the instructions here to setup and build "rpiboot". Then follow the instructions here to flash the latest or desired eeprom version. We recommend the "BOOT_ORDER=0xf215" for setting up our provided operating system. This should mention that a real CM4/CM5 carrier board is needed for these things. I was able to image a USB stick on a Raspberry Pi 3, and it worked. I loaded OMV. Doing updates after that install didn't seem to go very well, but it's running. Maybe I'll try another OS.