Upgrade 17.7.12_1>18.1 failure

Started by Taomyn, January 29, 2018, 09:48:45 PM

Previous topic - Next topic
January 30, 2018, 12:17:58 AM #15 Last Edit: January 30, 2018, 12:19:32 AM by nasq
In my company, we developers call this the "git monster" - eating away code  ;D

We're fixing the upgrade paths now allowing people to land in 18.1_1 instead. Mirror sync time may differ though...

https://github.com/opnsense/changelog/commit/a4e219fdaf1


Cheers,
Franco
"AI has absolutely reduced the cost of creating technical debt." -- ChatGPT

So I'm still on 17.7.12 and decided to go through all my rules and properly split out IPv4 and IPv6 rules to ensure that they are handled correctly - it's probably for the best anyway. Whether this will fix the real issue I had remains to be seen.


However, I'm delaying the upgrade to v18 until at least next week because the SMART service is reporting my drive is failing. I've ordered a replacement mSATA drive and will install v18 on that directly, at least then if it goes wrong I can swap back the old drive to get back up and running. The old drive may not actually be defective as it's a known issue of these Kingston drives but annoyingly the only way to upgrade is with a Windows utility which my box doesn't have. I did try for four hours to get Win7 running off a USB stick, but the utility wouldn't start so I gave up - hopefully with an mSATA to SATA adaptor I can sort that out.