Packages vanishes after reboot

  • Greetings friends.
    I have a strange issue.
    I installed packages cron, bandwidthd, OpenVpnExport list and configure everything.
    after a reboot the packages just gets vanished from "installed packages"
    is my filesystem mounted as readonly ? how can i check that ?
    many thanks

  • This is the output of the mount command from ssh:

    : mount
    /dev/ufs/pfsense1 on / (ufs, local, noatime, read-only, synchronous)
    devfs on /dev (devfs, local)
    /dev/md0 on /tmp (ufs, local)
    /dev/md1 on /var (ufs, local)
    /dev/ufs/cf on /cf (ufs, local, noatime, read-only, synchronous)
    devfs on /var/dhcpd/dev (devfs, local)


  • Sometimes on Alix (256MB memory) it runs out of memory when rebooting after a firmware upgrade and reinstalling packages. For example, I just updated a test system with 2 OpenVPN clients, blinkled, cron and squid. The process that was downloading squid got killed:

    Beginning package installation for squid3 . 100%
    Installing squid3 and its dependencies.   9%Killed

    When that happens, the package/s need to be manually installed again from the WebGUI. But all the settings should still be in the config, waiting to be used when the package is installed again.
    An ordinary reboot should not lose any packages. But note that I have done a few upgrades recently to systems you are looking at, so the packages might have been "lost" at that time.

    The /dev/ufs/pfsense1 and /dev/ufs/cf partitions are the ones that should be read-only, like in your command output below. Now days (2.1-BETA1) the System Information widget on the dashboard shows the rw/ro state:

    NanoBSD Boot Slice 	pfsense0 / ad0s1 (rw) 

    This example is from the system that had the squid install get killed. The filesystem has been left rw.
    You can fix that from Diagnostics:NanoBSD:

    Current Read/Write Status: 	Read/Write (reference count 2)

    Press the "Switch to Read-Only" button, the reference count drops by 1 each time, then it goes back to read-only.
    Normally, nanoBSD systems should boot cleanly and be read-only at the end of the boot!

  • Thankyou phil jee.
    I was nearly getting MAD.

Log in to reply