mirrored USB drives (boot) upgrade

[Wim Mistiaen]

So I upgraded my old 2x8Gb drives yesterday to 2x 64Gb drives. The way I did it was as follows:

1) remove first 8Gb USB key
2) insert first 64Gb key
3) detach 8Gb drive from pool
4) attach 64Gb drive from pool
5) wait for resilver
6) remove second 8Gb USB key
7) insert second 64Gb key
8) detach 8Gb drive from pool
9) attach 64Gb drive from pool

After this, i expected to see 64Gb for my pool, however, I still see the old 8Gb size... In the disks section, the new USB drives are correctly listed as 64Gb.

What did i do wrong and how can i correct this?

kind of related question, if i end up reinstalling freenas, and restoring the configuration, do i lose anything? or is litterally everything encompassed in the backup file?

 

[Chris Moore]

Did you do all this detach and attach action from the command line? If you did, that was your mistake. There is a menu option for it in the GUI and the GUI goes through the 'middleware' which handles re-partitioning the new device, which you didn't get if you did this from the command line.

 

[Wim Mistiaen]

I did this through the new GUI, and I did check the "Use all disk space" for both disks I attached.

 

[Chris Moore]

I did this through the new GUI, and I did check the "Use all disk space" for both disks I attached.

It might be a bug in the middleware. Would you file a bug report?

 

[sretalla]

Did you reboot? perhaps it's necessary to get it to update the pool size just for the boot pool.

 

[Mlovelace]

I suspect you didn't turn on autoexpand, as it's disabled on the boot pool by default.

Code:

root@CLNAS02:~ # zpool get autoexpand
NAME          PROPERTY    VALUE   SOURCE
freenas-boot  autoexpand  off     default
tank          autoexpand  on      local
root@CLNAS02:~ #
root@CLNAS02:~ # zpool set autoexpand=on freenas-boot
root@CLNAS02:~ # zpool get autoexpand
NAME          PROPERTY    VALUE   SOURCE
freenas-boot  autoexpand  on      local
tank          autoexpand  on      local

 

[Wim Mistiaen]

Did you reboot? perhaps it's necessary to get it to update the pool size just for the boot pool.

that indeed solved it. yay!

It might be a bug in the middleware. Would you file a bug report?

not sure if it's a bug, since the reboot solved it, but https://jira.ixsystems.com/browse/NAS-101562