2.3.1_1 Update completly borked
-
I suggest you don't storm in here with a rant. That is not going to ingratiate you to anyone. Bear in mind that many, many thousands of pfSense installs and upgrades work flawlessly. I have personally updated 20 odd so far.
What the hell does "kill the slice" mean?
What hardware - bugger your signature: spell it out?
What version prior to 2.3.1?
How did you get to 2.3.1 if it was broken on update?Calm down and let's see if we can help you.
Cheers
Jon -
I've just done a 2.3.1 -> 2.3.1_1 update on the router between you and me.
Earlier tonight (GMT+1) I finally got around to update i386 -> amd64 on a NanoBSD install. I had previously upgraded 2.3.1 to 2.3.1_1 on i386.
However the installer is still 2.3.1. I dumped the config, wrote a new CF card, put it in and booted, messed with VLANs, addresses etc, put the previous config in and restarted it. Then I ran the upgrade 2.3.1 -> 2.3.1_1.
I didn't even notice the drop because I was still writing the above comment.
-
I already said sorry…
Box is atm at 2.3.0
2.3.0 -> 2.3.1 did not work
2.3.0 -> 2.3.1_1 did not work either
the 2.3.1_1 is the only available updateHardware: 2.3-RELEASE (amd64) on Intel D2500CCE Board Intel Atom D2500 DC @1.86GHz, 2GB RAM, 32GB CF Card with NanoBSD (4GB)
Both (2.3.1 and 2.3.1_1) killed the second slice of the nano bsd installation as the update took place there.
-
Did you try to save your config reinstall with 2.3.1 and then update to 2.3.1_1?
Had some troubles here with a 32gb cfcard also (2.3.1-> 2.3.1, but 2.3.1-> 2.3.1_1 worked). 4gb and 8b worked ok.
-
Looks like the disk itself is not able to be read, or at least the filesystem. Personally I would not trust the card/disk at this point. At a minimum it should have some diagnostics run and a full dd style zero wipe of the entire disk before it's used again.
The vast majority of unexplained cases such as this – especially with flash media -- end up being failing disks.
CF is cheap, just get a new one.
Or use the opportunity to upgrade to a real SSD and ditch NanoBSD as well.
-
I have 2500CC and SSD installed, AHCI mode, no problem at all with updates. For me it looks like CF problem as jimp mentioned or some kind of compatibility issue that I have had with an older BIOS version.
-
The CF Card is absolutly fine.
Clone Slice from running system does not throw any errors.
Second slice boots perfect after clone…
Only the update does not work ;-)PS: If you wanna let nano bsd die then say so ;)
-
We have said so. It's going to be dead in 2.4 (though 2.3.x will live on for a while even after 2.4 releases)
Just because cloning a slice works does not mean the CF is fine. The clone action could have triggered remapping on the CF to mask failing areas.
It's still worth using a fresh CF. And I still wouldn't trust it.
-
We have said so. It's going to be dead in 2.4 (though 2.3.x will live on for a while even after 2.4 releases)
Just because cloning a slice works does not mean the CF is fine. The clone action could have triggered remapping on the CF to mask failing areas.
It's still worth using a fresh CF. And I still wouldn't trust it.
No Pun intended here..
I have ordered a SSD Yesterday and will reinstall tonight.. -
We have said so. It's going to be dead in 2.4 (though 2.3.x will live on for a while even after 2.4 releases)
Just because cloning a slice works does not mean the CF is fine. The clone action could have triggered remapping on the CF to mask failing areas.
If nano dies i have to shredder my alix? Or is there a way to use a usb stick?
-
If nano dies i have to shredder my alix? Or is there a way to use a usb stick?
You can keep running whatever the last release is that has NanoBSD. Current plan is to keep maintaining that branch for a while. IIRC when we drop NanoBSD, i386 is also being dropped, so either way the ALIX can't move forward. It's past time to be seeking a replacement for that hardware, it's been EOL for some time now.
