SG-2100 23.01 update failed
-
@keyser I read this: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/m-2-sata-installation.html
It says nothing about special keying - just that it has to be a 2242 and not NVMe.
-
@mspeculatrix I have a factory fitted 32GB m.2 sata in a 2100. I haven't opened the case to see what it looks like. Smartctl reports it as
ATP SATA III M.2 2242 -
Yeah a standard 42mm m.2 SATA drive should fit in the 2100. And yes that should work fine if the eMMC is dead for whatever reason.
Steve
-
@mspeculatrix said in SG-2100 23.01 update failed:
@keyser I read this: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/m-2-sata-installation.html
It says nothing about special keying - just that it has to be a 2242 and not NVMe.
Ahh, right, it was the NVMe drive in my 6100 that required a special key’ing. Sorry about that :-)
Then it’s just a standard 2242 M.2 Sata SSD -
@bigsy said in SG-2100 23.01 update failed:
@keyser Are you sure about that for the 2100? I know it's the case for the 4100/6100.
Yes, perfectly sure. If the PCI not working invalidated the M.2 slot, all of Netgates factory sold MAX models with 32Gb SSD would be impacted as well.
-
@keyser I was referring to your comment re the keying on the m.2 sata
-
@bigsy From all these posts this is what I infer:
Install a M.2 Sata Drive in SG-2100 and re-install the pfSense
Plus software on the new M.2 SATA drive.What I would like to do (not sure this is feasible):
-
Buy a M.2 Sata drive
-
Install the pfSense software on this drive (M.2 Sata is stand alone not installed in SG-2100)
-
Whenever the pfSense update goes south open the SG-2100 and install the M.2 with pre-installed PfSense
Will the above work?
-
-
@netboy Reinstall on the new drive inserted in the 2100.
-
@bigsy I want to re-install directly into the M.2 stand alone (M.2 is not installed in SG-2100) - Possible?
-
Technically it could be done since the recovery media just copies an image onto the target disk. Just extract the image from the recovery image and write it to the drive.
But it would be much easier just to write it to the drive in the 2100. -
@stephenw10 Thank you.
This is my understanding....Please confirm.
In case my 2100 update goes south I can recover to stock pfsense plus software directly to 2100 (without M.2) flash memory. To do this:
-
I need to request the software using support ticket,
-
Flash a USB using the download from above
-
Then try to install it using guide
-
Once the pfsense plus is installed RESTORE BIN back up image
Is the above process correct? Are the URL links I provided above correct?
Can I go ahead of do the updates to 23.01? Will it go south on me?
-
-
@netboy said in SG-2100 23.01 update failed:
Then try to install it using guide
That's the console connection, which you'll need, but also https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/reinstall-pfsense.html
Otherwise yes. Make a backup/download of your config first.
Once the pfsense plus is installed RESTORE BIN back up image
Not sure I understand this? Always have a backup. You can always request firmware before upgrading.
-
@steveits Yes I always take a backup (BIN) if I make any changes or do updates. Thanks for the URL.
For the record do ALL updates to 23.01 fail or only some? Has netgate ISOLATED the ones that fail and corrected the udpates?
-
@netboy See thread https://forum.netgate.com/topic/178007/update-2100-to-23-01-advice/7, seems Netgate can't replicate it yet. I know of at least one other forum user who posted it worked (and, generally people post about problems, not when something works as expected). I haven't tried yet, need to wait until my wife and son aren't using it. :)
-
@steveits said in SG-2100 23.01 update failed:
I haven't tried yet, need to wait until my wife and son aren't using it. :)
I always have a backup plan if router fails....Have a travel router to which I can connect my phone USB (hotspot) and my whole network will have internet. Not the best speed but at least can be connected.
IMHO it is always better to have a plan BEFORE shit hits the fan.
I will probably wait to do my updates.
-
Anyone know if I cant mount a copy of the config and back it up via usb console if on the 'Marvell>>' shell? Of course I forgot to make a backup after making changes, so I think I only have an older backup
Updated to 23.01 to find a failed reboot with the pleasant messages already mentioned here. If curious I got:
/*
...
efi_load_pe: Invalid DOS Signature
...
Reset SCSI
scanning bus for devices...
** Bad device scsi 0 **
resetting USB..
*/ -
@charliebrauw curious when did you buy your SG-2100 - Is there relationship between 23.01 failure on purchase date?
(...off course we also need those who were successful as well.)
Hopefully people can post the date purchased, 23.01 success or fail info in this forum. -
Yes your procedure there is correct.
Try running at the command line:
gpart showIf the EFI partition is shown as 200MB or more I would say it's extremely unlikely you will see an upgrade problem. Though at this point it's a theory since we've still not replicated it locally.
Just to be clear every upgrade test I've run has completed successfully.
Steve
-
@netboy
Purchased 05/15/2021 -
@charliebrauw
My purchase date is 10-25-2022 (not yet updated to 23.01)
