2100 SSD install steps

terryzb

I purchased a 128GB Kingspec B+M key M.2 SATA SSD to upgrade a Netgate 2100 and would like to confirm the steps for the hardware and software install.

Remove big packages (only pfBlockerNG for me)
Save config locally
Create USB installer with 2100 file from Netgate https://docs.netgate.com/reference/create-flash-media.html
Copy the config.xml saved in step 2 to the USB
Shut down the 2100 and wait 60 seconds
Remove the cover and install the SSD https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/m-2-sata-installation.html
Reinstall the cover
Plug-in the USB installer
Connect USB cable for a 'screen' terminal
Boot 2100 and install to the ada0 drive https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/reinstall-pfsense.html
After installation, remove the USB and reboot

Will the original MMC storage automatically be wiped?
When I reinstall pfBlockerNG it will use the config that was saved?
Are there any steps I missed?

SteveITS

@terryzb re wipe, see the Caution at the bottom of https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/reinstall-pfsense.html#install-pfsense-plus-software

No need to uninstall anything if you are installing clean, the restore will install the packages.

I haven’t used the new installer yet…

terryzb

@SteveITS Thank you for the heads up on disk wiping and the info on not needing to uninstall packages.

I thought I recalled @stephenw10 saying that the new installer would wipe the MMC but I can't find that thread.

If the new installer doesn't to this, at what point in the steps above should the MMC be wiped?

stephenw10

When you enter run usbrecovery in uboot it erases the eMMC to prevent any conflicts with any existing filesystems. That happens whatever is booted from USB.

terryzb

@stephenw10 Thank you Stephen!

stephenw10

Just for reference you can also: run recovery if you want to boot USB without erasing the eMMC. That allows for some fun custom setups! Most users should not do that though.

terryzb

@stephenw10 Thanks. I definitely don't have the Jedi rating for that.

terryzb

@stephenw10
Well, usbrecovery wasn't the smoothest of experiences. The installer phrasing and UI in some places was confusing. Since it's a 2100 I pressed Enter for the defaults and hoped for the best.

One question required a spacebar to select the drive instead of just highlighting. I did not notice any on-screen instructions about this so luckily I'd done enough Linux installs to recognize the "[ ]" and spacebar convention.

At the end of the install, the "OK" text was missing the "O" and most of the "K" making it look like a "<" so I thought it might still be installing and didn't realize for 15 minutes that it was an "OK" and waiting for an Enter.

I assumed that the config.xml would be copied to the 2100 and didn't realize that the USB installer needs to remain plugged into the unit for the config to be read after the reboot so it was essentially a fresh install. I correctly guessed the WAN and LAN interface names (mvneta0 and mvneta1) and set an admin password, then changed the LAN IP so I could login to the GUI and manually restore the config from backup.

After restoring the config and rebooting, the GUI dashboard said,

Packages are currently being reinstalled in the background.
Do not make changes in the GUI until this is complete.
If the above message is still displayed after a couple of hours, use the 'Clear Package Lock' button on the Diagnostics > Backup & Restore page and reinstall packages manually.

I waited about 2 hours, the CPU was idling at 15% and Installed Packages said, "No packages installed." There was no "Clear Package Lock" on the Backup & Restore page.

Configuration History showed:

8/3/24 16:53:29	(system): Removed pfBlockerNG package.	23.3	160 KiB	
8/3/24 16:53:20	(system): Removed Avahi package.	23.3	161 KiB	  
8/3/24 16:53:11	(system): Removed OpenVPN Client Export Utility package.	23.3	161 KiB	  
8/3/24 16:52:55	(system): Removed System Patches package.	23.3	162 KiB	  
8/3/24 16:52:32	(system): Removed ipsec-profile-wizard package.	23.3	162 KiB	  
8/3/24 16:52:21	(system): Intermediate config write during package removal for ipsec-profile-wizard.	23.3	162 KiB	  
8/3/24 16:52:00	(system): Overwrote previous installation of IPsec Profile Wizard.	23.3	163 KiB	  
8/3/24 16:51:51	(system): Intermediate config write during package install for IPsec Profile Wizard.	23.3	162 KiB	  
8/3/24 16:51:38	(system): Intermediate config write during package removal for ipsec-profile-wizard.	23.3	162 KiB	  
8/3/24 16:51:09	(system): Configured default pkg repo after restore	23.3	163 KiB

So I manually installed the packages, applied System Patches and rebooted.

Installing the SSD was 5 minutes but reinstalling and getting the 2100 to boot with the correct config and packages was several hours.

So I believe the updated steps should be:

Save config locally
Create USB installer with 2100 file from Netgate https://docs.netgate.com/reference/create-flash-media.html
Copy config.xml saved in step 2 to the USB
Shut down the 2100 and wait 60 seconds
Remove the cover and install the SSD https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/m-2-sata-installation.html
Reinstall the cover
Plug-in the network cables
Plug-in the USB installer
Connect USB cable for a 'screen' terminal
Boot the 2100, connect via 'screen' terminal.
For me, $ sudo screen /dev/cu.usbserial-1234 115200, -ixon
Hit a key to interrupt the boot, then 'run usbrecovery' https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/reinstall-pfsense.html
Choose the ada0 drive to install onto
After installation, reboot with the USB still inserted to pick up the config.xml

stephenw10

You can select the config to use during the install instead of pulling it in at the first boot with the ECL:
https://docs.netgate.com/pfsense/en/latest/install/install-walkthrough.html#install-config-recovery

JonathanLee

@terryzb I also use the Kingspec it is a great product. I also added a SSD heat sink to it to keep it cool.

terryzb

@stephenw10 Hi Stephen. I did select the config during the install.

terryzb

@JonathanLee Is this necessary? Can you share a link of what you installed?

stephenw10

No you don't need to add a heatsink. We have never fitted one and don't see issues with heat. Unless maybe you have some drive that runs especially hot or is designed to use a heatsink. I'm not aware of any but someone may have produced one.