SOLVED Boot Mirror Enlargement During Transition From Thumbdrives to SSD's

Joined
Jul 7, 2018
Messages
4
Big picture: Wanted to migrate boot mirror off USB thumbdrives to Samsung SSD 870 EVO 500GB SSD's on an existing, well-running TrueNAS (12.0-U8.1 and later 13.0-Release) machine, but resulting mirror cannot seem to be enlarged to match SSD capacity.

Process Used:
* Initially used "Replace" to substitute SSD's for thumbdrives in the mirror, one at a time - this resulted in a 16GB SSD-based mirror. This was expected.
* "Detached" one SSD from the new mirror
* ICW remaining singleton boot drive, used "Attach" with "Use all disk space" option checked, to rebuild the mirror using the drive I just detached (which, as expected, was available in the member disk dropdown and said to be 465.76GB)
* I then repeated this detach/add/Use all disk space process with the second SSD

Based on official documentation and web research, I expected this process (in particularly, executing "Use all disk space" on BOTH drives) would result in enlargement of the space available to the mirrored pool matching the capacity of these SSD's, however, Stats/Settings continues to report:

Boot Pool Condition: ONLINE
Size: 14.38 GiB
Used: 8.91 GiB

I have also repeated the above processes but used "Wipe" on each SSD before reattaching it to the mirror - but still ended up with 16GB mirror capacity. I've also reboot the machine, and even upgraded to 13.0-Release, to no avail.

For what it's worth, the mirror is said to be composed of "/dev/ada3p2" and "/dev/ada4p2" - I mention this in the event the "p2" is significant....

I know one option I've seen advocated might be to reinstall TrueNAS from scratch and reload a saved configuration. That said, I'd rather execute the least risky approach available although my outcomes appear inconsistent with documentation.

Thank you for any suggestions.
 

sretalla

Powered by Neutrality
Moderator
Joined
Jan 1, 2016
Messages
9,703
Have a look here:

zpool get autoexpand freenas-boot

The result is probably that it's off...

Super old post, but this suggests one option:

The other one is to set the autoexpand to on
 
Joined
Jul 7, 2018
Messages
4
Subsequent to submitting the above post, I finally discovered CLI commands (as root) which resolved my situation:

zpool status [displayed name of my boot mirror - freenas-boot, and component hardware, in my case ada3p2 and ada4p2

zpool status freenas-boot
[displayed mirror size and utilization, and space available for expansion]
zpool set autoexpand=on freenas-boot
zpool online -e freenas-boot ada3p2 [where ada3p2 is my first mirrored SSD drive]
zpool online -e freenas-boot ada4p2 [where ada4p2 is my second mirrored SSD drive]
zpool status freenas-boot [updated to show totality of SSD space has been allocated to the boot mirror]

I don't understand why this process isn't either 1) Handled by the GUI or 2) Described in official documentation, but I wish it had been.

Kudos to Jan-Philip Gehrcke and additional details can be found on https://gehrcke.de/2019/10/freenas-...eplace-the-usb-boot-device-with-a-larger-one/
 
Joined
Jul 7, 2018
Messages
4
Have a look here:

zpool get autoexpand freenas-boot

The result is probably that it's off...

Super old post, but this suggests one option:

The other one is to set the autoexpand to on
Thank you. I just discovered the solution and have submitted a "reply" with CLI details.
 
Top