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

    Mountroot issues after 2.2 upgrade

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    48 Posts 15 Posters 13.7k 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.
    • W Offline
      warhed
      last edited by

      I have successfully upgraded one system from 2.1.5 to 2.2

      Two other systems upgraded have been destroyed.
      Downloaded the 2.2 ISO, cannot install, corrupted installer. Downloaded a different source same issue, tried another cd burner on another machine another program, same issue?

      So 2.2 seems to be flawed for 2 of the 3 of my systems. There goes my weekend.

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

        Ouch!
        More information please, the devs can't fix something they don't know about.
        What failed? What hardware? What worked?

        Steve

        1 Reply Last reply Reply Quote 0
        • W Offline
          warhed
          last edited by

          Understood.

          One was the BandwidthD c annot be found, please specify path.

          The other states something like this.

          Loader Variables.
          vfs.root.mountfrom=ufs:/dev/ad6s1a
          vfs.root.mountfrom.options=rw

          manual root

          then a ton of variables and gibberish. I had to restore the units so I dont know how to grab logs when these things happen, sorry.

          1 Reply Last reply Reply Quote 0
          • W Offline
            warhed
            last edited by

            From another post on here I get exactly tjhis:

            Loader variables:
                vfs.root.mountfrom=ufs:/dev/ad0s1a
                vfs.root.mountfrom.options=rw

            Manual root filesystem specification:
                <fstype>: <device>[options]
                        Mount <device>using filesystem <fstype>and with the specified (optional) option list

            eg. ufs:/dev/da0s1a
                            zfs:tank
                            cd9660:/dev/acd0 ro
                                  (which is equivalent to: mount -t cd9660 -o ro /dev/acd0 /)

            ?                          List valid disk boot devices
            .                          Yield 1 second (for background tasts)
            <empty lines="">      Abort manual input

            mountroot></empty></fstype></device></device></fstype>

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

              Ok, so as I wrote in that other post it could be a device naming issue which is covered in the upgrade guide. If you type ? at that prompt and you see some devices specifically ada6 then you just need to reset the mount point.

              Don't know about Bandwidthd. I know it works under 2.2. Did that prevent the box booting?

              Steve

              1 Reply Last reply Reply Quote 0
              • W Offline
                warhed
                last edited by

                Ok, what about the bad ISO images? I can't get any to work on two machines for 2.2

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

                  Not seen that but I haven't personally been looking because all my machines run Nano.
                  Did you check the MD5 sums? https://files.pfsense.org/hashes/

                  Steve

                  1 Reply Last reply Reply Quote 0
                  • K Offline
                    kejianshi
                    last edited by

                    You sure you got the correct files?  I seriously doubt they are all corrupt or there would be alot more people screaming.

                    1 Reply Last reply Reply Quote 0
                    • R Offline
                      reqlez
                      last edited by

                      Can somebody change this title ? promotes negative vibes … everybody knows that if you install a product that was released YESTERDAY even if it is in "RELEASE" status issues can occur because an internal "test" cannot beat hundreds of users installing and breaking things :)

                      How about renaming title to "mountroot issues after 2.2 upgrade"

                      But just for the record ... what were the model / hardware configuration of your other systems that bricked ? were they installed on SD cards, CF cards, SSD ?? ... what storage ? I have seen mountroot issues unless you added a "delay" in the booting process, especially for usb connected media.

                      1 Reply Last reply Reply Quote 0
                      • marcellocM Offline
                        marcelloc
                        last edited by

                        Looks like xen vm but it's on release note. "run this before update"…

                        And you should never update anything without testing or backup first.

                        Treinamentos de Elite: http://sys-squad.com

                        Help a community developer! ;D

                        1 Reply Last reply Reply Quote 0
                        • R Offline
                          reqlez
                          last edited by

                          Okay … this line here: vfs.root.mountfrom=ufs:/dev/ad6s1a

                          As far as i remember, the newer versions of FreeBSD use ada0, ada1, etc for SATA and da0, da1, etc for USB or SAS HBA cards, etc.

                          1 Reply Last reply Reply Quote 0
                          • marcellocM Offline
                            marcelloc
                            last edited by

                            @reqlez:

                            How about renaming title to "mountroot issues after 2.2 upgrade"

                            +1

                            Treinamentos de Elite: http://sys-squad.com

                            Help a community developer! ;D

                            1 Reply Last reply Reply Quote 0
                            • R Offline
                              reqlez
                              last edited by

                              same issue here: https://forum.pfsense.org/index.php?topic=87330.0

                              It's either naming or you need to introduce a delay … i'm assuming...

                              1 Reply Last reply Reply Quote 0
                              • E Offline
                                edmund
                                last edited by

                                I upgraded two systems today, both via the autoupgrade.  One is a little nanoBSD box at home and the other is the main firewall at work - running on a Dell.  Both upgrades were flawless with no problems - both boxes support a pair of WAN interfaces with LAN, Wi-Fi, SIP, and a VPN and custom rules.

                                I read through the upgrade notes before performing the upgrades - and uninstalled all packages prior to running the autoupgrade and made backups of the configurations.  Uninstalling the packages is something that I have not done in the past and it definitely made the whole process much quicker than past upgrades.

                                1 Reply Last reply Reply Quote 0
                                • marcellocM Offline
                                  marcelloc
                                  last edited by

                                  @edmund:

                                  Uninstalling the packages is something that I have not done in the past and it definitely made the whole process much quicker than past upgrades.

                                  +1. This is the way I do upgrades since a while.

                                  Treinamentos de Elite: http://sys-squad.com

                                  Help a community developer! ;D

                                  1 Reply Last reply Reply Quote 0
                                  • K Offline
                                    kejianshi
                                    last edited by

                                    4 servers updated so far and all switched to unbound - 0 problems so far.  2 in ESXi and 2 physical.

                                    1 Reply Last reply Reply Quote 0
                                    • C Offline
                                      cheuk3
                                      last edited by

                                      @edmund:

                                      I upgraded two systems today, both via the autoupgrade.  One is a little nanoBSD box at home and the other is the main firewall at work - running on a Dell.  Both upgrades were flawless with no problems - both boxes support a pair of WAN interfaces with LAN, Wi-Fi, SIP, and a VPN and custom rules.

                                      I read through the upgrade notes before performing the upgrades - and uninstalled all packages prior to running the autoupgrade and made backups of the configurations.  Uninstalling the packages is something that I have not done in the past and it definitely made the whole process much quicker than past upgrades.

                                      so uninstall the package first and then use autoupgrade and import the package backup config after?

                                      1 Reply Last reply Reply Quote 0
                                      • K Offline
                                        kejianshi
                                        last edited by

                                        Thats what I did with the VMs running on GB connection with lots of packages.

                                        1 Reply Last reply Reply Quote 0
                                        • C Offline
                                          cheuk3
                                          last edited by

                                          @kejianshi:

                                          Thats what I did with the VMs running on GB connection with lots of packages.

                                          how did you backup the package? or just import the anything after autoupgraded?

                                          1 Reply Last reply Reply Quote 0
                                          • W Offline
                                            wbennett77
                                            last edited by

                                            @kejianshi:

                                            4 servers updated so far and all switched to unbound - 0 problems so far.  2 in ESXi and 2 physical.

                                            Upgraded with no issues as well. Is the switch to unbound automatic?

                                            Cheers!

                                            Dell Optiplex 390 Pfsense 2.2 / Asus AC56U Wireless AP / Asus Switch

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