Lost my FreeNAS

[Glorious1]

All I did was try to change the IP address in the WebGUI. I lost access to the WebGUI. It wasn't at the new IP. I got into the IPMI-KVM and tried to set the network interface there. No matter what I did, it finished by saying there was no configured interface. Then I rebooted and it got worse. It starts cycling between showing the console setup menu, then
Freenas init: getty repeating too quickly on port /dev/ttyv0, sleeping 30 seconds

It never even gets to the prompt. This thing seems pretty unstable.

 

[DrKK]

Seems similar to this:

https://bugs.pcbsd.org/issues/7135

Can you run netcli directly from /etc?

 

[Glorious1]

Thanks DrKK. While it was booting I saw something fly by in the KVM console about nginx failing to start up and nginx.conf was bad or something. I looked in debug.log and messages and couldn't find those statements.

I think the bug is the same, though unlike that ticket, I never configured IPv6 and have a simple set up. All I did was change IPv4 address in the GUI and it went berserk.

The command you suggested fails as follows

Code:

$ /etc/netcli
Traceback (most recent call last):
  File "/etc/netcli", line 57, in <module>
    cache.get_apps()
  File "/usr/local/lib/python2.7/site-packages/django/db/models/loading.py", line 139, in get_apps
    self._populate()
  File "/usr/local/lib/python2.7/site-packages/django/db/models/loading.py", line 78, in _populate
    self.load_app(app_name)
  File "/usr/local/lib/python2.7/site-packages/django/db/models/loading.py", line 99, in load_app
    models = import_module('%s.models' % app_name)
  File "/usr/local/lib/python2.7/site-packages/django/utils/importlib.py", line 40, in import_module
    __import__(name)
  File "/usr/local/www/freenasUI/network/models.py", line 39, in <module>
    from freenasUI.services.models import CIFS
  File "/usr/local/www/freenasUI/services/models.py", line 269, in <module>
    class AFP(Model):
  File "/usr/local/www/freenasUI/services/models.py", line 297, in AFP
    choices=list(choices.IPChoices()),
  File "/usr/local/www/freenasUI/choices.py", line 467, in __init__
    include_vlan_parent=include_vlan_parent
  File "/usr/local/www/freenasUI/choices.py", line 349, in __init__
    conn = sqlite3.connect(freenasUI.settings.DATABASES['default']['NAME'])
sqlite3.OperationalError: unable to open database file

/etc/local/nginx/nginx.conf looks like this - not sure if it's fouled up. The IP shown at the end, 192.168.0.2:80, has the correct OLD IP but the wrong port (it was 443). In any case I can't reach the WebGUI at that address.

Code:

$ cat /etc/local/nginx/nginx.conf
#
#    FreeNAS nginx configuration file
#

user www www;
worker_processes  1;

events {
    worker_connections  1024;
}

http {
    include       mime.types;
    default_type  application/octet-stream;

    # reserve 1MB under the name 'proxied' to track uploads
    upload_progress proxied 1m;

    sendfile        on;
    #tcp_nopush     on;
    client_max_body_size 500m;

    #keepalive_timeout  0;
    keepalive_timeout  65;

    #gzip  on;
    #upload_store /var/tmp/firmware;
    client_body_temp_path /var/tmp/firmware;
   
    server {
        server_name  localhost;
    listen            192.168.0.2:443 default_server ssl spdy;
    listen            [::]:443 default_server ssl spdy;

    ssl_certificate        "/etc/certificates/For HTTPS access.crt";
    ssl_certificate_key    "/etc/certificates/For HTTPS access.key";
    ssl_dhparam /data/dhparam.pem;

    ssl_session_timeout    120m;
    ssl_session_cache    shared:ssl:16m;

        ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
    ssl_prefer_server_ciphers on;
    ssl_ciphers EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA256:EECDH+aRSA+RC4:EDH+aRSA:EECDH:RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS;
    add_header Strict-Transport-Security max-age=31536000;

    ## TODO: OCSP Stapling
    #ssl_stapling on;
    #ssl_stapling_verify on;
    #resolver ;
    #ssl_trusted_certificate ;

        location / {
            include fastcgi_params;
            fastcgi_pass 127.0.0.1:9042;
            fastcgi_pass_header Authorization;
            fastcgi_intercept_errors off;
            fastcgi_read_timeout 600m;
            #fastcgi_temp_path /var/tmp/firmware;
            fastcgi_param HTTPS $https;

            # track uploads in the 'proxied' zone
            # remember connections for 30s after they finished
            track_uploads proxied 30s;
        }

        location /progress {
            # report uploads tracked in the 'proxied' zone
            report_uploads proxied;
        }

        location /dojango {
            alias /usr/local/www/freenasUI/dojango;
        }

        location /static {
            alias /usr/local/www/freenasUI/static;
        }

        location /reporting/graphs {
            alias /var/db/graphs;
        }

        location /dojango/dojo-media/release/1.10.1 {
            alias /usr/local/www/dojo;
        }

        location /docs {
            alias /usr/local/www/data/docs;
        }

        #error_page  404              /404.html;

        # redirect server error pages to the static page /50x.html
        #
        error_page   500 502 503 504  /50x.html;
        location = /50x.html {
            root   /usr/local/www/nginx-dist;
        }

        #include plugins.conf;
    }
    server {
    listen 192.168.0.2:80;
    listen [::]:80;
    server_name localhost;
    return 307 https://$host:443$request_uri;
    }
}

 

