Installation of 2.4.1 Memstick (weird installation procedure, should be known)

  • I'm not sure if I'm the only one, but installing 2.4.1 was inconsistent with the current set of instructions.

    In the installation menu, after selecting the keyboard mapping and 'Install', I was presented with a series of parition options (as expected).

    I selected the 'auto(ufs)' partition option, then a popup screen came up with a series of partitions containing no mountpoints. I had to manually delete all the partitions (except for the current ufs, as this was the live installer) and re-create new partitions.

    On a 16gb usb, I was only able to create a 1gb partition and then manually add the / (root) mountpoint in the available menu.

    It then asked me if I wanted to create an accompanying boot partition, which was required, to which I said yes. After this I was able to press 'Finish' and it would install.

    Prior to that, if I just pressed 'Finish', it would throw an error about requiring the boot partition to have a root mount-point. However, if I added said root mount-point to the existing ufs partition it would fail (for obvious reasons).

    This was an image downloaded from the Singapore mirror, AMD64 memstick. I used Rufus to install to the usb, after unzipping the .gz file.

    This procedure has not been detailed anywhere, that I can find, and perhaps should be known. Unless, of course, this was a rogue image that somehow escaped the clutches of the QA team.

    Thanks :)

  • Honestly, it sounds like a normal installation…you should have not needed to do a manual install. I just recently did the same installation on a 16GB SSD selecting the auto you described...I just let the installer do its thing.

  • Rebel Alliance Developer Netgate

    That doesn't happen here when choosing the auto options. It sounds to me like it either went into the manual install or something was wrong with the existing disk layout that auto couldn't handle.

Log in to reply