Date: Mon, 01 Oct 2012 11:50:21 +0100 From: Matthew Seaman <matthew@freebsd.org> To: Rod Person <rodperson@rodperson.com> Cc: Olivier Nicole <olivier.nicole@cs.ait.ac.th>, "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: Port update hosed entire system Message-ID: <5069756D.3010701@freebsd.org> In-Reply-To: <20121002061026.0a052767@atomizer64> References: <20121001200829.2c8afade@atomizer64> <CA%2Bg%2BBviBRZYQ1DZAYTi4Pwnr9P96vonx7c-kjiFhEd-aWe0Ojw@mail.gmail.com> <20121002061026.0a052767@atomizer64>
next in thread | previous in thread | raw e-mail | index | archive | help
On 02/10/2012 11:10, Rod Person wrote: > On Mon, 1 Oct 2012 09:47:51 +0700 > Olivier Nicole <olivier.nicole@cs.ait.ac.th> wrote: >> >> Can you run /bin/sh? That would be a start to try reinstalling what >> was lost. >> > Nope. > > $ /bin/sh > Segmentation fault (core dumped) How about /rescue/sh ? It's statically linked so should continue working no matter the state of the shared libraries on the system. Failing that, booting from the install media into a livefs is your best bet. You should be able to mount your system disks or import a ZFS pool and fix their contents. Also, wondering how exactly your original command managed to hose the base system. Did it fill up the disks? Is it possible that the problem is actually hardware failure? Cheers, Matthew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5069756D.3010701>