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

    pFsense HD Corupt?

    Scheduled Pinned Locked Moved General pfSense Questions
    4 Posts 3 Posters 900 Views 3 Watching
    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.
    • M Offline
      MyNetworkRocks
      last edited by

      Hi all,

      I had to reboot my pfsense which I havent done in over 9 months.

      The version I have is:

      System
Netgate XG-7100
BIOS
Vendor: coreboot
Version: ADI_PLCC-01.00.00.11
Release Date: Tue Jan 8 2019

      I noticed it wasnt responding to the webGui or to ssh. I connected a console cable to see what was happening.
      Firstly after numerous reboots I noticed it would get to:

      Configuring firewall......done.

      and would just hang there every single time - I left it for various time periods (5mins, 30mins, 2 hours - after reboots) and it would still just hang there.

      Full output

      Done.
.... done.
Initializing.................. done.
Starting device manager (devd)...done.
Loading configuration......done.
Updating configuration...done.
Checking config backups consistency.................................done.
Setting up extended sysctls...done.
coretemp0: <CPU On-Die Thermal Sensors> on cpu0
Setting timezone...done.
Configuring looplo0: link state changed to UP
back interface...done.
Starting syslog...done.
Starting Secure Shell Services...done.
Configuring switch...done.
Setting up interfaces microcode...done.
Starting PC/SC Smart Card Services...done.
Configuring loopback interface...done.
Creating wireless clone interfaces...done.
Configuring LAGG interfaces...done.
Configuring VLAN interfaces...done.
Configuring QinQ interfaces...done.
Configuring WAN interface...done.
Configuring LAN interface...done.
Configuring IPsec VTI interfaces...done.
Configuring CARP settings...done.
Syncing OpenVPN settings...done.
Configuring firewall......done.
Starting PFLOG...done.
Setting up gateway monitors...done.
Setting up static routes...done.
Setting up DNSs...
Synchronizing user settings...done.
Starting webConfigurator...done.
Configuring CRON...done.
Starting NTP Server...done.
Starting DHCP service...done.
Configuring firewall......done.

      I decided to check the boot options which are:

      Select boot device:
1. AHCI/1: KINGSTON SM2280S3120G ATA-8 Hard-Disk (111 GiBytes)
2. MMC drive M52532 29184MiB
3. iPXE (PCI 06:00.0)
4. iPXE (PCI 06:00.1)
5. Payload [setup]
Booting from Hard Disk... harddrive_index=0

/boot/config: -S115200 -h
Consoles: serial port
BIOS drive C: is disk0
BIOS drive D: is disk1
BIOS 638kB/2086672kB available memory

FreeBSD/x86 bootstrap loader, Revision 1.1
(Wed Sep  5 11:02:26 EDT 2018 root@buildbot3)
Loading /boot/defaults/loader.conf

      What I noticed is if I booted from option 1:

      AHCI/1: KINGSTON SM2280S3120G ATA-8 Hard-Disk (111 GiBytes)

      It would boot all the way up to:

      Configuring firewall......done.

      And then hang if then tried booting from option 2:

      MMC drive M52532 29184MiB

      It would boot and I could get to the web interface and on the console get the menu. I could then get into the web interface. Of course doing a hard reset it went back to the original version:

      2.4.4-RELEASE (amd64)
built on Thu Sep 20 09:33:19 EDT 2018
FreeBSD 11.2-RELEASE-p3

      I am now in the process of doing a upgrade to the latest version.

      My question
      Not sure what happened, I dont think it was booting off the 2. MMC drive M52532 29184MiB as every time I did a reboot it would revert back to booting off: AHCI/1: KINGSTON SM2280S3120G ATA-8 Hard-Disk (111 GiBytes) during a normal boot cycle (i.e. I didnt select any option)

      Is this right that it boots off the MMC drive? What I have noticed now is on the webGUI when I look at space it only shows one option in the disk space:

      8% of 26GiB - ufs

      Where I am almost certain it use to use the KINGSTON option (ATA-8 Hard-Disk).

      My Second Question
      I have now initiated a upgrade from:

      2.4.4-RELEASE (amd64)
built on Thu Sep 20 09:33:19 EDT 2018
FreeBSD 11.2-RELEASE-p3

      To:

      Version 21.02.2 is available. 
Version information updated at Tue Nov 23 15:50:05 UTC 2021

      But it seems to just stay on (well for the last 30mins) :

      Please wait while the update system initializes

      Should it be taking this long? My experiance before is that it might take a while but usually there is much more information whilst the system is updating and it doesnt stay on "Please wait while the update system initializes" for that long?

      Would appreciate the guidence!

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        SteveITS Rebel Alliance @MyNetworkRocks
        last edited by

        @mynetworkrocks re: your second question I've seen that in a few cases. Try restarting (which it sounds like you have been doing...?).

        If updating from 2.4.4 to 21.x doesn't work (and, note that it's not detecting 21.05.x!) I have at least a couple of times had to upgrade to 2.4.5 first. See if System/Update can be set to Previous Stable Version. Update to that, then change that page to update to 21.05.

        Only install packages for your version, or risk breaking it. Select your branch in System/Update/Update Settings.
        When upgrading, allow 10-15 minutes to reboot, or more depending on packages, and device or disk speed.
        Upvote 👍 helpful posts!

        1 Reply Last reply Reply Quote 1
        • stephenw10S Offline
          stephenw10 Netgate Administrator
          last edited by stephenw10

          Yup, you might have to go to 2.4.5 first. But I wouldn't do that.

          It looks like you have an older pfSense version installed on the eMMC and that;s what you are now booting into. Normally it would boot from SSD and not touch the eMMC, running a factory reset after booting from eMMC will do nothing to the SSD install.

          I would first try booting from the SSD again and where it hangs enter 'ctl+t' at the console. That should show you what it's waiting for.

          If you have a backup of the config I would probably just reinstall 21.05.2 on the SSD again directly and restore the config. Open a ticket with us to get the recovery image:
          https://go.netgate.com/

          Steve

          1 Reply Last reply Reply Quote 1
          • M Offline
            MyNetworkRocks
            last edited by

            @steveits said in pFsense HD Corupt?:

            @mynetworkrocks re: your second question I've seen that in a few cases. Try restarting (which it sounds like you have been doing...?).

            @SteveITS - yes that is what I was doing, I was rebooting it a few times to try figure out what was going on. It seems like something got corrupts on the M.2 drive that I have installed on the XG-7100 and the brought the whole thing down.

            I have now installed the latest version on the MMC drive and going to use that as a backup. I will be reinstalling on the M.2 drive.

            @stephenw10
            Thank you I did and support was excellent they pinged me a image download within a few minutes.
            On the MMC I had to go to 2.4.5 first then to the latest version. I will keep that as a "live" backup, I will reinstall on the M.2 with the new image.

            Thank you for all the replies!

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