Date: Thu, 20 Dec 2018 17:07:21 -0600 From: Paul Schmehl <pschmehl_lists@tx.rr.com> To: Scott Ballantyne <boyvalue@gmail.com>, FreeBSD <freebsd-questions@freebsd.org> Subject: Re: Upgrade to 11.2 failure Message-ID: <67967F37AC13D12475A956B9@Pauls-MacBook-Pro.local> In-Reply-To: <CAESeg0wTzdnatF0BNynCUTLXgN0wcke-=j8DMR8NTo%2BY05LPHQ@mail.gmail.com> References: <CAESeg0wTzdnatF0BNynCUTLXgN0wcke-=j8DMR8NTo%2BY05LPHQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--On December 20, 2018 at 1:51:59 PM -0500 Scott Ballantyne <boyvalue@gmail.com> wrote: > I have done this many, many times. It does seem that the > freebsd-update/pkg system is more fragile than > I have thought. This isn't a big deal for the stuff I have at homes, but I > have come to rely on this combo > to update systems to which I don't have physical access. Now I am a bit > concerned about doing that. > I know exactly how you feel. I used freebsd-update to upgrade two production systems from 10.4 to 11.2, and both systems didn't come back up after reboot. The first system was in California, so I had to have the hoster figure out what went wrong and fix it. The /etc/rc.conf file was screwed up. The second system was local, so I went to the hosting company and got on the console. It required two fsck runs to fix everything. So, the third system, I didn't even bother. I went to the site and upgraded from the console. That one worked fine. Go figure. And yeah, I've run freebsd-update numerous times without any problems - until now. Paul Schmehl, Retired My opinions are my own. ******************************************* "It is as useless to argue with those who have renounced the use of reason as to administer medication to the dead." Thomas Jefferson "There are some ideas so wrong that only a very intelligent person could believe in them." George Orwell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?67967F37AC13D12475A956B9>