Subject: Re: upgrade problem
To: None <firstname.lastname@example.org>
From: Nathan Langford <email@example.com>
Date: 02/10/2004 01:44:07
On Mon, 9 Feb 2004, John R. Shannon wrote:
> >From src/UPDATING:
> 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.
> On Monday 09 February 2004 04:24 pm, Nathan Langford wrote:
> > I am in the process of upgrading to -current to take advantage of the MP
> > code. I used build.sh to compile the kernel and userland into the obj/
> > directory, then ran "./build.sh install=/".
> > Fortunately the new kernel boots, but unfortunately it puts me in single
> > user mode after complaining about file system problems. The old kernel
> > boots up just fine, however.
> > Any suggestions would be greatly appreciated. Below are the error message
> > and dmesg output from the 1.6.1 kernel.
> > Thanks
> > -Nathan
> > ---- error message after kenel loads ----
> > swapctl: /dev/sd2b: Device not configured
> > Starting file system checks:
> > Can't open /dev/rsd2a: Device not configured
> > CAN'T CHECK FILE SYSTEM.
> > /dev/rsd2a: UNEXPECTED INCONSISTENCY; RUN fsck_ffs MANUALLY.
> > Automatic file system check failed; help!
> > init: /bin/sh on /etc/rc terminiated abnormally, going to single user
> > mode.