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

    2.2 to 2.1.4

    Problems Installing or Upgrading pfSense Software
    4
    18
    2.5k
    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.
    • O
      ozlecz
      last edited by

      I have an existing running pfsense 2.2

      How can I completely wipe this out and install a fresh 2.1.4

      thanks

      1 Reply Last reply Reply Quote 0
      • O
        ozlecz
        last edited by

        forget to tell…the storage is msata..

        1 Reply Last reply Reply Quote 0
        • V
          vindenesen
          last edited by

          Hi ozlecz,

          I would guess the same way that you installed 2.2? If you are running the "full" version, and not the embedded/nano (which I have no experience with), you can just run the installer of 2.1.4, select quick install, and it will wipe your disk before installing.

          Support the project by buying a Gold Subscription at https://portal.pfsense.org
          Running pfSense on SuperMicro A1SRI-2758F with ESXi 5.5

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

            If you are running Nano then just reflash it to the mSATA. There is no 'downgrade' option.
            Importantly the config file from your 2.2 install probably won't restore onto a 2.1.4 install.

            Steve

            1 Reply Last reply Reply Quote 0
            • O
              ozlecz
              last edited by

              wouldnt the APUTinyCore for PCEngines installer detect the existing higher version and NOT proceed?

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

                I don't have an APU but as far as I can see the TinyCore installer is only for updating the BIOS code on the board. You shouldn't need to use it to install pfSense. The pfSense installer will warn you it's about to reformat the drive but it does not detect the existing version AFAIK.

                Steve

                1 Reply Last reply Reply Quote 0
                • O
                  ozlecz
                  last edited by

                  yes there is that utility there to update the bios…but ive also used that to boot on a usb and install the 2.2 to the msata using gzip...

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

                    Ok, well if you're just un-gziping the file onto the msata disk then there will be no version checking etc. It will simply overwrite whatever is there.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • O
                      ozlecz
                      last edited by

                      just one more thing…i dont know the boot order of the APU...incase it will prioritize the msata, how can i change that to USB? thanks

                      1 Reply Last reply Reply Quote 0
                      • O
                        ozlecz
                        last edited by

                        this is the result of doing the gzip command from the tinyCore.

                        Root mount waiting for: usbus6 usbus3 usbus1
                        uhub6: 4 ports with 4 removable, self powered
                        uhub1: 5 ports with 5 removable, self powered
                        uhub3: 5 ports with 5 removable, self powered
                        ugen6.2: <generic>at usbus6
                        umass0: <generic 0="" 2="" flash="" card="" readerwriter,="" class="" 0,="" rev="" 2.01="" 1.00,="" addr="">on usbus6
                        umass0:  SCSI over Bulk-Only; quirks = 0x4001
                        umass0:0:0👎 Attached to scbus0
                        Trying to mount root from ufs:/dev/ufs/pfsense0
                        WARNING: / was not properly dismounted
                        da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
                        da0: <multiple card ="" reader="" 1.00="">Removable Direct Access SCSI-4 device
                        da0: 40.000MB/s transfers
                        da0: Attempt to query device size failed: NOT READY, Medium not present
                        ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=1710063
                        ad4: TIMEOUT - READ_MUL retrying (0 retries left) LBA=1710063
                        ad4: FAILURE - READ_MUL timed out LBA=1710063
                        g_vfs_done():ufs/pfsense0[READ(offset=875511808, length=53248)]error = 5
                        vnode_pager_getpages: I/O read error
                        vm_fault: pager read error, pid 24 (sh)
                        pid 24 (sh), uid 0: exited on signal 11
                        Jul 30 02:50:35 init: /bin/sh on /etc/rc terminated abnormally, going to single user mode
                        Enter full pathname of shell or RETURN for /bin/sh:
                        ?</multiple></generic></generic>

                        1 Reply Last reply Reply Quote 0
                        • O
                          ozlecz
                          last edited by

                          reinstalled again and here is what ive got

                          Trying to mount root from ufs:/dev/ufs/pfsense0
                          da0 at umass-sim0 bus 0 scbus0 target 0 lun 0
                          da0: <multiple card ="" reader="" 1.00="">Removable Direct Access SCSI-4 device
                          da0: 40.000MB/s transfers
                          da0: Attempt to query device size failed: NOT READY, Medium not present
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2489919
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2490015
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=1243943
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=1710063
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2255727
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2253879
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2258919
                          Configuring crash dumps…
                          Mounting filesystems...
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=3436359
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=934231
                          Setting up memory disks...ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2255527
                          done.
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2258623
                          Disabling APM on /dev/ad4

                          ___
                          / f
                          / p _                          / Sense
                          _                          / 
                              _                          _/

                          Welcome to pfSense 2.1.4-RELEASE  ...

                          Creating symlinks......ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2491295
                          done.
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2803655
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=2943431
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=3133047
                          ad4: TIMEOUT - READ_MUL retrying (0 retries left) LBA=3133047
                          ad4: TIMEOUT - READ_MUL retrying (1 retry left) LBA=3130375</multiple>

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

                            Hmm, well that doesn't look happy. As I said I don't have an APU but I know there were some issues with the mSATA modules originally being supplied by PCengines. ESF/Netgate stopped using them because of this. What mSATA do you have?
                            There appears to be no obvious cause or workaround for this particular error.

                            Steve

                            1 Reply Last reply Reply Quote 0
                            • O
                              ozlecz
                              last edited by

                              well it works straight away during fresh install of 2.2…it si the msata16c (Phison)...the latest version of their msata...maybe it needs formatting before installing...i want to try that but i dont know how...

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

                                Ok, so what are you installing, full or Nano? Which image are you using exactly?

                                The msata16c listed by PCEngines doesn't appear to say 'Phison' on it.  :-
                                Edit: The part number could be one of theirs though.

                                Steve

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

                                  @ozlecz:

                                  i dont know the boot order of the APU…in case it will prioritize the msata, how can i change that to USB?

                                  The boot order can be changed, and saved during bootup of the APU. You need serial console though… press 12 immediately when booting.

                                  @ozlecz:

                                  maybe it needs formatting before installing…i want to try that but i dont know how

                                  Easiest way it to make it boot a live install (install pfSense image on usb stick, boot from that). During pfSense boot, you have options for creating partitions manually, not 100% sure but I would think you can delete them there as well.
                                  Note here: I encountered quite some challenges when manually fiddling with the partitions on a mSata. It was on the other hand very easy to install pfSense if I just let the installer take care of that part… And yes it deletes existing partitions if you take the easy way.

                                  4x XG-7100 (2xHA), 1x SG-4860, 1x SG-2100
                                  1x PC Engines APU2C4, 1x PC Engines APU1C4

                                  1 Reply Last reply Reply Quote 0
                                  • O
                                    ozlecz
                                    last edited by

                                    @stephenw10

                                    =nano install amd64 4g
                                    =msata16c is phison…counterchecked it with another board with vga..it shows on the boot order

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

                                      Just a relabelled drive then.
                                      When 2.1.4 was first released there were some images the weren't correctly labelled, nano+vga labelled as nano. That has been fixed but if you downloaded your image a while ago you may have a bad one. Seems unlikely though.

                                      Steve

                                      1 Reply Last reply Reply Quote 0
                                      • O
                                        ozlecz
                                        last edited by

                                        iam facing the same issue with fresh install on a msata16c
                                        same procedures works on a msata16b

                                        1 Reply Last reply Reply Quote 0
                                        • First post
                                          Last post