9.2 GUI unresponsive when creating 11disk raidz3 vdev

[framewrangler]

I'm unable to create an 11 disk vdev (with or w/o spares) within the 9.2 GUI. I am able to do so at the CLI without issue. After doing so in the CLI my FreeNas instance is out of sync and not happy. Is that expected behavior? My research shows dated comments supporting the opinion that the CLI is bad news for some tasks for just this reason.

The GUI does permit me to make vdevs in other configurations such as 10disk raid 1+0 and stripes. The GUI simply flashes the progress bar and returns to the creation wizard screen when trying to make the desired 11disk raidz3 vdev. There is no error or dialog indicating that the attempt was made or failed. I've tried 3 different browsers and all have the same behavior.

Any inpt you could provide as to what I'm seeing in the GUI, or if there's a good workaround in the CLI would be helpful and appreciated.

Thanks

 

[dlavigne]

Is this a new installation? If so, can you try the 9.2.1-RC1 and see if the issue persists? If you do try, try dragging the slider as usual in ZFS Volume Manager. If that fails, try the "Manual Setup" button (which is in 9.2.1 but not 9.2.0) and let us know if that fixes the issue.

 

[framewrangler]

Thanks, I will be doing so immediately.

 

[framewrangler]

I've run into some issues booting to the 9.2.1-beta ISO. It may be that initial burn was bad (though I verified it). I'm attempting another DL and burn now.

Yes, this is a new build on new hardware.

 

[framewrangler]

I've confirmed that the problem with the gui/slider remains when using 9.2.1-Beta-Release. Using the manual option within the GUI was successful though there were graphical glitches within Firefox wherein options weren't visible until after a failed submission; ie, required fields (raid type) where invisible until I attempted to complete the "wizard". After the failure to complete the wizard the options then showed up to select raid type.

Also, when configuring disks as "spares" using the manual option there was no clear indication that this was functional. For example, "zpool status" did not show the spares appended to this new zpool. Maybe there is a global spare versus pool specific spare that is confusing me. I'll continue to review. After observing this I added the spares to the pool using the traditional GUI interface without issue. Zpool status now shows the spares under the pool in question.

Code:

[root@freenas] ~# zpool status
  pool: aaa
state: ONLINE
  scan: none requested
config:
 
        NAME                                            STATE    READ WRITE CKSUM
        aaa                                            ONLINE      0    0    0
          raidz3-0                                      ONLINE      0    0    0
            gptid/fffe94e1-890a-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/0096a9f2-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/012f940e-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/01c957bf-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/0262ad73-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/02fda9af-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/0399d385-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/0433eb1d-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/04c780d9-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/0563212c-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
            gptid/05fd5dda-890b-11e3-95d2-90e2ba40db94  ONLINE      0    0    0
        spares
          gptid/6c96dc92-890b-11e3-95d2-90e2ba40db94    AVAIL
          gptid/92f9e4e8-890b-11e3-95d2-90e2ba40db94    AVAIL
 
errors: No known data errors
[root@freenas] ~#

I assume at this point I should revert to 9.1.1 in order to get this box into production, assuming the problem doesn't exist there as well.

One final note, the 9.2.1-Beta-Release would not let me configure my nics from the console. The console appeared functional and all menus were responsive, but the changes never impacted my nics. DHCP was ever-present and my static configs were ignored. I tried disconnecting cables, using the reset option, and even resetting webgui to defaults. There was no change in behavior and the console was unable to administer my nics.

 

[framewrangler]

I've confirmed that the RC build does in fact fix this issue. No problems observed.