Cannot select Volumes/Datasets in webgui (therefore cannot detach volumes)

[Ramy]

When I click on something in the tree menu of the webgui, it does what I would expect. However, when I attempt to select a volume or dataset in the other area, nothing happens. It doesn't turn blue, it doesn't come up with options for scrub/create dataset/detach. When I double click, it expands/collapses the tree of volumes, but nothing else shows up. Also, there seems to be an invisible dataset (When I try to create a dataset with a certain name, it says that path already exists, even though it doesn't show up as a dataset.)

 

[SweetAndLow]

Hardware and freenas version? I usually use the menu across the top but the side to access my pool.

 

[Ramy]

Hardware and freenas version? I usually use the menu across the top but the side to access my pool.

The hardware is a Supermicro X10SLM+-F, an i3 4160, 16gb of crucial ECC DDR3 (the supported kind), and 6x2tb WD Red drives. I am running the latest stable release of freenas 9.3. Which menu are you referring to? Also, I have attached some screenshots to attempt to illustrate the issue (notice the lack of a detach pool button. When I click on the pool in the gui, it doesn't select it).

 

[SweetAndLow]

What did zfs list show you? Post output in code tags and you can use the cli functionality in the GUI.

 

[Ramy]

What did zfs list show you? Post output in code tags and you can use the cli functionality in the GUI.

Code:

NAME                                                               USED  AVAIL  REFER  MOUNTPOINT                                  
Network_Storage                                                   4.80M  7.02T   192K  /mnt/Network_Storage                        
Network_Storage/.system                                           3.23M  7.02T   208K  legacy                                      
Network_Storage/.system/configs-f1ae6c68bbe041c7bb38cadeec088781   192K  7.02T   192K  legacy                                      
Network_Storage/.system/cores                                     1.40M  7.02T  1.40M  legacy                                      
Network_Storage/.system/rrd-f1ae6c68bbe041c7bb38cadeec088781       192K  7.02T   192K  legacy                                      
Network_Storage/.system/samba4                                     663K  7.02T   663K  legacy                                      
Network_Storage/.system/syslog-f1ae6c68bbe041c7bb38cadeec088781    615K  7.02T   615K  legacy                                      
Network_Storage/Test                                               192K  7.02T   192K  /mnt/Network_Storage/Test                   
Network_Storage/jails                                              192K  7.02T   192K  /mnt/Network_Storage/jails                  
freenas-boot                                                       522M  6.70G    31K  none                                        
freenas-boot/ROOT                                                  514M  6.70G    25K  none                                        
freenas-boot/ROOT/Initial-Install                                    1K  6.70G   508M  legacy                                      
freenas-boot/ROOT/Wizard-2015-07-31_11:40:07                         1K  6.70G   509M  legacy                                      
freenas-boot/ROOT/default                                          514M  6.70G   510M  legacy                                      
freenas-boot/grub                                                 6.79M  6.70G  6.79M  legacy                                       

Is that what you wanted?

 

[SweetAndLow]

Perfect, so it looks like maybe you have a strange mismatch of what the GUI thinks you have and what you actually have. Did you destroy things using the cli by chance?

 

[Ramy]

Not as far as I know. Just FYI, these datasets/volumes are completely blank. I would be fine with wiping everything if it that could make it work.

 

[therealpure]

I'm having a similar issue. Can't see any drives in the GUI.

 

[sfcredfox]

notice the lack of a detach pool button

Does the new version allow you to remove a pool if it's the system dataset pool?
Maybe it transfers that automatically, or you have to move that first? Could be totally unrelated, just curious.

Don't do this without checking with someone else OP but can't he try something like this:

Code:

zpool export %poolname%
zpool import %poolname%

and then reboot. Shouldn't the GUI allow him to re-import the volume at that point and resync itself?