From owner-freebsd-questions@FreeBSD.ORG Wed Dec 11 06:46:55 2013 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BF678CD for ; Wed, 11 Dec 2013 06:46:55 +0000 (UTC) Received: from sc3app27.rit.edu (sc3app27.rit.edu [129.21.35.56]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 81F6C1DDF for ; Wed, 11 Dec 2013 06:46:55 +0000 (UTC) Received: from mail-qa0-f41.google.com (mail-qa0-f41.google.com [209.85.216.41]) by smtp-server.rit.edu (PMDF V6.3-x14 #31420) with ESMTPS id <0MXM00GE2QU45R@smtp-server.rit.edu> for freebsd-questions@freebsd.org; Wed, 11 Dec 2013 01:46:53 -0500 (EST) Received: by mail-qa0-f41.google.com with SMTP id j5so4457045qaq.7 for ; Tue, 10 Dec 2013 22:46:52 -0800 (PST) Received: by 10.224.191.195 with HTTP; Tue, 10 Dec 2013 22:46:52 -0800 (PST) X-Received: by 10.49.131.164 with SMTP id on4mr51390125qeb.16.1386744412884; Tue, 10 Dec 2013 22:46:52 -0800 (PST) X-Received: by 10.49.131.164 with SMTP id on4mr51390112qeb.16.1386744412722; Tue, 10 Dec 2013 22:46:52 -0800 (PST) Date: Tue, 10 Dec 2013 22:46:52 -0800 From: "ETHAN HOUSE (RIT Student)" Subject: Re: Base System Rebuild In-reply-to: <20131211144403.711eb6a9@X220.alogt.com> Sender: ewh2048@rit.edu To: Erich Dollansky Message-id: MIME-version: 1.0 X-RIT-Received-From: 209.85.216.41 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=VT9kki0cu1nIsFumyAqzIj7a3Sf7hlCgLqf531gMi0M=; b=i3/vDSPDwMtQU840+HCnjwsTLNx3q9wKBAhHw0UAKcgav6g6C7rQlDbblGM7itZ7nS 5cpUajEU/KFug123Svi8IzvFe+Q05/PqyLLvpv1/z9KTz1Z1GETyPCfPAlClgQS1OcVN E8CBV9ds+seCb+C46n/ueSe5OS+UAYDU+myeHUywOwNDekEvFFeWx3cO6bXjiqJ6LvHY AKwZi+h5wFLLA7tTX/9pPe7nx3mLT2pECTa8Ef7lRrLm0+bDU9Lx2B/D10TSyzGiwg00 2022OqJ9FsRLDpsvbYRBzBZTb+rn5RT9+a30kDRF69dtQdUrIMJlmHmyJTOvPoQCibie cm7Q== X-Gm-Message-State: ALoCoQnkiBt4DpU/hKWxD7CnnoADJSV61WU3b5vwSERd4MTOmXM/lCb8ACCZVzotVwYG7WyRfhJmG86vj3USzyX6EBAW5NOAMGx3QDFzzo80S4zNQwXbw7BBPZ2jpY+TNWz5MYnyjXYNeaUF1dMtnrjvzgTaYX+91rTUUbaCB5H/9kN1SJ7qv10= X-Google-Sender-Auth: gG4t0SQV3vHVLZ1-T1plwjxgaAg References: <20131210162820.6834d51b@X220.alogt.com> <20131210170905.1dfb9fd7@X220.alogt.com> <20131210172513.77fa8482@X220.alogt.com> <52A79136.7090103@ShaneWare.Biz> <76E49CC4-57CE-4A45-B051-025D465B311F@fisglobal.com> <20131211115641.5e15206e@X220.alogt.com> <20131211134031.77ef3e84@X220.alogt.com> <20131211140921.27cf6249@X220.alogt.com> <20131211144403.711eb6a9@X220.alogt.com> Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: FreeBSD Questions X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2013 06:46:55 -0000 It was a VM. Problem is the person who set up this machine had never used FreeBSD before and made a lot of really weird mistakes. I think the best course of action is to just create a new VM image and start from scratch. Ethan House On Tue, Dec 10, 2013 at 10:44 PM, Erich Dollansky < erichsfreebsdlist@alogt.com> wrote: > Hi, > > On Tue, 10 Dec 2013 22:27:11 -0800 > "ETHAN HOUSE (RIT Student)" wrote: > > > I think I found my problem. > > > > http://pastebin.com/tU395ifKhttp://pastebin.com/tU395ifK > > this is why I told you yesterday to run a fsck. > > Your main problem will be now finding the cause. Power failures are the > only cause that can be accepted from my point of view. When this is a > remote machine, I expect that it is connected to some kind of UPS. > > So, what was the real cause of it? Hard disk problem? If this was not > fixed, it could kill all your efforts in a fraction of a second. > > Try to find out more about the history of the machine. > > Erich > > > > > > > > Ethan House > > > > > > On Tue, Dec 10, 2013 at 10:09 PM, Erich Dollansky < > > erichsfreebsdlist@alogt.com> wrote: > > > > > Hi, > > > > > > On Tue, 10 Dec 2013 21:54:29 -0800 > > > "ETHAN HOUSE (RIT Student)" wrote: > > > > > > > As much as I hate giving up and starting up it's what I decided > > > > to do. > > > > > > > this is the best in your situation. > > > > > > > I am clearing out /usr/local and starting from scratch. > > > > > > you will then still have the database somewhere. This should > > > be /var/db/pkg but it also could be somewhere else. > > > > > > Just make a copy before you delete things. The good thing is that it > > > should be difficult to kill the system from now on. But you never > > > know. > > > > > > Erich > > > > > > > > > > > Thanks for all of the help guys, > > > > > > > > Ethan House > > > > > > > > > > > > On Tue, Dec 10, 2013 at 9:40 PM, Erich Dollansky < > > > > erichsfreebsdlist@alogt.com> wrote: > > > > > > > > > Hi, > > > > > > > > > > On Tue, 10 Dec 2013 21:23:59 -0800 > > > > > "ETHAN HOUSE (RIT Student)" wrote: > > > > > > > > > > > One more quick question. > > > > > > > > > > > > I am trying to rebuild all of my user land packages so it > > > > > > pulls down and fixes all of the broken deps. > > > > > > > > > > > I am not 100% sure if this will work. > > > > > > > > > > > $ portmaster -af > > > > > > ... > > > > > > ===>>> Currently installed version: virtio-kmod-9.0-0.242658 > > > > > > ===>>> Port directory: /usr/ports/emulators/virtio-kmod > > > > > > > > > > > > ===>>> This port is marked IGNORE > > > > > > ===>>> not supported ${OSREL} (9.2) > > > > > > > > > > > > > > > > > > ===>>> If you are sure you can build it, remove the > > > > > > IGNORE line in the Makefile and try again. > > > > > > > > > > Ask a search engine why this port is marked ignore. > > > > > > > > > > > > ===>>> Update for virtio-kmod-9.0-0.242658 failed > > > > > > ===>>> Aborting update > > > > > > > > > > > > Any idea how to get around this. I tried portupdate except it > > > > > > pkgdb -F wasn't happy I was using pkgng packages. > > > > > > > > > > > You must use either or. I would recommend pkgng. > > > > > > > > > > And still, I would copy the /usr/local directory to a different > > > > > location, delete all ports and start from scratch. I do not > > > > > believe that portmaster or portupgrade are able to handle all > > > > > weird situations which you might will find at that machine. > > > > > > > > > > Erich > > > > > > > > > _______________________________________________ > > > > freebsd-questions@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > > > To unsubscribe, send any mail to > > > > "freebsd-questions-unsubscribe@freebsd.org" > > > > > > > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to > > "freebsd-questions-unsubscribe@freebsd.org" > >