Moving boot pool to existing pool?

Given how little space is needed for the boot pool, I’d like to move it to my existing 2x512GB mirrored NVMe “apps” pool and be able to yank 2 aging SSDs from my case. The web UI seems to give me the option to relocate it in System > Advanced > Storage Settings > System Dataset Pool, but I’m wary… is it that easy to move it over on a running system, or is there a more specific workflow? I have always labored under the impression that the boot pool needed to be standalone, so I’m wanting to be extra cautious to avoid borking my system and also to avoid losing any data on my apps pool.

I found an RTFM for Core 13.0 on this but nothing for 25.10 (this is the closest thing I found). Can anyone confirm that selecting an existing pool for the boot pool is safe and sane? Given the warning dialog that spawns when going in here, I want to be triple sure this is the correct approach.

The boot pool has to be on its own physical device.

Adding: system dataset != boot pool. Moving the system dataset to your storage pool is recommended, but it will not move the boot device.

1 Like

You don’t need a Mirror boot-pool, most likely. You can’t remove the second device from the Mirror in the GUI but you can use the CLI, or you download a backup of your system configuration, do a a fresh install on a single boot device and reload your configuration.

Command line would be something like zpool detach boot-pool SDB This would detach drive SDB from the Mirror

1 Like