issues upgrading from 10.1-RELEASE to 11-RELEASE

[Yudi V]

hi

I tried updating from 10.1 to 11-RELEASE, did not go well.
current system:
$ uname -a
FreeBSD xxxxxxx 10.1-RELEASE-p41 FreeBSD 10.1-RELEASE-p41 #0: Fri Oct 21
23:03:01 UTC 2016
ro...@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC
amd64

first I cloned the OS filesystem and then booted to the cloned fiesystem
and then upgraded the OS following:
https://www.freebsd.org/releases/11.0R/installation.html
also read https://www.freebsd.org/releases/11.0R/relnotes.html#upgrade

did not notice anything that suggested I would run into problems.

Steps I followed:

# freebsd-update fetch
# freebsd-update install
# freebsd-update upgrade -r 11.0-RELEASE
Error:
# freebsd-update upgrade -r 11.0-RELEASE
Looking up update.FreeBSD.org mirrors... 4 mirrors
found.
Fetching metadata signature for 10.1-RELEASE from
update6.freebsd.org... done.
Fetching metadata index... done.
Fetching 1 metadata files... done.
Inspecting system... done.

The following components of FreeBSD seem to be
installed:
kernel/generic world/base world/doc world/lib32

The following components of FreeBSD do not seem to be
installed:
src/src world/games

Does this look reasonable (y/n)? y

Fetching metadata signature for 11.0-RELEASE from
update6.freebsd.org... done.
Fetching metadata index... done.
Fetching 1 metadata patches. done.
Applying metadata patches... done.
Fetching 1 metadata files... done.

The update metadata is correctly signed, but
failed an integrity check.
Cowardly refusing to proceed any further.

Solution is to upgrade to 10.3 first as suggested by
someone in the IRC channel.
freebsd-update upgrade -r 10.3-RELEASE
# freebsd-update install
# shutdown -r now
# freebsd-update install
//installs userland components
# freebsd-update fetch
# freebsd-update install //
rebuilds 3rd party apps

# shutdown -r now //
final reboot

EVerything looked fine with 10.3 upgrade, proceeded to
11-RELEASE upgrade

# freebsd-update upgrade -r 11.0-RELEASE //no
errors this time,
# freebsd-update install
# shutdown -r now
# freebsd-update install //installs userland
components
# freebsd-update install
# shutdown -r now // final reboot

after reboot, logged in and tried:
$ screen
Shared object "libelf.so.1" not found, required by "screen"
SAMBA failed sanity check,

$ pkg update
Shared object "libssl.so.7" not found, required by "pkg"

Again someone in the IRC channel suggested I try # pkg-static install -f
pkg to fix the pkg issue.

and to fix all of them, they suggested I do:
#fetch
http://ftp0.bme.freebsd.org/pub/FreeBSD/releases/amd64/11.0-RELEASE/base.txz;
tar -xzf base.txz -C / --exclude etc

Before I go ahead and replace the base system files, I would like to know
what went wrong.
because I cloned the OS filesystem, I can go back and re-do it properly if
the problem was at my end.
Any suggestions?
or should I log a PR?

regards
Yudi
_______________________________________________
freebsd-...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"

[Sergei Akhmatdinov]

On Wed, 18 Jan 2017 16:21:54 +1100
Yudi V <yudi...@gmail.com> wrote:
> I tried updating from 10.1 to 11-RELEASE, did not go well.
> current system:

> [snip]

> Before I go ahead and replace the base system files, I would like to know
> what went wrong.
> because I cloned the OS filesystem, I can go back and re-do it properly if
> the problem was at my end.
> Any suggestions?
> or should I log a PR?

My guess is that your binaries were compiled for 10.X, but 11.0 overwrote the
required shared libraries, so now the old binaries cannot find them.

Do core utilities (ls/cd/man and such) work?

Try upgrading all of your packages after your install the kernel and reboot,
but before you install the world (userland). It doesn't look like you did that,
judging by your message.

I am not sure that blindly extracting base into your FS would really fix things.

You *may* be able to get away with fixing pkg and upgrading your system as it
is now.
Otherwise, I am certain that rebuilding all installed packages from ports would
fix things.

Cheers,
--
Sergei Akhmatdinov

