PfSense memstick makes partitions automatically



  • Hello people on the internet,

    I've got a small problem when making pfsense 2.4.2 bootable on my USB.

    Everytime I wanna try to make the USB bootable, with Rufus en Etcher, three partitions appear in my USB flash drive. It will happen with Rufus adn Etcher. I also tried to have the non memstick versions, but Rufus and Etcher don't support those versions. Yes, I extracted the .gz file and also tried it with the ISO that was inside the .gz file.

    How is this possible?

    Please help me :-[



  • @Jeanke117:


    How is this possible?

    Ask Rufus ?
    It's the tool that decides how to 'layout' this information.



  • Why did not I create an automatic partition? Can you tell me what to do?



  • @Markynut:

    Why did not I create an automatic partition?

    I don't know why you didn't.
    Why should you ?

    @Markynut:

    Can you tell me what to do?

    No way,
    I take a USB key,
    A pfSense ISO,
    Use Rufus to make a bootable USB,
    Done.

    I never had any reason to think (or understand) it.

    Again : go support Rufus for real advise and explanations - or any other boot USB key maker.



  • What you're seeing is normal, the memstick image has actually four partitions on it pre-configured when the image file is made. One UEFI partition for UEFI booting, one for the freebsd-boot partition to hold the FreeBSD boot code, one for the actual install system and one freebsd-swap partition. The tool that is used to write the image file makes no changes at all to the image nor does it make decisions on how to create partitions on the destination device, the image is written on the memory stick exactly as it is including a new partition table, that's why the partitions are "created" during the writing process.

    Depending on your version of MS Windows you will see those partitions in your windows explorer or your system might not ever recognize the contents after writing the image on the memory stick.

    Don't worry about it.



  • @kpa:

    The tool that is used to write the image file makes no changes at all to the image nor does it make decisions on how to create partitions on the destination device, the image is written on the memory stick exactly as it is including a new partition table, that's why the partitions are "created" during the writing process.

    Humm, I stand corrected then.
    So the "USB Memstick Installer" already contains all this info ?
    And it that case, it's prepared by "pfSEnse" when it is build.



  • @Gertjan:

    @kpa:

    The tool that is used to write the image file makes no changes at all to the image nor does it make decisions on how to create partitions on the destination device, the image is written on the memory stick exactly as it is including a new partition table, that's why the partitions are "created" during the writing process.

    Humm, I stand corrected then.
    So the "USB Memstick Installer" already contains all this info ?
    And it that case, it's prepared by "pfSEnse" when it is build.

    Yes, the image when written on a USB memory stick replaces the contents of the stick completely including any existing partitions, the new partition table is included in the image file and written to destination disk verbatim . In theory it would be possible to prepare images that are written on existing partitions but it's too complicated to prepare such images in a way that they would be easily usable for everyone. That's why the installer images are meant to be written on the whole disk.