Trying to update…. for days now.
-
Anyone know why it's taking days to update to 2.0.2?? Tried the auto and that just wouldn't work so did the manual and it's going at about 1% every 45min.
-
Full install, nano, ..? What exactly is going at 1% every 45 mins?
-
Doing this again with 2.0.3.
Using the nano 512m version.
If I do the auto update, it fails every time but it takes hours to get to the failure.
If I do the manual mode it was saying the file is corrupt, so I figured out that when I tried to download it, it was finishing at 218M. So I did a "right click, save as" and I was able to download it properly but it's still taking forever to upload.
What's going at 1% every 45min is the upload. It shows the progress in the bottom corner.
I'm using Chrome to upgrade, is there anything known to be wrong when using Chrome?I just attached an image showing 11% progress. This is after 2 hrs.
-
Can anyone verify that the nano 512 version is good??
Keeps coming back with a file is corrupt. -
No one????
-
Some CF cards can be extremely slow at writing but not as slow as your experience.
CF cards are relatively cheap, if I were you I'd get another one and write the new image to it directly then restore your config.Steve
-
What I have done in some cases is this:
1. Make sure there is enough space on the slice to hold the upgrade image
2. Go to the shell prompt and run:fetch -o /root/update.img.gz http://wherevertheupdateimageisonthewebsites/pfSense-blah-blah-512m-blah.img.gz
3. Wait for that to finish, that's just downloading the image to your CF.
4. When that is done, back up to the console menu and use the console update function, then by file, and give it /root/update.img.gz
