Project

General

Profile

Bug #429

Upgrade failed from console disk full!

Added by Oscar Francia about 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Category:
Upgrade
Target version:
Start date:
03/15/2010
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

/root/firmware.tgz 76% of 81 MB 135 kBps 02m26s
/: write failed, filesystem is full
/root/firmware.tgz 76% of 81 MB 135 kBps 02m24s
fetch: /root/firmware.tgz: No space left on device

Warning: filesize(): stat failed for /root/firmware.tgz in /etc/rc.initial.firmware_update on line 58

File size mismatch. Upgrade cancelled.

History

#1 Updated by Oscar Francia about 9 years ago

I's embedded image 512Mb
df -h
Filesystem Size Used Avail Capacity Mounted on
/dev/ufs/pfsense0 215M 153M 45M 77% /
devfs 1.0K 1.0K 0B 100% /dev
/dev/md0 38M 4.0K 35M 0% /var/tmp
/dev/md1 58M 6.3M 47M 12% /var
/dev/ufs/cf 49M 39K 45M 0% /cf
devfs 1.0K 1.0K 0B 100% /var/dhcpd/dev

#2 Updated by Erik Fonnesbeck about 9 years ago

I use the 512 MB image on an Alix 2c3 and see the same type of thing when attempting an upgrade from the web gui in 2.0.

#3 Updated by Ermal Lu├ži about 9 years ago

  • Status changed from New to Feedback

Can you please test with latest snapshots which have debugging removed?

#4 Updated by Erik Fonnesbeck about 9 years ago

Yeah, 76% of 81 MB is about 61.5 MB and the new snapshots are smaller than that, so it might work at least on a system without any packages using up that space with things.

#5 Updated by Oscar Francia about 9 years ago

I've tested from web interface and the error is this I've tested from snapshot 03-05-2010 and from snapshot 12-05-2010 to 13-05-2010 nanobsd 1Gb :

May 12 19:41:42 php: /system_firmware.php: The command '/usr/local/sbin/gzsig verify /etc/pubkey.pem < '/root/firmware.tgz'' returned exit code '2', the output was 'No gzip signature found Couldn't verify input'
May 12 19:42:11 php: : New alert found: Upgrade failed due to the upgrade image being larger than the partition that is configured on disk. Halting. Size on disk: 450 < Size of new image: 950

#6 Updated by Jim Pingle about 9 years ago

That last message seems to indicate you were trying to load a 2G update onto a CF originally written with a 1G image.

#7 Updated by Oscar Francia about 9 years ago

Jim P wrote:

That last message seems to indicate you were trying to load a 2G update onto a CF originally written with a 1G image.

No, the CF is 1Gb and update is 1gb!

#8 Updated by Erik Fonnesbeck about 9 years ago

Do you mean that the uncompressed size is around 1 GB or that you used the image for the 1 GB NanoBSD platform? The uncompressed size of the update image for the 1 GB platform is a little under half a GB and the update image for the 2 GB platform is a little less than 1 GB.

#9 Updated by Oscar Francia about 9 years ago

Erik Fonnesbeck wrote:

Do you mean that the uncompressed size is around 1 GB or that you used the image for the 1 GB NanoBSD platform? The uncompressed size of the update image for the 1 GB platform is a little under half a GB and the update image for the 2 GB platform is a little less than 1 GB.

I used image: pfSense-2.0-BETA1-1g-20100513-1550-nanobsd.img.gz :)

#10 Updated by Jim Pingle about 9 years ago

That is a full image, not an upgrade image. You need, for example, pfSense-2.0-BETA1-1g-20100517-0921-nanobsd-upgrade.img.gz

#11 Updated by Erik Fonnesbeck about 9 years ago

It seems you probably did already at least get past the part where the image was too large to upload, so this is probably sort of worked around by the decreased size of newer images, though it would be nice to have a proper fix for this sometime in the future.

#12 Updated by Chris Buechler almost 9 years ago

  • Status changed from Feedback to Resolved

Also available in: Atom PDF