Upgraded Netgate FW-7541 to 2.4.0 and now it won't boot.



  • I upgraded our LAB Netgate FW-7541 pfsense box from 2.3.4-p1 to 2.4.0 this afternoon. After the reboot I was no longer able to communicate with the firewall. I connected to the unit through the console and see the error:

    Mounting from UFS:/dev/ad4s1a failed with error 19.

    I've attached a picture of the screen since I didn't have internet access at the time since my device was behind the firewall.

    Is there a simple solution to fix this issue or do I need to just reinstall? I saw in the release notes that there could be issues with bios/hardware but I didn't think the Netgate hardware would be affected.

    Any advise would be appreciated. Thanks.

    [Edit]
    Looks like there is another thread open about this, sorry I missed it.

    https://forum.pfsense.org/index.php?topic=137929.0

    I'll try the suggestion there and update on that thread.



  • I think pfsense is accidentally (oooops) obsoleting a whole lot of perfectly capable hardware.


  • Rebel Alliance Developer Netgate

    @kejianshi:

    I think pfsense is accidentally (oooops) obsoleting a whole lot of perfectly capable hardware.

    No, it has nothing to do with that. The /etc/fstab file is referring to old device names that no longer exist. It would have broken the same way on 2.3 but FreeBSD added legacy aliases to let the old names keep working. They removed those aliases in FreeBSD 11

    There are already a few threads for the same issue. The details and workaround are up at https://redmine.pfsense.org/issues/7937



  • I think I will let my SG-2220 cool of for some days, and wait for some "help for Dummies recovery instruktions" a FreeBSB know-nothing guy like me can use.



  • Thanks Jimp.  I think I will need to reinstall and restore configs on all my old machines.

    I will try more updates after I get the first two up and working again.

    BTW - Holy Christ the thread is still here.  Looks like the thin-skinned admins missed one (-;


  • Rebel Alliance Developer Netgate

    @kejianshi:

    Thanks Jimp.  I think I will need to reinstall and restore configs on all my old machines.

    If they are getting the above error, there isn't any compelling reason to reinstall. Just enter the new device name at the mountroot prompt then edit fstab/run ufslabels.sh

    @kejianshi:

    BTW - Holy Christ the thread is still here.  Looks like the thin-skinned admins missed one (-;

    We don't remove threads that actually have error messages and other concrete evidence to go on. Random ranting and complaining without any data to back it up? That all depends on how willing the person is to cooperate. I wouldn't exactly call it "thin-skinned" to stop people from posting FUD and scaring others unnecessarily.



  • Food for thought.  I've never said a bad word about pfsense for years.  I'm a big fan in fact.

    When I say I've had a problem, that should be all the proof that I've really had a problem you would need.

    I have to wait til Monday to get someone's hands on  those boxes because they are headless and unattended and 8k or so miles away.

    My experience with crashes like this is that if you want to satisfy curiosity, going to the console and fooling with line commands works.

    If you want to get a box up and running, a reinstall and restore of config file is a more sure fire method.

    For the boxes I have not updated yet, I will execute that command to try to fix it before I update.  Thanks for the suggestion.

    A word about that.  I can do it, but plenty of people are relatively helpless outside a gui.  I'm no expert.  Just pushing update and having it just work is most ideal.

    Thats why I was saying maybe wait to update because I'd bet anything a fix for the entire issue gets rolled into the update soon.

    End of FUD….


  • Rebel Alliance Developer Netgate

    @kejianshi:

    When I say I've had a problem, that should be all the proof that I've really had a problem you would need.

    For someone who we know has some knowledge and experience, perhaps. But we can't just take every person at their word because often they do not yet have the experience to know the difference between a real problem, something self-inflicted, a hardware failure that coincided with the update, or any other number of possible outcomes. Without some detail or proof about what happened, someone screaming "it's broken" is more like shouting "fire" in a crowded theater.

    @kejianshi:

    A word about that.  I can do it, but plenty of people are relatively helpless outside a gui.  I'm no expert.  Just pushing update and having it just work is most ideal.

    Sure, which is why that's exactly what we've done.

    @kejianshi:

    Thats why I was saying maybe wait to update because I'd bet anything a fix for the entire issue gets rolled into the update soon.

    End of FUD….

    You're being reasonable, talking about specific issues, providing detail, etc. Not FUD and vague ranting.  :-)



  • Took a little while to get someone to go over there to access the box.

    The reason I don't want to be forced to replace hardware like this is because these old boxes are old because they just refuse to break.  Never ever glitchy.

    New machines are a gamble.  I don't care if they are top of the line.  2 identical boxes, 1 will be flakey and the other will be solid.  Takes time to find out which is which.

    Anyway, all fixed.  The painful part was just getting the person at the keyboard to not typo the commands to get it to boot.  After that, ssh made the rest easy.

    Thanks for your patience.


  • Rebel Alliance Developer Netgate

    FYI- We have fixes in the update process to correct the fstab entries now, and they are in place for everyone already, so it's much harder to break in this way. I have not seen any new complaints since the fixes went in.



  • Thats awsome…  Working very well now.  Now I just have to get used to looking for a blue internet tab instead of a red one...


Log in to reply