Date: Tue, 28 Jun 2011 15:50:25 +0200 From: "Dr. A. Haakh" <bugReporter@Haakh.de> To: Polytropon <freebsd@edvax.de> Cc: Kurt Buff <kurt.buff@gmail.com>, freebsd-questions@freebsd.org Subject: Re: fubar'ed it good this time... Message-ID: <4E09DC21.6070903@Haakh.de> In-Reply-To: <20110628052446.89911e0a.freebsd@edvax.de> References: <BANLkTimc%2B-Dvjpp9h0DYg8ofFt-Yr8DrMg@mail.gmail.com> <4E08558A.7000101@my.gd> <BANLkTimbCcsdGnNLWcYvEjQUy5EHWDbVjQ@mail.gmail.com> <20110628052446.89911e0a.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Polytropon schrieb: > On Mon, 27 Jun 2011 06:40:27 -0700, Kurt Buff wrote: > >> Your advice sounds reasonable, but that site seems devoted to zfs bootables. >> >> I wonder if an 8.1 livefs iso will do the trick... >> > Check if you can download FreeSBIE somewhere. It's a live system > using the 5.x and 6.x kernel which should be fine. Next to two > GUI modes (light, heavy) it also has a versatile "maintenance mode" > for such operations. I have already successfully used this system > for solving similar situations, for diagnostics, and for data > recovery preparation. > > The loader obviously knows how to deal with the filesystem because he loads the failing new kernel. So the easiest solution would be to boot an older kernel if available. I don't know how freebsd-update deals with older kernels, he should still be around. First guess is /boot/kernel.old/kernel. So get the loader-prompt, "unload kernel" and try "load /boot/kernel.old/kernel". Andreas
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4E09DC21.6070903>