Broken dashboard after update to 2.3.4-RELEASE-p1 (nanoBSD)



  • Hi,

    I updated my NanoBSD system to 2.3.4-RELEASE-p1. Now the dashboard can't be displayed because of an error - see screenshot.
    Please, can you help me to fix the problem?



  • A very important file, /etc/inc/system.inc, hasn't been created or copied as it should.
    This file exposes the function system_get_uniqueid().

    Make a copy of /conf/config.xml and re install.



  • Could try and 'fix' it, run from console/ssh:

    pkg-static update -f
    pkg-static upgrade -f
    


  • Thanks, it was necessary to reinstall the whole firewall.

    pkg-static
    Doesn't fix the problem



  • Its rarely absolutely necessary. But often a easy way to fix things though, that is if the re-installation process is 'easy'.. (for a remote box without full OOB management its not always that easy..). Anyhow good your up and running again ;)



  • I have this issue too on a NanoBSD system. At boot I get the following in console:

    Welcome to pfSense 2.3.4-RELEASE on the 'nanobsd' platform…

    rm: /usr/local/etc/ipsec.d: Read-only file system
    rm: /usr/local/etc/ipsec.conf: Read-only file system
    rm: /usr/local/etc/strongswan.conf: Read-only file system
    Creating symlinks......ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/ipsec /usr/local/lib/perl5/5.24/mach/CORE
    32-bit compatibility ldconfig path: /usr/lib32
    done.
    cap_mkdb: /etc/login.conf.db: Read-only file system
    /usr/local/libexec/pfSense-upgrade: cannot create /usr/local/etc/pkg.conf: Read-only file system
    /usr/local/libexec/pfSense-upgrade: cannot create /usr/local/etc/pkg.conf: Read-only file system
    Failed to write core file for process php (error 14)
    pid 191 (php), uid 0: exited on signal 11

    Is a reinstall the only way to fix?



  • Not really an issue any more : your system IS telling you what's up :
    @jpns:

    Welcome to pfSense 2.3.4-RELEASE on the 'nanobsd' platform…
    …. Read-only file system
    .... Read-only file system

    …...

    Is a reinstall the only way to fix?

    Re installing is a solution among others.


  • Rebel Alliance Developer Netgate

    @jpns:

    Welcome to pfSense 2.3.4-RELEASE on the 'nanobsd' platform…

    rm: /usr/local/etc/ipsec.d: Read-only file system
    rm: /usr/local/etc/ipsec.conf: Read-only file system
    rm: /usr/local/etc/strongswan.conf: Read-only file system
    /usr/local/libexec/pfSense-upgrade: cannot create /usr/local/etc/pkg.conf: Read-only file system
    /usr/local/libexec/pfSense-upgrade: cannot create /usr/local/etc/pkg.conf: Read-only file system

    Is a reinstall the only way to fix?

    Reinstall is one way. There is a chance that booting to single user mode and running "fsck -y /" a few times until the scan finds no errors may help.

    Though if your system is capable of running a full installation, it would be a perfect time to reinstall and migrate away from NanoBSD.


Log in to reply