Fwd: fubar'ed it good this time...
kurt.buff at gmail.com
Mon Jun 27 14:19:08 UTC 2011
This should have gone to the list - sorry.
---------- Forwarded message ----------
From: Kurt Buff <kurt.buff at gmail.com>
Date: Mon, Jun 27, 2011 at 07:17
Subject: Re: fubar'ed it good this time...
To: Warren Block <wblock at wonkity.com>
On Mon, Jun 27, 2011 at 06:40, Warren Block <wblock at 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
> 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 hand:
atapci0: <Intel ICH8M SATA300 controller> port
decive 31.2 on pci0
ata0: <ATA channel 0> on atapci0
ata1: <ATA channel 1> on atapci0
Then, at the end, I show:
Trying to mount root from ufs:/dev/ad0s2a
ROOT MOUNT ERROR:
If you have invalid mount options, reboot, and first thre the
following from the loader prompt:
>> 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
> Don't know what would cause that. Custom kernels could have the
> ATA_STATIC_ID option removed, which might give the disk a different number,
> ad2 or ad4 usually.
> The BIOS could have AHCI mode set, but that should not change with 8.2. That
> 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.
More information about the freebsd-questions