My GPG public key:
gpg --keyserver pgp.mit.edu --recv-keys AD800D99

[Roland Smith]

On Wed, Jan 18, 2017 at 04:21:54PM +1100, Yudi V wrote:
> hi
>
> I tried updating from 10.1 to 11-RELEASE, did not go well.

<snip>

Looks like the base system update went OK.

> after reboot, logged in and tried:
> $ screen
> Shared object "libelf.so.1" not found, required by "screen"
> SAMBA failed sanity check,

> $ pkg update
> Shared object "libssl.so.7" not found, required by "pkg"

<snip>

> Before I go ahead and replace the base system files, I would like to know
> what went wrong.

It looks like all your problems are with *ports*.

After a major version update it is *strongly recommended* that you first
*delete* all ports/packages and then update your ports tree and re-install
them. This because of shared library version updates.

You can do this by making a list of all "leaf" packages (before deleting); packages that
have dependencies but are not depended on with this command:

pkg query -e '%#r == 0' '%n-%v\t%o'

This will list the current package name and origin. Save that to a file and
keep it

After you've made this list, delete all packages and re-install all leaf
packages.

Roland
--
R.F.Smith http://rsmith.home.xs4all.nl/
[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93 FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)

[Yudi V]

Thanks guys the issue is I missed the below section as I followed the
release notes instructions.
23.2.3.2. Upgrading Packages After a Major Version Upgrade

ran

pkg-static install -f pkg
# pkg-static upgrade -f


fixed all the issues. Problem was to do with different ABIs.

--
Kind regards,

[krad]

Its worth noting the latest version of pkg will realise there has been an
ABI change and upgrade all the packages without having to force them. You
can also install the compat libraries as well if you want a quick fix if
the rebuild is complex. If you are not using boot environments look into
them as well and see if they would be viable for you as they can save a lot
of grief, and let you do a lot of this grunt work before the 1st reboot.

> To unsubscribe, send any mail to "freebsd-questions-
> unsub...@freebsd.org"

[Yudi V]

Hi Krad,

I did upgrade pkg first (pkg-static install -f pkg) but it did not upgrade
all the packages as you suggest, I had to do it manually. Anyway now
everything is back to normal.

I was thinking of using boot environments and even setup the suggested
dataset hierarchy, ie: pool/ROOT/environments, then I realised to boot
into a different boot-environment/dataset I can just use the bootfs flag,
this only works if all the boot environments/datasets are set to
mountpoint=legacy.
I was using this method well before beadm was officially released.
It's only two commands to remember, clone and set bootfs, so never
bothered with beadm.
This is one of the main reasons why like FreeBSD.
I was inquiring about similar functionality in btrfs and some in the
community were adamant that it is not a critical feature so not yet
implemented (although I have read somewhere that it was possible to boot
into a cloned dataset). I completely disagree with them. I guess they never
came across a situation where there was no easy way to go back to a working
system that was borked by an upgrade.

cheers
Yudi

On Tue, Jan 31, 2017 at 11:51 PM, krad <kra...@gmail.com> wrote:

> Its worth noting the latest version of pkg will realise there has been an
> ABI change and upgrade all the packages without having to force them. You
> can also install the compat libraries as well if you want a quick fix if
> the rebuild is complex. If you are not using boot environments look into
> them as well and see if they would be viable for you as they can save a lot
> of grief, and let you do a lot of this grunt work before the 1st reboot.
>
> On 19 January 2017 at 16:36, Yudi V <yudi...@gmail.com> wrote:
>
>> Thanks guys the issue is I missed the below section as I followed the
>> release notes instructions.
>> 23.2.3.2. Upgrading Packages After a Major Version Upgrade
>>
>> ran
>>
>> pkg-static install -f pkg
>> # pkg-static upgrade -f
>>
>>
>> fixed all the issues. Problem was to do with different ABIs.
>>
>> --
>> Kind regards,
>> Yudi
>> _______________________________________________
>> freebsd-...@freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-questions

>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe
>> @freebsd.org"

>>
>
>


--
Kind regards,
Yudi
_______________________________________________
freebsd-...@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-questions

To unsubscribe, send any mail to "freebsd-questi...@freebsd.org"