Slow Boot on Upgrade i.e., one character per 1.5 seconds


  • Hi,

    Just upgraded to 2.2.2 and have this same problem with this guy posted on youtube… https://www.youtube.com/watch?v=MPO5nAkVm7o

    Is there any solution rather than re-installing it from scratch?

    Regards


  • Disable serial interface in bios and then reboot.  Try it then.


  • @CrackBlue:

    Hi,

    Just upgraded to 2.2.2 and have this same problem with this guy posted on youtube… https://www.youtube.com/watch?v=MPO5nAkVm7o

    Is there any solution rather than re-installing it from scratch?

    Regards

    What makes you think "re-installing it from scratch" would work?
    But if you'd prefer that rather than putting down the crack blue pipe and reading.  Go ahead.


  • @NOYB:

    @CrackBlue:

    Hi,

    Just upgraded to 2.2.2 and have this same problem with this guy posted on youtube… https://www.youtube.com/watch?v=MPO5nAkVm7o

    Is there any solution rather than re-installing it from scratch?

    Regards

    What makes you think "re-installing it from scratch" would work?
    But if you'd prefer that rather than putting down the crack blue pipe and reading.  Go ahead.

    What made you think i have a crack blue pipe?
    I have read and wait for some good advise on my posts, that make sense than having that crack blue pipe. :)


  • After its up and running, take a look here.

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


  • @CrackBlue:

    What made you think i have a crack blue pipe?

    Well really it was a tongue n cheek commit.  But your seemingly lack of discipline to go read the release notes does make me think it maybe true.  The information you seek is readily available.  No need to wait for anyone to respond to your post.  Or for that matter there is really no need even for this thread to have been started.


  • @kejianshi:

    After its up and running, take a look here.

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

    Any idea how long it takes a 2.2.2 with the serial issue to boot on average?

    I have a remote device that was upgraded and is experiencing this issue.  I'll probably have to log into it remotely and patch it, I was just wondering how long I need to wait for the box to come back online.

    I'm at 90 minutes and holding….


  • Guys, can we please not have yet another geek pissing match?  They're getting tiring.  Surely we can help each other without the critical snark & insults?


  • @tim.mcmanus:

    @kejianshi:

    After its up and running, take a look here.

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

    Any idea how long it takes a 2.2.2 with the serial issue to boot on average?

    I have a remote device that was upgraded and is experiencing this issue.  I'll probably have to log into it remotely and patch it, I was just wondering how long I need to wait for the box to come back online.

    I'm at 90 minutes and holding….

    I got roughly 30% through the boot screen stuff in about 4 hours.
    I think if you WALK to wherever the remote site is, fix it, and WALK back, it'll be faster than waiting on it to complete.


  • So in only 9 hours and 20 minutes you will be all set.  Not sure if patience is a virtue in the IT world?


  • LOL, thanks for the benchmark and walking suggestions.

    Yeah, I am more than likely going to schlep over to the router myself to tweak it.  Nine hours isn't a deal-breaker this time, we have a workaround.

    Thanks again!


  • @KOM:

    Guys, can we please not have yet another geek pissing match?  They're getting tiring.  Surely we can help each other without the critical snark & insults?

    +1 for this post
    I also never understood what is arrogancy good for.


  • tim.mcmanus - Did it eventually boot on its own?


  • I too had this problem after the most recent update.  I didn't have time to screw around with it so I tried reinstalling from a freshly downloaded image and I didn't have the problem.  I hope that may help someone figure out how to get around it or how to fix it.

    For those of you with more time let your pissing match continue.


  • @KOM:

    Guys, can we please not have yet another geek pissing match?  They're getting tiring.

    So are idiotic posts about my system won't boot after the upgrade to 2.2.2 but I too special to go read the upgrade guidance notes etc.

    Which is basically how this thread started out.  That has no refection on the recent change in direction by Tim though.  Legit quest for information that doesn't seem to be readily available for making an informed decision about course of action to take for his situation.


  • The full update files (only thing affected) have been updated with this change:
    https://github.com/pfsense/pfsense/commit/cc1f655f8e88ccda837e21d0646bbc71781198b9

    so this won't happen to anyone else.


  • @kejianshi:

    tim.mcmanus - Did it eventually boot on its own?

    I never gave it a chance to finish.  It patched and rebooted today at 12:00 GMT, and I got to the machine at 22:00 GMT.  The screen was still outputting characters when I arrived.

    As much as I like benchmarking and metrics, this was one I could live without.  I rebooted, applied the fix in the other thread, and it booted in 90 seconds or so.  Everything back to normal, and I got my walking exercise in for the week!


  • On my part it was just morbid curiosity.  Anyway - The fixed it.  Hurray!


  • @cherrypie:

    I too had this problem after the most recent update.  I didn't have time to screw around with it so I tried reinstalling from a freshly downloaded image and I didn't have the problem.  I hope that may help someone figure out how to get around it or how to fix it.

    For those of you with more time let your pissing match continue.

    Because the images have since been patched with the fix.  You could have just spent 30 seconds of reading and avoided the reinstall all together.

    I have extra time because I missed out on all the troubleshooting of a failed upgrade due to a serial port issue on a system that has no need of a serial port (and never will, regardless of any circumstances that ever occur).  Even if existed it would never be used.  KISS


  • cmb, seems that NanoBSD images are affected too: https://forum.pfsense.org/index.php?topic=93010.0
    Can you please update these too with the appropriate change?