From owner-freebsd-current@freebsd.org Sun Nov 8 14:49:15 2015 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 04558A29B93 for ; Sun, 8 Nov 2015 14:49:15 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id DDD2A1532 for ; Sun, 8 Nov 2015 14:49:14 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: by mailman.ysv.freebsd.org (Postfix) id DAA0EA29B91; Sun, 8 Nov 2015 14:49:14 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id BF5CAA29B90 for ; Sun, 8 Nov 2015 14:49:14 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from aibo.runbox.com (aibo.runbox.com [91.220.196.211]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4FA371531 for ; Sun, 8 Nov 2015 14:49:13 +0000 (UTC) (envelope-from jbtakk@iherebuywisely.com) Received: from [10.9.9.241] (helo=rmm6prod02.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1ZvRHK-0005Q7-M3; Sun, 08 Nov 2015 15:49:10 +0100 Received: from mail by rmm6prod02.runbox.com with local (Exim 4.76) (envelope-from ) id 1ZvRHK-0007EM-Kh; Sun, 08 Nov 2015 15:49:10 +0100 Content-Type: text/plain; charset="utf-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Received: from [Authenticated user (846156)] by runbox.com with http (RMM6); Sun, 08 Nov 2015 14:49:10 GMT From: "Jeffrey Bouquet" Reply-To: jbtakk@iherebuywisely.com To: "jbtakk" CC: "current" Subject: Re: Cannot installworld, don't expect to... part 2... Date: Sun, 08 Nov 2015 06:49:10 -0800 (PST) X-Mailer: RMM6 In-Reply-To: Message-Id: X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Nov 2015 14:49:15 -0000 On Sat, 07 Nov 2015 19:14:47 -0800 (PST), "Jeffrey Bouquet" wrote: > I've a not-complete-installworld from today, dumped core halfway through= =20 > despite single-user mode... >=20 > began with an install of libc++... which was fine. >=20 > i can restore > /lib > /libexec > /bin > /sbin > /usr/bin > /usr/sbin > from an earlier backup >=20 > and most binaries work again, but nowhere near > full functionality... wanting to restore browser > functionality... which mysteriously broke (all segfault) which > prompted the buildworld. >=20 > setting COMPILER_TYPE results later in > sh: cc; not found during the installworld.=20=20 > OTOH some buildworld=20 > produced files may have been lost during the fsck to lost+found >=20 > I noticed a few clang files ended up in lost+found during one of the many= fsck. >=20 > So as an aside of any usual question... > Is there any documentation=20 > where make installs should proceed? > for instance libc++ first, then ... >=20 > and/or how to run the installworld segment-at-a-time to find the > specific failure? OR it is too complex >=20 > Assuming "no" to each of the above... is there a best > practice to=20 > copy a greater number of the /lib, libexec from=20 > backup to completely restore, or is it necc. to > do a reinstall to an ENTIRELY new disk... given that > the existing disk for some reason does not want to > complete it. >=20 > Maybe even someone has an easier way... or procedure. >=20 > Thanks. >=20 > ... > As an aside, a wanted feature: >=20 > during one disk crash recently, the pass* in /etc wound up in lost+found. > No login resulted. Restored from backup by luck... was clueless. > Would it be wise to build redundancy into the base, so that for example > if /etc/fstab has vanished, its shadow copy in /etc/shadow/... > or even enough binaries, (similar /rescue ) to complete a complete svn > buildworld installworld as a sort of /rescue/usr/src with all binaries and > libraries contained therein. >=20 > Maybe... >=20 >=20 Crash recovered. All /root/.* directories had vanished also... so I was t= hinking, maybe if fsck_ffs were more elaborate when placing the files in lost+found it would = place metadata as to where it came from, and then lost+found-replace.sh or binary could recover = FROM lost+found... I could be just wishing though. But the reason for this reply-followup rather than a new post (the paragrap= h above) with apologies... Now that the recovery here has been done, ( files between nov 3 and nov 7 c= opied from /mnt where the crashed disk(s) and backups were mounted)... WHAT is the best practice if *this* working r288246 (11.0-CURRENT) builds w= orld, then core dumps during installworld, rendering login and/or paths upon login and= /or segfaults of nano, etc after login and/or all working but browsers segfault= ing after fixup... since this is a principal desktop ...=20 ... the best practice for "if this installworld hoses, simply copy files fr= om ..." recovery? OR, no one else knows either, which I think is more likely, in which case = I=20 apologize for even stating the question. Thanks.=