Date: Thu, 9 Dec 2010 11:38:29 -0800 From: Kurt Buff <kurt.buff@gmail.com> To: FreeBSD Questions <questions@freebsd.org> Subject: Re: mountroot prompt in the middle of updating - can't get past it Message-ID: <AANLkTi=8KPAECMPNfxgMMuC3r8eX%2Bh1ByQtX=_eqUyix@mail.gmail.com> In-Reply-To: <84950898@bb.ipt.ru> References: <AANLkTin8vGQCnCQa2q_r5n%2BFg9vOTAyEwP68BMacdeYu@mail.gmail.com> <84950898@bb.ipt.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Dec 8, 2010 at 22:50, Boris Samorodov <bsam@ipt.ru> wrote: > On Wed, 8 Dec 2010 11:49:41 -0800 Kurt Buff wrote: > >> All, > >> I have a Lenovo T61 with a 100g HD that I dual boot with FreeBSD >> 8.0-STABLE amd64 and Windows XP. > >> FBSD is on ad0s2a, with ad0s2b as swap, and XP on ad0s1a. > >> Yesterday I booted up FBSD, started xfce4, started a terminal session, >> su'ed to root and did the following - running a generic kernel: > >> # cd /usr/src >> # make buildworld >> # make buildkernel >> # make installkernel > >> Then I exited xfce4, did sudo shutdown -r now, and got a mountroot >> prompt that I now can't get past. > >> I can get to the loader prompt, and lsdev shows the following: > >> =C2=A0 =C2=A0cd devices: >> =C2=A0 =C2=A0disk devices: >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0disk0: =C2=A0 =C2=A0 BIOS drive C: >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 disk0s1: NTFS/HPFS >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 disk0s2a: =C2=A0= FFS >> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 disk02sb: =C2=A0= swap > >> when I use '?' at the mountroot prompt I get: > >> =C2=A0 =C2=A0List of GEOM managed disk devices: >> =C2=A0 =C2=A0 =C2=A0 acd0 >> =C2=A0 =C2=A0Loader variables: >> =C2=A0 =C2=A0vfs.root.mountfrom=3Dufs:/dev/ad0s2a >> =C2=A0 =C2=A0vfs.root.mountfrom.options=3Drw > > >> I've tried entering the following at the mountroot prompt, with no succe= ss: >> =C2=A0 =C2=A0ufs:/dev/ad0s2a >> =C2=A0 =C2=A0ufs:/ad0s2a >> =C2=A0 =C2=A0ufs:ad0s2a >> =C2=A0 =C2=A0ffs:/dev/ad0s2a > >> and several other variations that I've found while googling, but no >> success anywhere. > >> Does anyone have thoughts on how to remedy this? > > Just for the last question: > Try to load an old kernel. (Type "boot /boot/kernel.old" at loader > prompt.) That worked... I think I'll try the update process again. Anything else you can recommend? Thanks, Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTi=8KPAECMPNfxgMMuC3r8eX%2Bh1ByQtX=_eqUyix>