Date: Thu, 16 Mar 2017 09:52:13 -0500 (CDT) From: "Valeri Galtsev" <galtsev@kicp.uchicago.edu> To: freebsd-questions@freebsd.org Subject: Re: Second severe crash in six weeks Message-ID: <30597.128.135.52.6.1489675933.squirrel@cosmo.uchicago.edu> In-Reply-To: <20170316055219.GA23268@becker.bs.l> References: <20170315222221.GA18691@becker.bs.l> <20170316042450.GA5861@lime.woodcruft.co.uk> <20170316055219.GA23268@becker.bs.l>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, March 16, 2017 12:52 am, Bertram Scharpf wrote: > On Thursday, 16. Mar 2017, 04:24:50 +0000, Frank Shute wrote: >> On Wed, Mar 15, 2017 at 11:22:21PM +0100, Bertram Scharpf wrote: >> > since I upgraded to FreeBSD 11.0, every second >> > port rebuild freezes the system. Besides that, >> > in the last two weeks I had two packages that >> > refused to build. >> Before pointing the finger at FreeBSD, remind yourself that you will >> then >> have four fingers pointing at yourself. > > I know. It's always the other ones fault. Do you know? It can be one or more of many things. Let me mention my own recent "pilot errors" (stealing William's name for it): 1. I did "freebsd-update upgrade -r ...". And left the box live like that for quite some time. Then I finally decided to indeed go through the whole upgrade game, and got the box messed-up as a result (with libraries everything bases on missing, like libc). 2. I had hardware (in my opinion) trouble mess things for me once. It must have been badblock (no, I don't have zfs on that box), which cut part of my filesystem tree. This can create big mess if you hit it during upgrade. And I join someone's opinion that yours may be hardware problem (you just push the box over the edge during massive build). As a "band-aid" solution, I would remove any parallel flags from build. But if I have this happening to one of my boxes I would do this. Take different machine that can permanently replace functions of this one. Clean build the system you need on it (be it 10.3, or 11.0). Migrate everything to this new machine from box in question. Once all works on replacement box and it is in production for 1-2 Months, wipe the original box, install new system on it and give the box real stress test to see if you can rule out hardware, then roll out this hardware into production (as something else). Alternatively, if you have small shop with no spare machines, back everything up, shut the machine down, pull original drive, and stick in new drive (do all minor hardware tricks like re-seating memory, extra cards etc), install system, and install all what machine had, and restore users and data from backup. Good luck! Valeri > > Bertram > > > -- > Bertram Scharpf > Stuttgart, Deutschland/Germany > http://www.bertram-scharpf.de > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org" > ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?30597.128.135.52.6.1489675933.squirrel>