New to the forums, I did check many other previous posts. Have been searching for over a week. Attempted the upgrade last weekend, trying to revisit this weekend...
From My Reddit Post:
Baremetal, i5/3rd Gen, 16GB Ram. ZFS
I have been sweating the update for weeks. Saw several posts and prepared myself the best I could. Attempted the upgrade tonight and lost all connectivity. Build: ZFS (snapshot before upgrade), never had microcode plugin installed, Legacy ISC, simple rules migrated over, backed up Config. Began the upgrade.
Got stuck in a "rebooting now" and returning to the Lobby/Dashboard loop, assumed the update failed. Started to disconnect to add my ISP/backup router back in to troubleshoot, decided to manually reboot the Opnsense box, patiently waited, and heard the boot chime. Logged in from my daily driver desktop, and saw the new dashboard with 26.7.1. Loaded rules via the migration tool, verified they were there, deleted "Legacy Rules" via the tool. Success! ...Nope, no devices on my network receiving any connection. I cannot find the issue, but the Live logs show no traffic being let in whatsoever (all blocked).
I have no clue how to install the bootloader to the secondary drive. Reading tons on it, but just don't understand any of it.
Switched to my backup/ISP provided router, for now...hope to dive in some more tomorrow.
Any insights would be great.
Feels like this is simply a rules issue, but don't know where to begin.
If I need a fresh install, that isn't a big deal, I just have a few questions.
Will I still be able to migrate my old rules?
Are there "new" default rules with a fresh install?
Will my old 26.1 config files work with a fresh install of 26.7 (Legacy ISC and Legacy Rules)? I hope to migrate to dnsmasq, but would prefer to be running first.
with loads of successful upgrades so far I can only assume some sort of setup/settings have come to bite.
What makes you think that you need to install the bootloader to the secondary drive? Do you have a mirrored pair of disks for the OS ? If yes, then it is a likely possibility but if you can boot after the upgrade, then you can look at that afterwards.
What's the status now, is it rolledback via a snapshot?
Note that if you had to put the isp router back in and then had router-behind-a-router, then that could account for no clients hitting it.
Quote from: cookiemonster on Today at 10:42:25 PMwith loads of successful upgrades so far I can only assume some sort of setup/settings have come to bite.
Thank you for the reply.
QuoteWhat makes you think that you need to install the bootloader to the secondary drive?
It was just part of what I have been reading needs to be done to get ZFS corrected?
QuoteDo you have a mirrored pair of disks for the OS ? If yes, then it is a likely possibility but if you can boot after the upgrade, then you can look at that afterwards.
Yes, and i can boot to OpnSense and look at (what appears to be) a working build...other than no internet access.
QuoteWhat's the status now, is it rolledback via a snapshot?
No, it's completely in the state of the upgrade and migrated rules. I had too many questions to give up on it, or attempt a fresh install. Someone on the app thought it might be the kernel fail...but it doesn't (didn't) stay in the boot loop. When I manually restarted, the upgrade must have continued (or i hadn't waited long enough).
QuoteNote that if you had to put the isp router back in and then had router-behind-a-router, then that could account for no clients hitting it.
I only put the ISP provided router in to get things working. My wife works from home, so I need a contingency to keep her up and running. The OpnSense box is offline while the ISP router is in place. I can only devote time to the fix late at night, or on the weekends.