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

    Upgrade from 2.1.5 nano to 2.2.1 problem

    Scheduled Pinned Locked Moved Problems Installing or Upgrading pfSense Software
    17 Posts 5 Posters 3.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.
    • S
      stenio
      last edited by

      Hello,

      I tried to upgrade to version 2.2.1 but the system stalls on a disk command timeout after the reboot:

      
Rebooting...

1   FreeBSD
2   FreeBSD

Boot:   2
▒▒▒߿▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒J▒▒▒▒▒▒▒▒▒▒▒ф▒▒▒▒7▒1
 ▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
/boot/kernel/kernel text=0x11f7fd9 data=0x832cf0+0x279e60 syms=[0x4+0xf36c0+0x4+0x16b89c]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...
KDB: debugger backends: ddb
KDB: current backend: ddb
ACPI BIOS Error (bug): A valid RSDP was not found (20130823/tbxfroot-223)
Copyright (c) 1992-2014 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
        The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 10.1-RELEASE-p6 #0 b69ba8f(releng/10.1)-dirty: Fri Mar 13 08:45:06 CDT 2015
    root@pfs22-i386-builder:/usr/obj.i386/usr/pfSensesrc/src/sys/pfSense_wrap.10.i386 i386
FreeBSD clang version 3.4.1 (tags/RELEASE_34/dot1-final 208032) 20140512
VT: running with driver "vga".
CPU: VIA Eden Processor 1000MHz (997.52-MHz 686-class CPU)
  Origin = "CentaurHauls"  Id = 0x6d0  Family = 0x6  Model = 0xd  Stepping = 0
  Features=0xa7c9bbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>Features2=0x4181 <sse3,est,tm2,xtpr>AMD Features=0x100000 <nx>VIA Padlock Features=0xffcc <rng,aes,aes-ctr,sha1,sha256,rsa>real memory  = 1073741824 (1024 MB)
