Hi, I’m trying to restore and upgrade an old system that has been running as a basic media server for years.
Running V12 on a single 4GB USB as the boot pool.
I can’t upgrade it further as I get a not enough space warning.
So I figured a simple solution is to drop a 16GB drive in, Boot> Pool > Replace.
Drive and poo resilvered successfully and booted fine.
Still had the same issue although the System still saw it as a 16GB drive
What am I missing here?
Or does disk “replace“ not utilise the expanded disk space?
Backup and download your system configuration with any required keys. Do a fresh install on the new boot device with the same version of V12 you are running and then restore the configuration from the file you downloaded.
But still interested if this method “should” work.?
Does it behave the same if I replace a disk in my media pool with a larger drive, is that additional space not available.?
I.e I have a number of different pools.
One of them is simply a single disk last resort backup of cloud storage.
If I need to expand that pool, will this operation not work as I expect?
You can expand data VDEVs easily with drive replacements and then ZFS does the expansion or, current TrueNAS, you have to manually chose ‘expansion’ once all the drives of the data VDEV are replaced. Auto expansion is not automatic and requires intervention with the GUI.
The boot devices are treated differently and it is just easier to do a fresh install and restore the configuration.
