Upgrade to 2.1.2: Stuck on 2.1
-
Hi,
I tried upgrading from 2.1 to 2.1.2 (I didn't get a chance to upgrade to 2.1.1). After router upgrades, I still end up on 2.1.
I'm on alix board with nanobsd (4g)
Anyone else having this issue?
-
I installed a fresh install of 2.1.1 on an ALIX. Now I updated to 2.1.2 but system seems to be crashed. Don't know exactly what happend, but I can't reach anything on my IP. Have to check via console later this day :(
2.1.2 seems to be broken for ALIX.
-
2.1.2 seems to be broken for ALIX.
Negative. 8 Alix boxes running 2.1.2 ATM. And please do not multipost about the same issue.
-
Go to Diag>nanobsd and check the upgrade log, what does that show?
-
Negative. 8 Alix boxes running 2.1.2 ATM.
and I have 11 Alix/nanoBSD running 2.1.2 - they are working nicely.
-
@cmb:
Go to Diag>nanobsd and check the upgrade log, what does that show?
Showing success upgrade.
Only errors I've noticed where:Misc log: fdisk: invalid fdisk partition table found bsdlabel: /dev/ad0s3: no valid label found bsdlabel: /dev/ad0s3: no valid label found bsdlabel: /dev/ad0s3: no valid label found tar: Failed to set default locale tar: Failed to set default locale shutdown: [pid 90083] -
2.1.2 seems to be broken for ALIX.
Negative. 8 Alix boxes running 2.1.2 ATM. And please do not multipost about the same issue.
Don't know exactly why you deletet my post with error updating my ALIX APU1C to 2.1.2. This thread is a different issue, but ok. I will go on…
After resetting my pfsense because it was stuck on "Reboot after updating firmware", my serial console isn't working anymore. I only can connect via SSH. The connection is fine, because I see the ALIX booting till you can select from what you want to boot. As default I chose F1: pfsense, then it starts to boot up, but nothing more happens.
What to do?
Also strange: I now use a i386 version of pfsense, with 2.1.1 I used the AMD version.
-
0/ I deleted nothing, I'm not even a moderator. Regardless, it has been deleted because you posted two idential posts in two different threads. Just do NOT do that.
1/ APU != ALIX. You seriously are confusing people here. Totally different HW!
2/ Last time I've heard, cross-arch upgrades are not exactly something supported. Why don't you just do a fresh install and restore the config?
3/ The APU is something far from tested as well. -
OK, the APU is from the same manufactor of the ALIX but called different. I will try a fresh install and come back later.
-
I'm seeing the same issue on an ALIX board. The upgrade goes through with no errors reported on screen/console, but when it reboots, it boots back into 2.1. The upgrade log has only the following that appears notable.
fdisk: invalid fdisk partition table found
bsdlabel: /dev/ad0s3: no valid label found
bsdlabel: /dev/ad0s3: no valid label found
bsdlabel: /dev/ad0s3: no valid label found
shutdown: [pid 75726] -
@kaput are you on 4g image?
-
Yes.
-
Can someone test 4g image to see if it's not broken? I had no problems upgrading 2g images, but 4g gives problem.
-
Provide the whole upgrade log. The part being quoted isn't the problem.
We tested the 4GB version more than others, as it's the most common one in use.
-
http://pastebin.com/YX8vK7C1
-
Here's your problem:
gpart set -a active -i 1 ad0 gpart: table 'ad0' is corrupt: Operation not permittedTry this:
gpart bootcode -b /boot/mbr ad0Then try the upgrade again.
-
Thanks, jimp. Missed that perm issue in the log.
Unfortunately, running "gpart bootcode -b /boot/mbr ad0" also results in the exact same error, noting that ad0 is corrupt.
-
I have the exact same issue with same error in my upgrade log on a 2g install on an Alix box.
I also had the issue on a 4g install but I opted to flash a new image and swap cards. The 2g box though is 4 hours round trip away so I would love to fix the issue and update remotely.
I also had another 4g box that updated just fine. So, 2 out of 3 are broken and would not update with autoupdate or manual update.
-
Other things to try:
Set the boot slice on Diagnostics > NanoBSD, see if it actually changes.
or
gpart recover ad0or
sysctl kern.geom.debugflags=16 boot0cfg -v -s 1 ad0 fdisk -a /dev/ad0 sysctl kern.geom.debugflags=0(For fdisk make sure to specify the values it asks and press 'y' to confirm!)
We have yet to be able to reproduce this effectively, but several people have hit it. It would be helpful to know some more about the original setup that failed. Was it your own CF or did it come with the device? Had it ever been upgraded before, and if so how many times? What was its original version of pfSense on that CF card before upgrading?
-
Slice does not change; nor I can copy ad0s2 -> ad0s1.
