Hi Greg,
Thanks for the tips. I'll be able to retry the upgrade this weekend.
- Stu
On 10/11/2012 5:49 PM, Greg Larkin wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/11/12 2:43 PM, Stuart Matthews wrote:
Hi everyone,
I am including as much information in here as I think will be
useful. Since I can do snapshots on VMWare, I am happy to try any
solution or diagnostics. Steps I took to upgrade FreeBSD: Using
freebsd-update, I upgraded from 7.2-RELEASE to 7.2-RELEASE-p8 Then,
to upgrade to 9.0-RELEASE, I ran the following commands, using
http://www.freebsd.org/doc/handbook/updating-upgrading-freebsdupdate.html
as my guide: freebsd-update -r 9.0-RELEASE upgrade freebsd-update
install reboot freebsd-update install portupgrade -f ruby rm
/var/db/pkg/pkgdb.db portupgrade -f ruby18-bdb rm
/var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db portupgrade -af
freebsd-update install reboot
I noticed that lots of things weren't working, and specifically
that I was getting lots of complaints about /libexec/ld-elf.so.1. I
also noticed that when I ran freebsd-update IDS, it seemed to
report that every single file had the wrong signature.
So, this being a VMWare guest, I reluctantly reverted to a
previous snapshot, putting me back at 7.2-RELEASE-p8.
I decided to try this time to go from 7.2-RELEASE-p8 to 7.4-RELEASE
to 8.0-RELEASE to 8.3-RELEASE. I only got to 7.4-RELEASE before I
had the same issues as above. As a specific example of errors I
would get, I try to run sudo and I get: [stuart@richelieu ~]$ sudo
bash /libexec/ld-elf.so.1: sudo: invalid PT_PHDR
This seems to be the most relevant thread to the problem I'm
having:
http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218443.html
However, I'd be more comfortable using an official upgrade path,
like freebsd-update, exclusively. That thread involves replacing a
file from a FreeBSD liveCD. Also, with freebsd-update IDS reporting
so many files with incorrect signatures, I feel like my problem is
bigger than fixing one file.
Right now I am back on 7.2-RELEASE-p8 eager to get my OS upgraded
to something that is under current support by the security team.
Optimally I'd like to be on 8.3 after looking at the EOL dates.
Also, I did see one other post _somewhere_ mentioning a similar
proble also on a VMWare guest. So I am suspicious that the problem
might be related to VMWare.
Thanks, everyone.
- Stuart Matthews
Hi Stuart,
If you click the link in this mailing list article
(http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218554.html),
then follow the rest of the threaded messages, you should be able fix
the problem once you upgrade to 7.4.
The issue is that freebsd-update cannot update the ld-elf.so.1 binary
on a running system, so after the upgrade to 7.4 (or higher), the
system is not completely updated.
This message
(http://lists.freebsd.org/pipermail/freebsd-questions/2010-July/218884.html)
has a fix, but it involves booting from a liveCD and replacing the
binary manually.
Hope that helps,
Greg
- --
Greg Larkin
http://www.FreeBSD.org/ - The Power To Serve
http://www.sourcehosting.net/ - Ready. Set. Code.
http://twitter.com/cpucycle/ - Follow you, follow me
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (Darwin)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iEYEARECAAYFAlB3aQ8ACgkQ0sRouByUApAj2QCgjZZKHLHa04PM3qhtKfwuzJpq
D0MAn3uolwsr/ukwGSxLXK42410IfMt8
=JiOa
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
