Date: Mon, 27 Jun 2011 07:19:06 -0700 From: Kurt Buff <kurt.buff@gmail.com> To: FreeBSD Questions <questions@freebsd.org> Subject: Fwd: fubar'ed it good this time... Message-ID: <BANLkTikaS-yOObAPc4r=s8fNuVgnG%2BCL3Q@mail.gmail.com> In-Reply-To: <BANLkTinEdhygWbHc5foC3UbBspOs0fTY-A@mail.gmail.com> References: <BANLkTimc%2B-Dvjpp9h0DYg8ofFt-Yr8DrMg@mail.gmail.com> <alpine.BSF.2.00.1106270729580.95578@wonkity.com> <BANLkTinEdhygWbHc5foC3UbBspOs0fTY-A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This should have gone to the list - sorry. ---------- Forwarded message ---------- From: Kurt Buff <kurt.buff@gmail.com> Date: Mon, Jun 27, 2011 at 07:17 Subject: Re: fubar'ed it good this time... To: Warren Block <wblock@wonkity.com> On Mon, Jun 27, 2011 at 06:40, Warren Block <wblock@wonkity.com> wrote: > On Sun, 26 Jun 2011, Kurt Buff wrote: > >> Sitrep: Lenovo T61, dual booting WinXP and FreeBSD (amd64 8.1-RELEASE) >> on a 500gb drive. Just did a freebsd-update from 8.1 to 8.2, just >> doing the second boot to do 'freebsd-update install' for the second >> time, and got dumped into the mountroot prompt. >> >> AFAICT, I managed somehow to write something strange into /etc/fstab. >> Can't tell what it is, because during boot it passes by too quickly >> for me to read, and the boot process dumps me into the mountroot >> prompt. > > Scroll Lock and Page Up/Down should work there to scroll back to see the > disk device numbers. Scroll lok and page up work, and what I see is the following, copied by han= d: =C2=A0 =C2=A0 atapci0: <Intel ICH8M SATA300 controller> port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x1c30-0x1c3f,0x1c20,0x1x2f at decive 31.2 on pci0 =C2=A0 =C2=A0 ata0: <ATA channel 0> on atapci0 =C2=A0 =C2=A0 ata0: [ITHREAD] =C2=A0 =C2=A0 ata1: <ATA channel 1> on atapci0 =C2=A0 =C2=A0 ata1: [ITHREAD] Then, at the end, I show: =C2=A0 =C2=A0 Trying to mount root from ufs:/dev/ad0s2a =C2=A0 =C2=A0 ROOT MOUNT ERROR: =C2=A0 =C2=A0 If you have invalid mount options, reboot, and first thre the following from the loader prompt: etc. >> WinXP still boots just fine, and the FreeBSD boot manager is in place, >> and was working before the update. >> >> FreeBSD was booting just fine from /dev/ad0s2a, prior to running >> freebsd-update. > > Don't know what would cause that. =C2=A0Custom kernels could have the > ATA_STATIC_ID option removed, which might give the disk a different numbe= r, > ad2 or ad4 usually. > > The BIOS could have AHCI mode set, but that should not change with 8.2. T= hat > would make the disk ada0. > > I second the suggestion of mfsBSD. OK - when I get home from work, I'll download and see what that does for me= . Thanks, Kurt
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?BANLkTikaS-yOObAPc4r=s8fNuVgnG%2BCL3Q>