Project

General

Profile

Bug #1149

nano build - upgrade size failure on USB flash drives

Added by Richard Illes about 8 years ago. Updated almost 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/02/2011
Due date:
% Done:

0%

Estimated time:
Affected Version:
Affected Architecture:

Description

Fresh USB key I loaded 12/29 nano 1G or 2G image on it.

- on reboot, the dashboard prompted me to upgrade to 12/30 build, clicked on the invoke button, it downloaded it and said it installed it.
- refresh the webgui and the system log has the error:

"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: 448 < Size of new image: 450"

for a 2G build the error is: "....Halting. Size on disk: 926 < Size of new image: 928"

It seems for every image I have tried it is 2 'blocks' too small then the image on the USB key. The USB key was imaged with physdiskwrite-0.5.2 and the initial image was downloaded from: /FreeBSD_RELENG_8_1/i386/pfSense_HEAD/nanobsd.

- issue does not appear to happen on CF drives.

http://forum.pfsense.org/index.php/topic,31489.0.html

History

#1 Updated by juan peridot almost 8 years ago

newbie on bsd and pfsense.

filed a bug week or so ago, got rejected. found this, exactly my problem.

currently using a 2g nanobsd image in a new 4g usb flash drive. same upgrade failure 926 < 928, it is always 2 off! i don't think the new 4g flash drive have 50% defects since the 2g image was installed.

have tried 4g image on 4g flash drive, same 2 off!

#2 Updated by juan peridot almost 8 years ago

newbie on bsd and pfsense.

filed a bug week or so ago, got rejected. found this, exactly my problem.

currently using a 2g nanobsd image in a new 4g usb flash drive. same upgrade failure 926 < 928, it is always 2 off! i don't think the new 4g flash drive have 50% defects since the 2g image was installed.

have tried 4g image on 4g flash drive, same 2 off!

#3 Updated by Jim Pingle almost 7 years ago

  • Status changed from New to Closed

I added some fixes for this a while back (before 2.0), it should be fine now.

Also available in: Atom PDF