SG-2100 23.01 update failed
-
@steveits I've already tried using 23.01 and 22.05. No dice.
-
@bigsy I hadn't thought of that. Might be worth dropping a few pennies on an M.2 SSD just to find out. If it doesn't work, I'm sure I can find a use for it.
-
@mspeculatrix You can, and it will work. Once a M.2 SATA drive is fitted in it, the mmc0 wil effectively be disabled. It might prolong the boot phase though if the mmc0 stops responding all together.
-
@keyser Ok, thanks guys. SSD ordered from Amazon. I've already replaced the SG-2100, but it would be good to have a backup.
-
@mspeculatrix https://docs.netgate.com/pfsense/en/latest/releases/23-01.html#errata-known-hardware-issues
It seems that the PCI BUS won't work when using SG-2100 and 23.01.
-
@mcury Not in issue regarding the M.2 Sata port. Its the SOC’s M.2 SATA feature that drives this.
-
@mspeculatrix said in SG-2100 23.01 update failed:
@keyser Ok, thanks guys. SSD ordered from Amazon. I've already replaced the SG-2100, but it would be good to have a backup.
Did you notice the “speciel” keyed M.2 SATA device needed for the SG-2100? Standard M.2 SATA keyed drives cannot be mounted.
-
@mspeculatrix They are not hard to find, you just need to be aware of this.
-
@keyser said in SG-2100 23.01 update failed:
Not in issue regarding the M.2 Sata port. Its the SOC’s M.2 SATA feature that drives this.
hm, I thought that the M.2 port was PCI and not Sata. Disregard my last post then.
Thanks for the info keyser. -
@keyser Are you sure about that for the 2100? I know it's the case for the 4100/6100.
-
@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.
