From owner-freebsd-questions@FreeBSD.ORG Thu Jan 29 14:12:53 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 504F516A4CF for ; Thu, 29 Jan 2004 14:12:53 -0800 (PST) Received: from EMAILSERVER2.nemschoff.com (host-66-202-56-162.mil.choiceone.net [66.202.56.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id C39A843D1D for ; Thu, 29 Jan 2004 14:12:15 -0800 (PST) (envelope-from MClark@Nemschoff.com) Received: by EMAILSERVER2.nemschoff.com with Internet Mail Service (5.5.2653.19) id ; Thu, 29 Jan 2004 16:16:23 -0600 Message-ID: From: Michael Clark To: 'Chris' , "'freebsd-questions@freebsd.org'" Date: Thu, 29 Jan 2004 16:16:22 -0600 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: RE: 5.1 -> 5.2 disaster X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Jan 2004 22:12:53 -0000 Assuming that happened somehow, which is hard to believe because I scripted the process and have upgraded this machine before, what can be done to fix it? Am I on the correct track with using a CD upgrade? Should I run a dd and force a system from another box onto it? I dont like the dd option because it requires I take the box offline and offsite.... -----Original Message----- From: Chris [mailto:racerx@makeworld.com] Sent: Thursday, January 29, 2004 3:19 PM To: Michael Clark; 'freebsd-questions@freebsd.org' Subject: Re: 5.1 -> 5.2 disaster -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thursday 29 January 2004 02:54 pm, Michael Clark wrote: > First off, this is not a hardware problem! It crashes at the exact same > spot over and over on multiple different commands. > > I had a 5.1 - 5.2 upgrade via cvsup that went terribly wrong. The machine > got rebooted and certain things would no longer work. I cannot get a make > world, or make buildworld to work. Errors on on the mtree command with: > > mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p > /usr/obj/usr/src/i386/usr/include > *** Signal 12 > > When I try the line manually I get: > > bash-2.05b# mtree -deU -f /usr/src/etc/mtree/BSD.include.dist -p > /usr/obj/usr/src/i386/usr/include > Bad system call (core dumped) > > I have tried brining in a new kernel and /usr/bin and /usr/src from another > machine. The problems just seem to get worse > Before we were only dumping on sendmail, now I have: Did you by chance read /usr/src/UPDATING ? ****************************DANGER******************************* DO NOT make installworld after the buildworld w/o building and installing a new kernel FIRST. You will be unable to build a new kernel otherwise on a system with new binaries and an old kernel. Even better, tha handbook describes the process in detail down to single user mode. - -- Best regards, Chris -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAGXjbD5P/gMAbw2MRAhiNAJwJjJKtBRsJrYe/cr+JVHApG1I6KwCfTFEc w6PCizIzNw2ljkQqLS274NI= =y8ik -----END PGP SIGNATURE----- CONFIDENTIALITY NOTE: This electronic transmission, including all attachments, is directed in confidence solely to the person(s) to whom it is addressed, or an authorized recipient, and may not otherwise be distributed, copied or disclosed. The contents of the transmission may also be subject to intellectual property rights and all such rights are expressly claimed and are not waived. If you have received this transmission in error, please notify the sender immediately by return electronic transmission and then immediately delete this transmission, including all attachments, without copying, distributing or disclosing same.