Upgrade from 16.7.14: First boot failed with Error 19 in Hyper-V VM

[sh8pe]

Hi,

I tried to upgrade my opnsense from 16.7.14 to 17.1 in my Hyper-V (W2K12R2) VM, and after the
first boot I´ve got the Error: Mounting from ufs:/dev/da0s1a failed with error 19
With pressing "?" (List valid disk boot devices) only CD0 and FD0 is shown, nothing else.
One of the last message I see before is: (da0:blkvsc0:0:0:0): Periph destroyed

Maybe it is related to this bug?
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212721

Someone else run into the same problem?

Best regards,
sh8pe

[weust]

I haven't updated yet, but will check it tomorrow evening.

I have a fresh install of 17.1b which is updated to 17.1rc1.
That runs and boots just fine.

Also have a 16.7.12 iirc, that I will upgrade full to 17.1 tomorrow night.
Will let you know how that went.

Oh, keep in mind that 11 had problems with booting, but that was pre-release.
Like the links mentions for 11-rc2/rc3.

[sh8pe]

Now I´ve tried to boot with kernel.old and was successful. Afterwards I choose option 12 again, answered the question with "y" to install minor updates, installed kernel 16.7.11 and now I´m back again.  ;D

Now I am able to backup / snapshot and all that stuff before trying the update again ... in some month  ;)

BR
sh8pe

[GurliGebis]

The fix is here, we just need it applied, and a new ISO to install from: https://bugs.freebsd.org/bugzilla/attachment.cgi?id=175166&action=diff

[GurliGebis]

And here is an ISO that works: https://pkg.opnsense.org/snapshots/OPNsense-17.1-HyperV-cdrom-amd64.iso.bz2

[GurliGebis]

Upgrading is not possible with it though, so backup the config, reinstall with this iso, then restore the config like you normally would.

[sh8pe]

This was quick! I will try it this evening!  :D
Thank you for your support!

BR
sh8pe

[franco]

Upgrade is still possible, you can mount the ISO into the existing VM, boot from it, go to the installer, select "Import Configuration", and then "Guided Installation". It will keep all your settings.

Note this is a FreeBSD 11.0 bug. We're adding a fix to 17.1.1.


Cheers,
Franco

[GurliGebis]

Ohhh, I didn't think about the import config directly from the installer - that's pretty smart :D

[franco]

FYI: https://github.com/opnsense/src/commit/bdf347ea9da

Coming to 17.1.1, thanks for testing GurliGebis!


Cheers,
Franco

[weust]

I'll just wait for 17.1.1 then.

Reading the FreeBSD page I find it very confusing.
11-RC2 and 11-RC3 has this issue. It was fixed, and somehow came back exactly the same in 11-RELEASE?
Then what was OPNsense 17.1b and 17.1rc1 running? Thought that was 11-RELEASE?

[franco]

*Not* fixed on 11.0-RELEASE. 11-STABLE is, but with a very long patch from Microsoft basically updating Hyper-V support, but who knows what problems are in there then... ;)

[weust]

What branch was 17.1b and 17.1rc1 based on, then?

[franco]

11.0-RELEASE with some things from 11-STABLE backported manually. 11-STABLE is not so stable (at least not with a verified release out there, it's open for commits and that makes it difficult to ensure "stableness"), so we are somewhere in the middle between those two points.

[weust]

Oh, the joy of FreeBSD and their naming conventions!