Base System Rebuild

[ETHAN HOUSE (RIT Student)]

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 at alogt.com> wrote:

> Hi,
>
> On Tue, 10 Dec 2013 22:27:11 -0800
> "ETHAN HOUSE (RIT Student)" <ewh2048 at 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 at alogt.com> wrote:
> >
> > > Hi,
> > >
> > > On Tue, 10 Dec 2013 21:54:29 -0800
> > > "ETHAN HOUSE (RIT Student)" <ewh2048 at 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 at alogt.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > On Tue, 10 Dec 2013 21:23:59 -0800
> > > > > "ETHAN HOUSE (RIT Student)" <ewh2048 at 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 at freebsd.org mailing list
> > > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > > > To unsubscribe, send any mail to
> > > > "freebsd-questions-unsubscribe at freebsd.org"
> > >
> > >
> > _______________________________________________
> > freebsd-questions at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> > To unsubscribe, send any mail to
> > "freebsd-questions-unsubscribe at freebsd.org"
>
>