very slow upgrading
-
@stephenw10
I update rarely, once a year, today I updated from 2.7.0 to 2.7.2 for 40 minutes, it downloads quickly, then reboots and takes a long time to install. And this despite the fact that there were no packages installed there at all. A year ago it also took a very long time to update. I’m starting to think maybe 100 gigs isn’t enough for him when updating. -
I upgraded a box from 2.7.0 to 2.7.2 on Thursday and it was running in 4GB.
It took a long time, over an hour, but that was mostly because it's running from a CF card and it's incredibly slow. Your drive should not see anything like that restriction.
-
@Cergo is DNS working on pfSense itself? IPv6 enabled or disabled?
-
@SteveITS running dns resolver and set Allow IPv6
-
@Cergo does it work though? Diagnostics/DNS Lookup succeeds using both?
Upgrades on eMMC storage normally don’t take more than 10-15 minutes so 1-2 hours seems absurdly slow.
-
@SteveITS The download is fast, but then after a reboot the unpacking and installation is very slow.
-
Next time when you upgrade, while upgrading, open a console, or SSH, option 8 and run 'top' during the upgrade.
You'll see what process is so slow ...You didn't tell anything about the hardware used.
If the processor used is a 6502, your system is actually very fast
Or, as said above, depending the hardware storage used, some time can be needed to write out all the file.
For reference : my 4100 Max : updating was as fast as downloading : a minute or two maybe. -
@Gertjan top during installation
, I will try.
my system it's old hp proliant
Intel(R) Xeon(R) CPU E5530 @ 2.40GHz
16 CPUs: 2 package(s) x 4 core(s) x 2 hardware threads
AES-NI CPU Crypto: No
QAT Crypto: No -
.... and the drive is ? I get it, probably not a "eMMC" or a "CF" card.
The disk is in a clean state ?
Does it boot normally ? -
@Gertjan sas raid1
-
@Cergo said in very slow upgrading:
then after a reboot the unpacking and installation is very slow.
Hmm, that seems odd. Hard to see how that could be anything but a drive issue.
Unless maybe it's a decompression issue, trying to use some hardware offloading that isn't correctly supported.
