Unable to invoke auto update
-
I have a NetGate m1n1wall 2D13 pfSense box that I got about 2 years ago. Currently it's running 2.1-RELEASE, and I'm trying to use the auto update to go up to 2.1.4-RELEASE. I've tried this a few times, but after the reboot it's showing the same version.
As far as specs, I ran a "sysctl hw.physmem" command and it shows 256MB of RAM. For platform it shows up as "nanobsd (4g)" in the web interface, and here's what I have for disk space (I think it's a 4GB CF card):
Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ufs/pfsense0 1890014 168926 1569886 10% / devfs 1 1 0 100% /dev /dev/ufs/cf 50527 3336 43149 7% /cf /dev/md0 39406 180 36074 0% /tmp /dev/md1 59246 18446 36062 34% /var devfs 1 1 0 100% /var/dhcpd/devI assume my pfSense box has the proper specs to even support an update, correct? And assuming that's the case, is there a reason why the auto update is not working on my pfSense box?
-
Yes, that should upgrade fine.
Check the upgrade log in Diagnostics: NanoBSD:
You could try upgrading from the console which should give you more info about why it isn't upgrading.
You might be stuck in this condition: https://forum.pfsense.org/index.php?topic=75069.0Worst case you might have to re-flash the CF card externally.
Steve
-
Thanks for the information. The nanobsd logs provided me with the "gpart: table 'ad0' is corrupt: Operation not permitted" message. Reading on that for a while has lead me to the conclusion that attempting to fix the corruption will probably not work. I'm going to buy another SLC CF card, image that, and then replace the one that's in there. That way I'll have a backup for future issues.
-
That's the safest way. :)
Steve
-
Thanks for the information. The nanobsd logs provided me with the "gpart: table 'ad0' is corrupt: Operation not permitted" message. Reading on that for a while has lead me to the conclusion that attempting to fix the corruption will probably not work. I'm going to buy another SLC CF card, image that, and then replace the one that's in there. That way I'll have a backup for future issues.
If you're using NanoBSD there isn't any real need for a SLC card. I only use those for full installs.
-
+1.
Good point I missed that.Steve
-
I thought I read that SLC CF cards could take more read/writes, so I bought a Dane-Elec 8GB CF card from Amazon last night.
In the meantime, I will read up on flashing the card with the image. I just wanted to know if there's any way to copy my current config on the card after imaging but before putting the card in the pfSense box.
-
I thought I read that SLC CF cards could take more read/writes, so I bought a Dane-Elec 8GB CF card from Amazon last night.
In the meantime, I will read up on flashing the card with the image. I just wanted to know if there's any way to copy my current config on the card after imaging but before putting the card in the pfSense box.
Writes, yes, but NanoBSD has minimal writes. It's basically designed to work with low-end, unreliable cards.
-
There's no problem using an SLC card they're just more expensive and unnecessary for Nano.
You can write the config file into the config slice on the new card but you'll have to mount it on something that understands UFS. That's usually a FreeBSD box but could be a live cd like ghostbsd.
Steve
-
I finally got around to this upgrade by swapping with a different CF card, but that was definitely a pain to deal with. For a Netgate m1n1wall, you have to take out the 4 cover screws, the 4 screws that hold the board to the case, and the 2 nuts that hold the serial port connector in the back. Only then can you remove the board from the case just to swap out the CF card. After that, it was just importing the backup config and allowing it to reboot one last time. I know it bugged me just having to do this once, but I just feel bad for any admins that may have purchased these for multi-site implementations.
Anyways, it's all good now. Thanks for everyone's help! 8)
