Subject: Re: upgrade problem
To: Nathan Langford <njl@sdf.lonestar.org>
From: Johnny Billquist <bqt@update.uu.se>
List: current-users
Date: 02/10/2004 02:50:39
On Tue, 10 Feb 2004, Nathan Langford wrote:

> On Mon, 9 Feb 2004, John R. Shannon wrote:
>
> > >From src/UPDATING:
> >
> > 20040109:
> >         Compatibility for old ffs superblock layouts has been
> >         added, and the restrictive fsck checks have been reenabled
> >         when using those layouts.  If you have been using -current
> >         since 20030402, you may find that fsck again signals fatal
> >         superblock mismatches.  To work around, you can use
> >         fsck_ffs -b 32 -c 4 to restore an alternate superblock
> >         and complete the filesystem upgrade.
> >
> >
> > My guess is this is your problem.
>
> I tried running "fsck_ffs -b 32 -c 4 /dev/rsd2a":
> FREE BLK COUNT(S) WRONG IN SUPERBLK
> SALVAGE? [yn] y
> UPDATE STANDARD SUPERBLOCK? [yn] y
>
> It didn't seem to solve anything and I got the same error
> message at boot time.  I also tried with SALVAGE=n.
>
> Once again, any suggestions are most appreciated.

The original error looks like you don't have sd2.
swapctl and fsck both complains that /dev/sd2x is not configured.
Does /dev/sd2x exist in your /dev? (where x = a,b,c...)

Does netbsd nowadays create a /dev on a ramdisk if it don't exist? If so,
make sure you are not getting into that when you get into single-user
mode.

Another item would be to check that you actually have a sd2 when you boot.
That's earlier in your dmesg.

	Johnny

Johnny Billquist                  || "I'm on a bus
                                  ||  on a psychedelic trip
email: bqt@update.uu.se           ||  Reading murder books
pdp is alive!                     ||  tryin' to stay hip" - B. Idol