Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Configuration being lost on reboot whether stored on floppy or usb drive

    Scheduled Pinned Locked Moved General pfSense Questions
    6 Posts 4 Posters 2.5k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      netnerd
      last edited by

      I know from reading previous posts this has been addressed before and apparently resolved so I assume it must be something unique to my configuration or something I don't understand even after reading the same posts over and over:

      hardware: Dell Poweredge 1650, Perc Raid with Raid 0 and hot spare, cdrom, floppy, usb stick

      version: 1.2.2

      To prepare for the event that all three drives in my array fail before being swapped I have repeatedly attempted the following to have a good configuration stored on a usb drive or floppy to boot into:

      1. removed all hard drives and boot from live cd with either a floppy in the drive or a usb drive attached (not both at the same time).

      2. Select option 98 to store a backup config on the appropriate device recognized during boot.

      3. set the lan interface and created a simple working configuration from the webgui

      4. reboot from the webgui

      When pfsense comes back up I get a network mismatch error and I am again required to set the interfaces. The rest of the configiguration is lost. I verified this by checking the mount point, shutting down and checking the removables on another machine.

      From reading another post I know there was some confusion about how this feature was supposed to be used i.e. it doesn't work in conjunction with a hard disk install but I think I am using it as intended.

      Hopefully somebody sees something obvious I am doing wrong or knows of a known issue with my hardware?

      Thanks in advance.

      1 Reply Last reply Reply Quote 0
      • S
        Sensehans
        last edited by

        I've got the same problem with version 1.2.2. Any solutions?
        After any reboot the system reportes an interface error with a third network device listed that is definetley not installed.
        Tried mOnOwall before and no such error was reported. Tried different USB Memory sticks from 512MB to 1GB.

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          What network device?

          What is the error message?

          Have you tried one of the 1.2.3 snapshot builds? They include a more recent version of FreeBSD which is known to have fixed a number of hardware related problems.  The snapshot builds can be downloaded from http://snapshots.pfsense.org/FreeBSD_RELENG_7_2/pfSense_RELENG_1_2/livecd_installer/

          1 Reply Last reply Reply Quote 0
          • S
            Sensehans
            last edited by

            Interfaces:
            Extern: D-Link DFE-528TX FAST ETHERNET PCI ADAPTER with Realtek RTL8139 Chipset
            Onboard:VIA Rhine II Fast Ethernet Adapter probably with VIA VT8378 Chipsatz. Not very actual chipsets pfsense should handle them.
            Also tested with two PCI cards (Onboard disabled). Same failure!

            I didn't tried a snapshot because I need a stable system. Fallback to mOnOwall was successful. I think this problem occours because the BSD used by pfsense is an older version. If I can spend some time I will try a snapshot.

            1 Reply Last reply Reply Quote 0
            • H
              hioctane21
              last edited by

              I'm having the same exact issue.  I tried the newer snapshot version 1.2.3.  Also tried modifying /boot/device.hints and added hint.acpi.0.disabled="1" and burn a modded iso.  The liveCD seems to be reading the config.xml file but I'm getting

              Initializing............................ls: *.xml: Invalid argument
              

              Then comes up with the "Network interface mismatch – Running interface assignement option."

              Can any one help?

              1 Reply Last reply Reply Quote 0
              • S
                Sensehans
                last edited by

                Sorry there seems to be no solution at this time. Try Monowall. For my system it works fine. I will use it until there is a bug fix or other hints for a solution.
                Regards Hans

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.