From owner-freebsd-questions@FreeBSD.ORG Tue Jul 6 14:38:13 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id B3A22106566B for ; Tue, 6 Jul 2010 14:38:13 +0000 (UTC) (envelope-from glarkin@FreeBSD.org) Received: from mail1.sourcehosting.net (113901-app1.sourcehosting.net [72.32.213.11]) by mx1.freebsd.org (Postfix) with ESMTP id 906868FC08 for ; Tue, 6 Jul 2010 14:38:13 +0000 (UTC) Received: from 68-189-245-235.dhcp.oxfr.ma.charter.com ([68.189.245.235] helo=cube.entropy.prv) by mail1.sourcehosting.net with esmtp (Exim 4.69 (FreeBSD)) (envelope-from ) id 1OW9Hj-0004he-Cv; Tue, 06 Jul 2010 10:38:12 -0400 Received: from [127.0.0.1] (fireball.entropy.prv [192.168.1.12]) by cube.entropy.prv (Postfix) with ESMTP id 4D17F4230A8F; Tue, 6 Jul 2010 10:38:07 -0400 (EDT) Message-ID: <4C333FC8.20802@FreeBSD.org> Date: Tue, 06 Jul 2010 10:38:00 -0400 From: Greg Larkin Organization: The FreeBSD Project User-Agent: Thunderbird 2.0.0.24 (Windows/20100228) MIME-Version: 1.0 To: Mike Barnard References: In-Reply-To: X-Enigmail-Version: 0.96.0 OpenPGP: id=1C940290 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) Cc: FreeBSD Questions Subject: Re: /usr/local empty after upgrade X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: glarkin@FreeBSD.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Jul 2010 14:38:13 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Mike Barnard wrote: > Hi All, > > I have never encountered anything like this before and I am little puzzled. > After upgrading my FreeBSD 8.0 RELEASE, I ended up with FreeBSD > 8.1-PRERELEASE and an empty /usr/local directory. It wiped out my /usr/local > directory! I did nothing out of the usual on this upgrade. Any one > experienced the same thing? How do I safely get /usr/local populated again? > > > Hi Mike, It's possible that your disk device names changed during the upgrade and /etc/fstab can no longer mount the previous device on /usr/local. Do you see any error messages during the boot process? Please reply to the list with the output from the following commands: ls -l /dev/da* # Assuming SCSI disks ls -l /dev/ad* # Assuming ATA disks cat /etc/fstab That information may help figure out what happened to the devices during the upgrade. Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFMMz/I0sRouByUApARAtS0AJ9Ny8rx0AcIen2o5fiJAQTn04ugKQCglxei L7dLVcqJbKqB/B9pc3v1fWM= =AGrW -----END PGP SIGNATURE-----