avail memory = 983949312 (938 MB)
MPTable: <template etemplate =""></template></rng,aes,aes-ctr,sha1,sha256,rsa></nx></sse3,est,tm2,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>
      1 Reply Last reply Reply Quote 0
      • D
        doktornotor Banned
        last edited by

        • Does that card handle UDMA? If not, set the hints in loader.conf.local accordingly:  https://doc.pfsense.org/index.php/Boot_Troubleshooting#pfSense_2.2_and_later
        • Did not help? Reimage the card, restore configuration backup.
        • Did not help? Replace the faulty CF card and do the above.
        1 Reply Last reply Reply Quote 0
        • S
          stenio
          last edited by

          I think the card supports UDMA:

          [2.1.5-RELEASE][admin@firewall.b2]/root(12): atacontrol cap ad2

          Protocol              ATA/ATAPI revision 4
          device model          SanDisk SDCFX3-008G
          serial number        AGZ091009122714
          firmware revision    HDX 5.00
          cylinders            7773
          heads                16
          sectors/track        63
          CFA supported
          lba supported        7835184 sectors
          lba48 not supported
          dma supported
          overlap not supported

          Feature                      Support  Enable    Value          Vendor
          write cache                    yes      no
          read ahead                    no      no
          Tagged Command Queuing (TCQ)  no      no      0/0x00
          SMART                          no      no
          microcode download            no      no
          security                      no      no
          power management              no      no
          advanced power management      no      no      0/0x00
          automatic acoustic management  no      no      0/0x00  0/0x00

          So it seems a faulty CF card, right?

          Anyway I'll try to disable DMA at boot time because currently it is not using it and works:

          [2.1.5-RELEASE][admin@firewall.b2]/root(13): atacontrol mode ad2
          current mode = PIO4

          1 Reply Last reply Reply Quote 0
          • D
            doktornotor Banned
            last edited by

            @stenio:

            Anyway I'll try to disable DMA at boot time because currently it is not using it and works:

            [2.1.5-RELEASE][admin@firewall.b2]/root(13): atacontrol mode ad2
            current mode = PIO4

            Because UDMA is disabled by default on nanobsd on 2.1.x, but enabled by default on 2.2.x. Use the 2.2 hints before upgrade.

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

              Thanks doktornotor,

              I created the file /boot/loader.conf.local and this evening I'll try to upgrade again.

              [2.1.5-RELEASE][admin@firewall.b2]/root(18): cat /boot/loader.conf.local
              hint.ata.0.mode=PIO4
              hint.ata.1.mode=PIO4

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

                Just tried with the hint.ata.1.mode=PIO4 and now it is evev worse:

                […]
                (aprobe0:ata1:0:1:0

                system locked.  :'(

                1 Reply Last reply Reply Quote 0
                • D
                  doktornotor Banned
                  last edited by

                  Ditch the card.

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

                    I'm thinking to switch to the hdd version.

                    Do you know if it is possible to restore the configuration of the nano version on it?

                    Thanks

                    1 Reply Last reply Reply Quote 0
                    • D
                      doktornotor Banned
                      last edited by

                      Yes, you can do that.

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

                        @doktornotor:

                        Ditch the card.

                        Hi, I tried with a new CF card attached to an USB card reader but the error is the same:

                        (aprobe0:ata1:0:1:0): ATA_IDENTIFY. ACB: ec 00 00 00 00 40 00 00 00 00 00 00
(aprobe0:ata1:0:1:0): CAM status: Command timeout
(aprobe0:ata1:0:1:0): Retrying command

                        I'll try with:

                        hint.atapci.1.msi="0"

                        I hope it works!  :-\

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

                          No way!

                          I tried with all possibles hint settings, booting from an USB stick, also disabling the internal CF by BIOS but the result is the same.

                          At this point I think that FreeBSD 10.1 is simply not compatible with my hardware.  :'(

                          EDIT:

                          I think this is the problem:
                          http://freebsd.1045724.n5.nabble.com/no-subject-td5952628i20.html

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

                            What hardware are you running?
                            There has been at least one other platform that reports similar errors on 2.2+. There is no solution as yet I'm afraid.
                            https://forum.pfsense.org/index.php?topic=87364.0

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • B
                              bval
                              last edited by

                              @stenio:

                              At this point I think that FreeBSD 10.1 is simply not compatible with my hardware.  :'(

                              EDIT:

                              I think this is the problem:
                              http://freebsd.1045724.n5.nabble.com/no-subject-td5952628i20.html

                              stenio, were you ever able to resolve this? I am running into the exact same issue on a soekris net4801 with the exact same model # of CF card.

                              Thanks,

                              Brandon

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

                                @bval:

                                stenio, were you ever able to resolve this? I am running into the exact same issue on a soekris net4801 with the exact same model # of CF card.

                                Hi Brandow,
                                I've just tried with the latest PF 2.2.6 but the problem is still there!  :(

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

                                  @stephenw10:

                                  What hardware are you running?
                                  There has been at least one other platform that reports similar errors on 2.2+. There is no solution as yet I'm afraid.
                                  https://forum.pfsense.org/index.php?topic=87364.0

                                  Sorry Steve, I missed your post. I'm using a Fabiatech FX5621:
                                  https://forum.pfsense.org/index.php?topic=92279.msg511016#msg511016
                                  https://forum.pfsense.org/index.php?topic=92279.0

                                  Regards,
                                  Stenio

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    phil.davis
                                    last edited by

                                    Note for reference: https://forum.pfsense.org/index.php?topic=87364.msg583303#msg583303
                                    No luck with the FW-525B on latest pfSense 2.3-ALPHA that follows FreeBSD 10 development.

                                    As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
                                    If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

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

                                      @phil.davis:

                                      Note for reference: https://forum.pfsense.org/index.php?topic=87364.msg583303#msg583303
                                      No luck with the FW-525B on latest pfSense 2.3-ALPHA that follows FreeBSD 10 development.

                                      It seems that the problem will be solved in FreeBSD 11:
                                      https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=199495

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