9.1.1 GUI Error, empty content pane

[Azani Ramsan]

As seen in above screenshot, content does not load in anything such as disk list, volume list, smart test list, NTP server list, anything that list records. Looks like JS error to me. I tested using all kind of browser and the result is still the same. The NAS is working fine, the GUI does not.

For diagnosing, I will list my recent activities below :
1. Migrating from old board into a new board, this is not the problem as this problem also exists while I'm using the old board
2. Changing the UPS
3. Removed and reinstalled Transmission plug-in.
4. Reconfigure network interface setting

Other than that, as long as I remembered, the GUI still works fine.

The only times when I access/modify anything in freenas that not using its GUI (through ssh) is when I need to move personal files and folder as root, only for file management, simple commands such as mv, mkdir, rm.
Also, there was a time when my transmission is messed up so I have to fix the json setting file by editing and removing json file through ssh (doing some modification at first, but apparently does not solve the problem, so I resort to deleting the config file, then it works), but that was it, nothing else.
Forgot to mention, I also occasionally check the condition of my UPS through GUI console.

And no, I don't have any spare freenas USB but I do made config backup every 2 months or so. I intend to upgrade to 9.3 after I get my encryption key backups. As far as I know, I cannot do this without accessing the volume details which is impossible with this problem.

Someone had similar problem with the GUI ?

 

[dlavigne]

What are the hardware specs?

 

[Azani Ramsan]

Not some server grade hardware though :

M/B : Asrock B75M-GL
CPU : Intel G2020
RAM : 8GB DDR3 1600 corsair value select
PSU : Seasonic Gold 300W
HDD : 2x WD RED 3TB, 3x WD RED 4TB
UPS : APC BackUPS 800
FreeNAS drive : Sandisk Cruzer Fit 8GB

Old Board :
M/B : MSI 760GM-P34
CPU : AMD Athlon II x4 630
--rest were the same--

 

[dlavigne]

The hardware meets the minimum. Typical other causes for this is flaky network connectivity. Anything related in /var/log/messages?

 

[cyberjock]

That motherboard isn't even remotely close to recommended.

And as I have zero clue what the NIC is because the manufacturer calls it "PCIe Gigabit LAN" I'm gonna go with "probably realtek" which are known to cause all sorts of problems. I'd recommend you review our hardware recommendations thread and buy well supported hardware.

 

[Azani Ramsan]

Hmm, I don't find anything suspicious in /var/log/messages, only ipv6 warning from transmission. My router does not support ipv6 as default route. But I don't know, maybe there are suspicious messages indeed, here I posted in the latest log. I removed all the ipv6-related messages.

Code:

