Navigation

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

    [Solved] Unbootable after Writing Disk Images to USB 2.3.3-RELEASE

    Installation and Upgrades
    3
    6
    773
    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.
    • C
      CaladorGCS last edited by

      I can't get the pfSense-CE-memstick-2.3.3-RELEASE-amd64.img.gz file to load on a USB. Same experience with the i386 version and the ICO image.

      I've tried Rufus, Win32 Disk Imager, UNetbootin, and Etcher.
      3 different USB drives have been tried.
      3 different computers were tested, all unsuccessful at booting the drive.
      I've cleaned the USB Drive every time I experienced a failure.
      I've tried both WinRar and 7-Zip to uncompress the files.
      Followed every step like clockwork and all the SHA2 Checksum's check out…

      The results: It creates 24 MB partition every time for the amd64 and  i386 and the ICO declares it to be unbootable. I contacted an experienced pfSense user and he went through the same process on an Apple OS with the same results.

      As a side note, it's not inexperience and the issue has been Peer-Reviewed. If you attempt downloading the 3.3.3-Releace in i386, amd64, or the ICO image and try making a bootable USB you'll experience what I'm talking about. I can install Ubuntu Server using the same procedure flawlessly - but not pfSense. Thanks for any assistance...

      pfSense or Bust!

      pfSense© running on…

      • CPU: Intel Core i5-5250U Processor (3M Cache, up to 2.70GHz, Broadwell) + Intel 4 GBit LAN

      • Configuration: RAM 8GB DDR3; SSD 128GB; AES-NI; Hyperthreaded; Model: Qotom-Q355G4

      Switch - NETGEAR ProSAFE JGS516PE 16-Port Gigabit PoE WM (Plus) & GS105Ev2 5-Port WM (Plus)
      Access Point - (2) Unifi 802.11ac Dual-Radio PRO

      1 Reply Last reply Reply Quote 0
      • dotdash
        dotdash last edited by

        I downloaded the 2.3.3 x64 memstick shortly after it was released, and it works fine for me.
        I used a Win10 pc and these steps-
        Open a cmd as Administrator
        Insert the usb stick
        run diskpart, clean the usb drive
        physdiskwrite -u pfSense-CE-memstick-2.3.3-RELEASE-amd64.img.gz

        Just threw it into an old Lenovo Thinkcenter and it booted right up.
        Checksum on the file I have, calculated with 7zip, matches the SHA256 on the download page.

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

          And make sure you are NOT trying to boot from UEFI. Will not work at all with 2.3

          1 Reply Last reply Reply Quote 0
          • C
            CaladorGCS last edited by

            @dotdash:

            I downloaded the 2.3.3 x64 memstick shortly after it was released, and it works fine for me.
            I used a Win10 pc and these steps-
            Open a cmd as Administrator
            Insert the usb stick
            run diskpart, clean the usb drive
            physdiskwrite -u pfSense-CE-memstick-2.3.3-RELEASE-amd64.img.gz

            Just threw it into an old Lenovo Thinkcenter and it booted right up.
            Checksum on the file I have, calculated with 7zip, matches the SHA256 on the download page.

            Ya, I've been doing all the right stuff. Not sure but I think the file might have changed since the pfSense 2.3.3-p1 RELEASE and maybe thats it? The file name after uncompressing is not pfSense-CE-memstick-2.3.3-RELEASE-amd64.img.gz it's pfSense-CE-memstick-2.3.3-RELEASE-amd64.img <– Not sure if that makes a difference?

            pfSense© running on…

            • CPU: Intel Core i5-5250U Processor (3M Cache, up to 2.70GHz, Broadwell) + Intel 4 GBit LAN

            • Configuration: RAM 8GB DDR3; SSD 128GB; AES-NI; Hyperthreaded; Model: Qotom-Q355G4

            Switch - NETGEAR ProSAFE JGS516PE 16-Port Gigabit PoE WM (Plus) & GS105Ev2 5-Port WM (Plus)
            Access Point - (2) Unifi 802.11ac Dual-Radio PRO

            1 Reply Last reply Reply Quote 0
            • dotdash
              dotdash last edited by

              @PingTheNet:

              The file name after uncompressing is not pfSense-CE-memstick-2.3.3-RELEASE-amd64.img.gz it's pfSense-CE-memstick-2.3.3-RELEASE-amd64.img <– Not sure if that makes a difference?

              I never bother un-gzipping (gunzipping?) the file, try using physdiskwrite to write the img.gz directly.

              1 Reply Last reply Reply Quote 0
              • C
                CaladorGCS last edited by

                @doktornotor:

                And make sure you are NOT trying to boot from UEFI. Will not work at all with 2.3

                Oh, yep just Checked It is UEFI

                Awesome, Thank you so much! I see the pfSense setup screen! Thank you everyone for looking out!  :D

                pfSense© running on…

                • CPU: Intel Core i5-5250U Processor (3M Cache, up to 2.70GHz, Broadwell) + Intel 4 GBit LAN

                • Configuration: RAM 8GB DDR3; SSD 128GB; AES-NI; Hyperthreaded; Model: Qotom-Q355G4

                Switch - NETGEAR ProSAFE JGS516PE 16-Port Gigabit PoE WM (Plus) & GS105Ev2 5-Port WM (Plus)
                Access Point - (2) Unifi 802.11ac Dual-Radio PRO

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