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

    ZFS ISSUES!!! built on Wed Jul 11 16:46:22 EDT 2018

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    37 Posts 9 Posters 6.3k 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.
    • L
      LostInIgnorance
      last edited by LostInIgnorance

      Glad to see you guys are bringing this bug back on the latest snapshot.

      https://redmine.pfsense.org/issues/6929

      1 Reply Last reply Reply Quote 1
      • chpalmerC
        chpalmer
        last edited by

        https://forum.netgate.com/topic/132727/latest-snap-stopping-with-error-2-4-on-watchguard-xcs-box

        I was running a snap from earlier this morning and then tried the one labeled about 1130 when I started seeing this.

        Triggering snowflakes one by one..
        Intel(R) Core(TM) i5-4590T CPU @ 2.00GHz on an M400 WG box.

        1 Reply Last reply Reply Quote 0
        • L
          LostInIgnorance
          last edited by

          Someone has filled out a redmine ticket related to it. I suggest tracking progress there.

          https://redmine.pfsense.org/issues/8639

          1 Reply Last reply Reply Quote 1
          • Raul RamosR
            Raul Ramos
            last edited by

            If i install at least built on Thu Jul 12 08:51:04 EDT 2018 manually i can boot pFsense again. Don't know if is a update problem.

            pfSense:
            ASRock -> Wolfdale1333-D667 (2GB TeamElite Ram)
            Marvell 88SA8040 Sata to CF(Sandisk 4GB) Controller
            NIC's: RTL8100E (Internal ) and Intel® PRO/1000 PT Dual (Intel 82571GB)

            1 Reply Last reply Reply Quote 0
            • L
              LostInIgnorance
              last edited by

              I have not updated mine yet, but will be getting out of work soon to test as I don't have remote IPMI setup yet and am afraid to do it remotely at this moment of noway to get it back up.

              1 Reply Last reply Reply Quote 0
              • L
                LostInIgnorance
                last edited by

                @raul-ramos It's a no-go for me on that snapshot, although I did not manually modify the config after to add the lines back in.

                1 Reply Last reply Reply Quote 0
                • w0wW
                  w0w
                  last edited by

                  Yes, this is upgrade bug. Clean install works, but if you upgrade it to the next snapshot it is going to fail on boot.

                  1 Reply Last reply Reply Quote 0
                  • M
                    maverick_slo
                    last edited by

                    Updated redmine as well...

                    1. Clean install of (2.4.4-DEVELOPMENT (amd64)built on Fri Jul 13 10:56:07 EDT 2018FreeBSD 11.2-RELEASE)
                    2. Restore config
                    3. Reboot
                    4. Upgrade and reboot (2.4.4.a.20180713.1957)
                    5. Borked system zfs won`t mount
                    w0wW 1 Reply Last reply Reply Quote 0
                    • w0wW
                      w0w @maverick_slo
                      last edited by w0w

                      @maverick_slo
                      Actually you don't need to restore config, at least it is not necessary to reproduce the problem. I've used clean install in VM and right after boot updated it with option 13, without configuring anything.

                      1 Reply Last reply Reply Quote 0
                      • M
                        maverick_slo
                        last edited by

                        Yeah I know.
                        I just wanted to note exactly what I did.

                        But lack of offical response makes me concerned...
                        At least they could pull upgrades.

                        w0wW 1 Reply Last reply Reply Quote 0
                        • w0wW
                          w0w @maverick_slo
                          last edited by w0w

                          @maverick_slo
                          May be it's vacations. Delays are expected in summer time ☺
                          And this is development branch that have low priority I think, because everyone who uses it, must be ready for fail. The other thing embarrassing me is that 2.4.4 have too much major changes for the minor version.

                          1 Reply Last reply Reply Quote 0
                          • w0wW
                            w0w
                            last edited by

                            Should be fixed with recent snapshot.

                            1 Reply Last reply Reply Quote 0
                            • M
                              maverick_slo
                              last edited by

                              Tried todazs and same mountroot error.

                              w0wW 1 Reply Last reply Reply Quote 0
                              • w0wW
                                w0w @maverick_slo
                                last edited by

                                @maverick_slo
                                Before upgrade check that your /boot/loader.conf contains

                                zfs_load="YES"
                                

                                Mine was just missing. I've added it manually and upgraded successfully to JUL 17 7:07 version.

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

                                  I do have zfs_load="YES" on loader.conf and it failed to upgrade from:

                                  2.4.4-DEVELOPMENT (amd64)
                                  built on Fri Jul 13 19:58:06 EDT 2018
                                  FreeBSD 11.2-RELEASE

                                  to:

                                  Can't be sure snapshot version. It was arround 14:00 GMT+1.

                                  1 Reply Last reply Reply Quote 0
                                  • w0wW
                                    w0w
                                    last edited by w0w

                                    0_1531844987826_VirtualBox_pfSense-244 testing bug_17_07_2018_19_25_49.png

                                    Clean install and upgrade, both versions are on the screenshot. No problem after boot and reboot.

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

                                      Well.... it didn't work for me.

                                      EDIT: sorry. Adding pics.

                                      EDIT2: Now it should be here.

                                      0_1531846918393_pic1.jpg 0_1531846947671_pic2.jpg

                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        maverick_slo
                                        last edited by

                                        For me either... Same error

                                        Updating repositories metadata...
                                        Updating pfSense-core repository catalogue...
                                        pfSense-core repository is up to date.
                                        Updating pfSense repository catalogue...
                                        pfSense repository is up to date.
                                        All repositories are up to date.
                                        Setting vital flag on pkg... done.
                                        Downloading upgrade packages...
                                        Updating pfSense-core repository catalogue...
                                        pfSense-core repository is up to date.
                                        Updating pfSense repository catalogue...
                                        pfSense repository is up to date.
                                        All repositories are up to date.
                                        Checking for upgrades (9 candidates): ......... done
                                        Processing candidates (9 candidates): ......... done
                                        The following 10 package(s) will be affected (of 0 checked):

                                        New packages to be INSTALLED:
                                        openvpn-auth-script: 1.0.0.3 [pfSense]

                                        Installed packages to be UPGRADED:
                                        snort: 2.9.11.1_1 -> 2.9.11.1_2 [pfSense]
                                        php72-pfSense-module: 0.62_1 -> 0.62_5 [pfSense]
                                        pfSense-rc: 2.4.4.a.20180713.1056 -> 2.4.4.a.20180717.0756 [pfSense-core]
                                        pfSense-kernel-pfSense: 2.4.4.a.20180713.1056 -> 2.4.4.a.20180717.0756 [pfSense-core]
                                        pfSense-default-config: 2.4.4.a.20180713.1056 -> 2.4.4.a.20180717.0756 [pfSense-core]
                                        pfSense-base: 2.4.4.a.20180713.1056 -> 2.4.4.a.20180717.0756 [pfSense-core]
                                        pfSense: 2.4.4.a.20180713.0955 -> 2.4.4.a.20180717.0730 [pfSense]
                                        git: 2.18.0 -> 2.18.0_1 [pfSense]
                                        e2fsprogs-libuuid: 1.44.2_1 -> 1.44.3 [pfSense]

                                        Number of packages to be installed: 1
                                        Number of packages to be upgraded: 9

                                        57 MiB to be downloaded.
                                        [1/10] Fetching snort-2.9.11.1_2.txz: .......... done
                                        [2/10] Fetching php72-pfSense-module-0.62_5.txz: ...... done
                                        [3/10] Fetching pfSense-rc-2.4.4.a.20180717.0756.txz: .. done
                                        [4/10] Fetching pfSense-kernel-pfSense-2.4.4.a.20180717.0756.txz: .......... done
                                        [5/10] Fetching pfSense-default-config-2.4.4.a.20180717.0756.txz: . done
                                        [6/10] Fetching pfSense-base-2.4.4.a.20180717.0756.txz: .......... done
                                        [7/10] Fetching pfSense-2.4.4.a.20180717.0730.txz: . done
                                        [8/10] Fetching git-2.18.0_1.txz: .......... done
                                        [9/10] Fetching e2fsprogs-libuuid-1.44.3.txz: ..... done
                                        [10/10] Fetching openvpn-auth-script-1.0.0.3.txz: . done
                                        Checking integrity... done (0 conflicting)

                                        Upgrading pfSense kernel...
                                        Checking integrity... done (0 conflicting)
                                        The following 1 package(s) will be affected (of 0 checked):

                                        Installed packages to be UPGRADED:
                                        pfSense-kernel-pfSense: 2.4.4.a.20180713.1056 -> 2.4.4.a.20180717.0756 [pfSense-core]

                                        Number of packages to be upgraded: 1
                                        [1/1] Upgrading pfSense-kernel-pfSense from 2.4.4.a.20180713.1056 to 2.4.4.a.20180717.0756...
                                        [1/1] Extracting pfSense-kernel-pfSense-2.4.4.a.20180717.0756: .......... done
                                        ===> Keeping a copy of current kernel in /boot/kernel.old
                                        Upgrade is complete. Rebooting in 10 seconds.
                                        Success

                                        w0wW 1 Reply Last reply Reply Quote 0
                                        • w0wW
                                          w0w
                                          last edited by

                                          Will try exactly 2.4.4.a.20180713.1056 to see what happens. ☺

                                          1 Reply Last reply Reply Quote 0
                                          • w0wW
                                            w0w @maverick_slo
                                            last edited by w0w

                                            @maverick_slo
                                            yes, it refuses to boot with the same error after upgrade.
                                            I don't understand how it's happening... Ask on redmine, please.

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