Feb  1 21:27:37 freenas avahi-daemon[2416]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Feb  1 21:27:38 freenas kernel: bridge0: Ethernet address: 02:fe:4a:c8:9c:00
Feb  1 21:27:38 freenas kernel: bridge0: link state changed to UP
Feb  1 21:27:38 freenas kernel: re0: promiscuous mode enabled
Feb  1 21:27:38 freenas kernel: epair0a: Ethernet address: 02:4b:6f:00:08:0a
Feb  1 21:27:38 freenas kernel: epair0b: Ethernet address: 02:4b:6f:00:09:0b
Feb  1 21:27:38 freenas kernel: epair0a: link state changed to UP
Feb  1 21:27:38 freenas kernel: epair0b: link state changed to UP
Feb  1 21:27:38 freenas kernel: re0: link state changed to DOWN
Feb  1 21:27:38 freenas kernel: epair0a: promiscuous mode enabled
Feb  1 21:27:39 freenas ntpd[1807]: sendto(203.89.24.34) (fd=22): No route to host
Feb  1 21:27:40 freenas ntpd[1807]: sendto(202.150.160.150) (fd=22): No route to host
Feb  1 21:27:40 freenas ntpd[1807]: sendto(203.160.128.59) (fd=22): No route to host
Feb  1 21:27:40 freenas ntpd[1807]: bind() fd 28, family AF_INET6, port 123, scope 8, addr fe80::4b:6fff:fe00:80a, mcast=0 flags=0x11 fails: Can't assign requested address
Feb  1 21:27:40 freenas ntpd[1807]: unable to create socket on epair0a (7) for fe80::4b:6fff:fe00:80a#123
Feb  1 21:27:42 freenas kernel: re0: link state changed to UP
Feb  1 21:27:43 freenas kernel: done.
Feb  1 21:27:43 freenas ntpd[1807]: time reset -0.166490 s
Feb  2 00:25:55 freenas ntpd[1807]: time reset -0.825493 s
Feb  2 00:29:26 freenas upsmon[1932]: UPS ups on battery
Feb  2 00:29:51 freenas upsmon[1932]: UPS ups on line power
Feb  2 00:48:26 freenas ntpd[1807]: time reset +0.783669 s
Feb  2 07:06:34 freenas ntpd[1807]: time reset -0.176077 s
Feb  2 07:07:00 freenas ntpd[1807]: time reset +0.173368 s
Feb  3 12:09:12 freenas ntpd[1807]: time reset -0.156385 s
Feb  3 12:32:01 freenas ntpd[1807]: time reset -0.169638 s
Feb  3 13:00:52 freenas ntpd[1807]: time reset +0.157445 s
Feb  4 18:43:24 freenas ntpd[1807]: time reset -0.192621 s
Feb  4 18:50:05 freenas ntpd[1807]: time reset +0.202473 s
Feb  4 20:42:22 freenas ntpd[1807]: time reset -0.404967 s
Feb  4 20:56:33 freenas ntpd[1807]: time reset +0.398550 s
Feb  5 18:10:22 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v
Feb  5 18:10:22 freenas last message repeated 2 times
Feb  5 18:10:23 freenas manage.py: [py.warnings:193] /usr/local/lib/python2.7/site-packages/django/http/request.py:193: DeprecationWarning: HttpRequest.raw_post_data has been deprecated. Use HttpRequest.body instead.   warnings.warn('HttpRequest.raw_post_data has been deprecated. Use HttpRequest.body instead.', DeprecationWarning)
Feb  5 18:10:23 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v
Feb  5 18:10:59 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v
Feb  5 18:10:59 freenas last message repeated 3 times
Feb  5 18:46:03 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v
Feb  5 18:46:03 freenas last message repeated 3 times
Feb  6 07:39:02 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v
Feb  6 07:39:34 freenas last message repeated 4 times
Feb  6 07:39:38 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v

--EDIT-- Whenever I open a list, for example wants to view disk/volume list, this shows up :

Code:

Feb  6 08:05:37 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v

Can't afford for recommended hardware, no vendor in my country sells the specific models listed in hardware recommendation, the only way I can get those by order online and that is expensive, 150% the price (tax & custom). This board only a temporary until I got a new one later, hopefully this quarter.
While it is indeed not a recommended hardware (it is realtek), I have an experience using this board before long ago in FREENAS and no problem at all, in fact, the initial installation of my current FREENAS is using this board, then I switched to AMD and then switched back using this. The reason was I need this board for my gaming rig, now I have a new one, the AMD needs to be buried.
As for the network, I think the GUI responded just fine for example when I click "reporting", the content pane immediately shows the content, same for network summary, global configuration, display system processes etc.
Is there is a way to get encyption key backup using the console ?

 

[cyberjock]

I'm sorry but past history of the NIC provides no guarantee of present or future reliability or performance. Realtek's drivers are also updated regularly and so an upgrade can, in theory, make things unreliable for a NIC that was previously working.

Unfortunately the only recommendation I can provide is to seek out better hardware. If that's not an option you may want to look at using a different OS that may be more compatible with the hardware you purchased. You will find very few people willing to volunteer their own time in troubleshooting problems that are very likely self-inflicted by using inappropriate hardware.

 

[Azani Ramsan]

I understand, it might take 2 months for them to arrive, hopefully this current setup will last until then. I'm ordering the supermicro. (it still haunts me whenever I think about imported stuff when things goes wrong, I have nowhere to get help unless deliver it back to US, another 50% price). Or will list all the available models sold in my country and ask if any of them recommended later, some of them supermicro with intel NIC but none listed in hardware recommendation.

About my question :
is there is a way to get volume encyrption key backup using the console ?
also, if anyone can tell me what this message means :

Code:

Feb  6 08:05:37 freenas manage.py: [common.pipesubr:57] Popen()ing: /usr/local/bin/warden list  -v

 

[Azani Ramsan]

Update, local supermicro vendor won't sell motherboard-only purchase, must bundled with the entire server. Here are the other server board that widely available in my country :
ASUS P8B-X
Tyan S5510GM3NR
Is any of those 2 recommended ?

 

[cyberjock]

Nope.

 

[Azani Ramsan]

I just wanted to report that this problem is no longer exists after migrating to 9.3. Now the contents are properly showing.