Invalid Signature for a RELEASE image
-
Is there something I can clean in the / FS in order to be able to upgrade to 2.1 ? :-[
( my appliance always ran the original pfSense images – no addons whatsoever --, and I'm surprised to run out of space )
-
Do you have any packages installed? If so, uninstall them
-
I don't have any packages installed ( I'm running a stock 2.03 version of pfSense ) on my appliance
What can I do to be able to upgrade to 2.1 ? :-[
-
Hmm, odd, you can't be the first person with a 512MB Nano install to try to update.
You could always flash 2.1 clean onto the card and restore your config aftwerwards. Bit inconvenient though. It would give you an opportunity to upgrade to a bigger card at the same time.
Steve
-
Yes indeed, I have tought about this.
But as you've written, it is really odd, running a stock pfSense on a 512MB CF, not being able to upgrade to a version that supposely fits that kind of support ( including an upgrade procedure ) :o
That's why I'm also trying to understand what is taking the extra space I'm missing ( could the RRD graphs data be the reason ? )
-
Have you ever run any packages on that box?
It seems more likely that the space is taken up by the remains of a previous failed update. :-\ Just speculating there though.Steve
-
I Never ran any packages on that box.
There are 43MB available on the /cf FS. If I could add that to the 50MB available on the /, I would have enough to fetch the upgrade image ( ~ 76MB ).
Filesystem Size Used Avail Capacity Mounted on
/dev/ufs/pfsense1 215M 148M 50M 75% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/md0 38M 258K 35M 1% /tmp
/dev/md1 58M 15M 38M 28% /var
/dev/ufs/cf 48M 1.5M 43M 3% /cf
devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev -
You can't add the conf slice to the main slice in use. The best you could so, if you went that route, would be to increase the size of /tmp. However you would have to then reconfigure it to use /tmp for the download and you might run out of memory anyway.
Here's a suggestion. Try switching to the other slice in Diagnostics: NanoBSD:. The other slice probably has 2.0.2 on it but you should be able to upgrade to 2.1 directly from that. Since you were able to upgrade to 2.0.3 it must have had at least 66.4MB of space.
Steve
-
I hit this today as well on a client. I took an axe to a bunch of files until I had enough space to upgrade, but it worked once I freed up 80MB of disk space.
Seriously though the best solution is to replace the 512MB card/image with something much bigger, 4GB should do it.
-
I've run into space issues before - I would delete all packages AND reset the RRD data to clean out all the saved graph data too - even if you're not using RRD now it's still a good idea to clean out the data if you've ever used it in the past.
Then upgrade. When you've upgraded, add the packages back in but install the bigger packages first (ie Avahi) and the smaller packages last (blinkled etc). CF cards are cheap these days so there's no reason not to have a 4Gb card but you can run out of RAM as well as disk space so a larger CF card isn't necessarily going to solve your problems.
