Date: Tue, 10 Dec 2013 22:46:52 -0800 From: "ETHAN HOUSE (RIT Student)" <ewh2048@rit.edu> To: Erich Dollansky <erichsfreebsdlist@alogt.com> Cc: FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: Base System Rebuild Message-ID: <CAFRryZjAvexmHGS8%2Bm6v=61oYGcag55wba%2BgzaB0afArhmLcMw@mail.gmail.com> In-Reply-To: <20131211144403.711eb6a9@X220.alogt.com> References: <CAFRryZg9GwSWLB3ytdpmVgrfnp4T0i6b0sgCJh9xuEdOic-Dng@mail.gmail.com> <20131210162820.6834d51b@X220.alogt.com> <CAFRryZhTbbb8ZFBXX3HPvFSCDz16P9be0nd2Y%2B8T_vNxk-9tag@mail.gmail.com> <20131210170905.1dfb9fd7@X220.alogt.com> <CAFRryZhNKQz=EsxNdvXqBNj81u3VeFjJAYwcJnBMrFLXFk-jdA@mail.gmail.com> <20131210172513.77fa8482@X220.alogt.com> <CAFRryZivwj-0%2BSPO4gUZxv=0LAQZE8UoUrBOAb0cYVMZkUohtw@mail.gmail.com> <CAHu1Y72sTOpWSD_%2BKVwHxxj6N=L7aQdso092sYS=yeABFv=zXg@mail.gmail.com> <52A79136.7090103@ShaneWare.Biz> <76E49CC4-57CE-4A45-B051-025D465B311F@fisglobal.com> <CAFRryZjJ_Q2GGyPnAEKp_403f_8zOuG4FD%2BNdWCSJb%2BuvBgQ0w@mail.gmail.com> <20131211115641.5e15206e@X220.alogt.com> <CAFRryZghKK55kFUbnzKC7omkNCkqeJ7-Kg76QWBsZ=jeA5sGbA@mail.gmail.com> <20131211134031.77ef3e84@X220.alogt.com> <CAFRryZi0coRx%2B3urhvj=jvAKfhdc3=YkhbpcLs4mdKVN%2B3buCA@mail.gmail.com> <20131211140921.27cf6249@X220.alogt.com> <CAFRryZj6n8NuT1AViCkQLWyjGUG6HDM_vyzcMYTryHnhf5tT0Q@mail.gmail.com> <20131211144403.711eb6a9@X220.alogt.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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)" <ewh2048@rit.edu> 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)" <ewh2048@rit.edu> 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)" <ewh2048@rit.edu> 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" > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAFRryZjAvexmHGS8%2Bm6v=61oYGcag55wba%2BgzaB0afArhmLcMw>