[DrKK]

Sir, it is time to reinstall your FreeNAS boot device. It should not affect any data pools.

 

[Glorious1]

Oh man what a pain. After dinking around I got a fresh install from the iso. Then I was able to set the network interface IP as desired. Then I uploaded my configuration. As expected, it set the IP address back to the old one. So then I reset it to the new IP - nope. It won't work, always says no interface found.

The configuration is apparently screwed up.

 

[Glorious1]

This just keeps getting better and better. Now, just trying to do a totally fresh install, it stops at the mountroot prompt after getting through the GRUB and choosing installer. I found the illustrious KK post on workaround/semi-fix for that, but it didn't seem applicable, didn't look the same, and more importantly, it didn't work. I'm stuck in mountroot hell.

Freenas is really stable if you just get it running and leave it alone, but it seems if you start tinkering with anything a bit out of the ordinary, it has the potential to come down like a house of cards. Just me venting.

 

[Ericloewe]

Out of curiosity, what's the hardware?

The only install/upgrade/boot issue I've had since I moved to 9.3 early February (and 9.2.1.7, for that matter) was a borked FreeNAS update caused by a bug in the config importer - which was automagically fixed by rolling back to the snapshot of the previous installation.

 

[Glorious1]

Motherboard: SuperMicro A1SRi-2758F mini-ITX with integrated
CPU: Intel Atom C2758 CPU, 8-core 2.4 GHz, TDP 20 W
HBA/Expander: LSI 9240-8i PCIe board flashed to IT mode, provides 8 SATA ports
RAM: Crucial 2x 8GB SO-DIMM 204-pin Unbuff. ECC DDR3-1600 1.35V
Drives: 4x WD Red NAS 3 TB, 4x WD Green 3 TB
Power Supply: SeaSonic Platinum Series SS-400FL2 Fanless, Active PFC
Case: Lian Li PC-Q26 with 4x 120-mm fans and room for 10 3.5" drives
FreeNAS: 9.3-STABLE-201412142326, five disks in RaidZ1 (remaining disks for backup)
Boot Device: 2x mirrored SanDisk 8 GB Cruzer Fit

After 6-8 hours of frustration, I reinstalled again fresh. I didn't put my old config in, starting from scratch. I forgot just how much configuration there was! I'm just afraid when I try to change the network IP again, it will go belly up again.

 

[Ericloewe]

I wonder if the networking hardware (whatever Intel calls the accelerator...) might be needing a driver fix...

 

[Glorious1]

I have no idea about a networking driver; that would be something in FreeBSD I assume?

It just registered that you said you rolled back to a snapshot of a previous installation - could you explain? Do you mean a previous FreeNAS version in the System>Boot menu? Or you're snapshotting the boot volume, or what?

 

[Ericloewe]

I have no idea about a networking driver; that would be something in FreeBSD I assume?

It just registered that you said you rolled back to a snapshot of a previous installation - could you explain? Do you mean a previous FreeNAS version in the System>Boot menu? Or you're snapshotting the boot volume, or what?

A snapshot is automatically made for each update. If an update fails, FreeNAS automagically rolls back to the last known-good one.